Archive for category: News

Note: Though possible, I would not recommend using jobdump and jobload from one version of Lawson to another as fields may change. Use at your own risk.

 

For this article, we will be doing jobdump and jobload in v10 between Prod and Test ProductLine.

Here are the flags for jobdump:

As you can see above, the flags give plenty of flexibility to specify what to dump. For this tutorial, we will be dumping all jobs for a single user from v10 Prod to v10 Test.

Step 1: First login to Lawson Interface Desktop, we’re logging into our v10 Prod server.

jobdump -d -o Job -v UserName LawsonPOBatch po_jobs.dmp

So we are essentially dumping all jobs –o Job for user –v UserName <YourUsersName> to a file called po_jobs.dmp that will be created in our current directory D:\lawson\temp\jobdump

We are dumping all jobs under our user: LawsonPOBatch. Make sure your user(s) exists in both ProductLines already.

Step 2: Transfer over your_dump_file.dmp file to other server via FTP etc.

Step 3: Login to your other servers productline, for us it will be v10 Test. Navigate through LID to your_dump_file.dmp file. This for us is: po_jobs.dmp

Here are the flags for jobload:

Since we dumped from Prod, we would be loading to Test. If it’s for the same user, no need to specify the username. If migrating to a new user with a different name, you can use a –m <source_user> <target_user>

We are transferring to the same user that is in both PROD and TEST so we don’t specify this.

Since we are transferring jobs from PROD to TEST you could specify this with –m ProductLine <SOURCE_PRODLINE> <TARGET_PRODLINE> (Must be in caps.)

Step 4: Run jobload in preview mode (without -c)

jobload -o Job -m ProductLine PROD TEST po_jobs.dmp

Or you could simply go into the .dmp file and change all instances of PROD to TEST (or whatever the name of your ProductLine is)

Then you could simply run

jobload -o Job po_jobs.dmp

This will run in preview mode. Run until you have no errors.

Step 5: Run in commit mode.

jobload -c -o Job -m ProductLine PROD TEST po_jobs.dmp

or

jobload -c -o Job po_jobs.dmp

if you edited the .dmp file manually.

If it was successful you’ll see the jobs being added.

Login to Lawson portal and verify those jobs got transferred over from that user.

Done!

File Channels are a feature in IPA that is similar to the ScanFile Client feature in ProcessFlow. A File Channel scans a directory periodically for files which will kick off processes in IPA. The files and processes are configured in File Receivers. Here is how to set them up.

How to Set up File Channels

1. Log in to Rich Client 
2. The canvas is now open. Look in the upper left corner and make sure you are pointing to the prod or test data area (not gen) 
3. In the upper right corner, click “Start > Applications > Process Server Administrator > Administration > Channels Administrator”
   
   1. At this point, you can click, HOLD, and drag the “Channels Administrator” link to the canvas. That way, it will create a shortcut on the canvas. 
4. Once you are in Channels Administrator, click on the File Channels tab
5. Click Actions > Create or click the create icon 
6. Overview Tab
   
   1. Enter a meaningful channel name
   2. Enter a description for the channel
   3. Check “Is Enabled”
      1. This can be unchecked when the file scanner is not needed
   4. Choose the channel type
      1. Local points to a directory on the local server
      2. Remote requires FTP to be enabled on the local server and the remote server
   5. Enter the directory that will be scanned by the file channel
   6. Choose whether to match case sensitivity on the file
   7. Enter an error file directory
      1. This is where files will go if there is an error in the scanning (NOT an error in the flow)
   8. Enter an in-progress file directory
      1. This is where files will go once they are successfully scanned
   9. Choose a scan interval (in minutes)
7. Click the Save icon 

How to Set up File Channel Receivers

1. Once you have created your File Channel, you must now set up the File Channel Receivers, which will configure the files that are picked up during a scan
2. Make sure your File Channel is deactivated
   1. File Receivers cannot be created or modified if the File Channel is active
   2. Go to the File Channels screen
   3. Right click on the File Channel for which you are adding a receiver
   4. Select “Deactivate” 
3. Open your new File Channel and navigate to the File Channel Receivers tab
4. Click Actions > Create or click the create icon 
5. Enter the Receiver details
   

1. Enter a name for the Receiver
2. Enter a description
3. Choose the file name for which the receiver will be scanning
   1. You can use regular expressions here
4. Select the process that should begin when the file is found in a scan
5. Choose the Startup Type

• Click the Save icon 
• Be sure to reactivate your File Channel so that it can begin scanning for your files

You’re about to make some changes but want to create a backup for LDAP just in case there are any mistakes.

Let’s get started:

First thing we need to do is remote into the v10 server you want to backup LDAP.

Once in, create a “temp” directory somewhere in Lawson or lsfprod. For us, this will be Lawson\temp\<todays date>

Run CMD.exe as administrator:

Switch to drive Lawson is on, for us this is the D:\

Now type dsdbutil and hit enter, then type list instances and hit enter to get a list of instances.

Once you know what instance you want, type Activate instance <Instance Name>

This will set the instance name to backup.

Type ifm and press enter. To create the backup, type create full <directory output name>

Make sure there are no spaces in your directory output name.

Example:

create full D:\lawson\temp\20160531

Now check that directory and there should be a .dit file.

To restore an LDAP backup, turn off IBM Services in the correct order.

This should be:

1. IBM Websphere app. server v8.5 Infot10Prod-app.
2. IBM Websphere app. server v8.5 Node Agent
3. IBM Cellmanager02

Turn off Prodinfor10ADLDS service (or similar name)

Then go to the <Drive>\Microsoft ADAM\ProdInfor10ADLDS\data directory and replace the .dit file with your backup (back up the existing .dit file just in case).

Start those IBM services back up in proper order along with Prodinfor10ADLDS.

System Preparation

1. Get the latest BSI installation file and save to the Infor downloads folder on the server
2. Run the executable to unpackage the installation files

Database Preparation

Create the TF10 database

1. Open SQL Server Management Studio
2. Create TF10_10X database
   1. Right click on databases > New
   2. Set the file locations under General
      

3. Options Menu
   1. Set collation to Latin1_General_Bin
   2. Recovery model = Full
   3. Compatibility Level = SQL Server 2008
   4. Keep the other defaults

Create the TF10 user

1. In SSMS, right click on the main Security server and select “new Login”
2. Login name = tf10
3. Use SQL Server authentication
   1. Password is usually tf10 unless the client request a different password
4. Default Database = (your desired database name)
5. Click OK
   

6. Add the user to your database
   1. Expand the database in SSMS
   2. Expand the security folder
   3. Right click on Users > New
   4. User name = (tax factory user)
   5. Login name = (tax factory user)
   6. Default schema = leave blank for now
   7. Click Ok

BSI SQL Scripts

1. Locate the SQL scripts within the BSI installation files (ServerInstall/SQL)

1. crtschma.sql
   1. Creates the tax factory schema
2. tf10sqv.sql
   1. Creates the table structure for tax factory
3. noessqv.sql
   1. Resets BSI TaxFactory extended security to off

Adjust Database Permissions

Adjust db permissions now that schema has been created:

1. Edit the database user on the new database
2. Make the new schema the Default schema
3. Click OK
   

4. Under Owned Schemas, select the new schema
   

5. Under “Membership”, select db_owner
   

6. Click OK

System Configuration

Set up ODBC

1. Open the ODBC (64-bit) tool
2. Go to the System DSN tab and click “Add”
   
3. Driver is SQL Server
   

4. Data source name = (meaningful name)
5. Description = (meaningful description)
6. Server = client’s database server name (SQL Server where you installed the database)
   

7. Use SQL Server authentication
8. Provide the login credentials
   

9. Keep the defaults on the rest of the screens
   

10. Test the data source
    Environment Variables

1. Create dataset environment variable
2. Create the TF10_CONNECT_STRING environment variable using the login credentials for the ODBC data source you just created
   

3. Reboot for env variables to take effect

Copy application files

1. Copy new tf10api.dll from the installation files (ServerInstall\server) to Lawson application server (C:\Windows\System32 & C:\Windows\System)
   

Installation

Install Client Application

1. Obtain BSI password needed for TF10 install from BSI Customer Services
2. Install TF10 – TF10ClientInstall.exe on the BSI application server (adding a new BSI instance such as test, qa, test, etc)
   
   
   (password obtained from BSI customer services)
   
   

1. If prompted to install Web Server, refer to Apache Tomcat installation instructions
   
1. Select the Tomcat installation directory (will most likely default)
   

4. Select the JRE configuration file (will most likely default)
   

5. Choose the XML server corresponding to the system configuration
6. Select a directory for the server base
   

7. Choose Install
   

8. Enter the corresponding system information and click Next
   1. Clicking on the MS SQL Server ODBC configuraiton will prompt the system to ass if you use Windows Authentication. Select “No”.
      
      
      

9. Can install up to 3 test instances on same server, but each one would have different WEB Server Service Port
10. Repeat this section for the remaining test instances
11. When you are finished with all instances, select the environments to be installed and click “FINISH”
    
    

Test the install

1. Open <server>:<port> for the initial test
   

2. Open the custom site that you installed and log in
3. Check the System tools
   1. Regulatory bulletins should be 0
   2. Cyclic should be blank
4. Log into server:port/ef10x/PRD
   1. Where “x” is the cyclical release and “PRD” is the environment
      

Cyclical Data Refresh

1. Back up new 10x database
2. Back up the current 901 BSI database
3. Restore the 901 data to the 10x database to preserve all the tax updates.
   1. NOTE: During db restore, be SURE to confirm the target db file names, will probably need to change.
   2. Kill the bsi services running on bsi xml server, then sp_who2 to kill any remaining processes
   3. Take db offline
      

4. Restore the database
5. Restore of db disconnects users
   1. Assign the tax factory and db_owner schemas to dbo
   2. Delete and recreate tax factory user following instructions above
      
      
      

4. Log into the BSI site and verify that the Cyclical update inofrmation is now populated

Install Machine Key

As INFO: table containing the BSI machine key:

12. Install Machine Key – if/when we have it
    1. Generate from BSI site, Maintenance, Maintain Machine Key
    2. Bring up web client, System Tools, Database Tools, Install Machine Key
13. Can skip the load regulatory bulletins, cyclic files, etc, since DB restore was performed

PRTFX

1. Open LID
2. Type in msgmnt
3. Update Lawson PRTFX Message Definition, (change bottom TF90 to TF10)
   

4. Compile the prtf program, (needed after changing the TF90 to TF10 in screen above)
   

5. Test with LID
   1. Click Refresh Version
   2. Click “test TaxFactory US”
      1. Will generate a licensing error if the machine key isn’t installed yet
         

6. New jobs should start reflecting in BSI TaxFactory Product in Message Viewer

Apache Tomcat Installation

1. Download the required installation files from the Apache website
   
   

2. Save the executable
   
   

3. Run the executable
   
   
   

4. Customize the Windows service name
   
   
5. Select the JRE path (will likely default)
6. Choose the install location
7. After the installation is complete, change the service to startup type Automatic