Archive for category: News

This article will demonstrate how to set up the most commonly-used Infor Lawson configurations in Landmark.

Infor delivers two configuration sets with Landmark: “main” and “system”.  “Main” refers to the LSF environment, and “system” refers to the Landmark environment.  It is best practices to use these configuration sets for the processes that access these systems.

Here are the most commonly used configurations for Lawson:

Infor Lawson

Used for web calls (DME/AGS) to Lawson, as well as Resource queries (Lawson Security)

• Infor recommends using Connection Type “Web”
• Retry Count – number of times IPA will retry the connection after a failed attempt
• Pause Time – Amount of time in milliseconds between each attempt to reconnect when web call fails
• User – the web user who has access to DME/AGS calls and/or Lawson Security
• Password – the web user’s password
• Data Area – the name of the data area being accessed in the LSF environment
• Web Root – https://servername.company.com
• Time Out – Number of seconds of attempting to connect after which a timeout occurs
• Page Size – The number of records returned in a DME query (blank means no limit)

File Access

Used for file reads and manipulation on the LSF server

• Click “Remote” if LSF resides on a different server from Landmark
• LSF Web RMI Root – Same as Web Root in the Infor Lawson connection (https://server.company.com)
• Web user – the user who has directory access on the Lawson server
• Web password – the above user’s password
• RMI timeout – Number of milliseconds of attempting to connect after which a timeout occurs
• GENDIR – GENDIR environment variable value on the LSF server
• LAWDIR – LAWDIR environment variable value on the LSF server

 

JDBC

Used for SQL Queries and transactions

• JDBC Driver – the driver name used for JDBC
• Database URL – build the URL for your db
  • Example: jdbc:sqlserver://servername\instancename:port;databasename=databasename
  • Instance Name is optional
  • Port is optional (default is 1433)

 

Web

Used for the Web Run process node (can be used to update and run batch jobs, etc.)

• Data Area – the data area to which you are connecting on LSF
• Web Root – https://servername.company.com
• User – the user who has access to web run calls
• Password – the above user’s password
• Time Out – Number of seconds of attempting to connect after which a timeout occurs
• Amount of time in milliseconds between each attempt to reconnect when web call fails

 

Sys Cmd

Used to run command line system commands, including Lawson commands such as importdb

• Check “Remote” is LSF resides on a separate server from Landmark
• LSF Web/RMI Root – https://server.company.com
• Web User – the user who has access to the LSF system
• Web password – Web User’s password
• RMI timeout – Number of milliseconds of attempting to connect after which a timeout occurs
• GENDIR – GENDIR on LSF system
• LAWDIR – LAWDIR on LSF system
• Run as user – the provide user credentials under which the command should run
  • NOTE: Windows no longer allows cmd to be run as a different user, so command line will always be run under the user running the bpm service. This is most likely the system user, and as a result, that user will have to be added to Lawson security and given access to run Lawson commands (if that is how this node is used)
• Run as user password – above user’s password (see note above)
• Command timeout – Number of milliseconds of attempting to connect after which a timeout occurs

These are instructions for copying user jobs (by user) between environments. This will NOT allow you to copy jobs between environments on different versions of LSF (i.e. you cannot use these commands to copy v901 jobs to v10x).

1. Run listusermap in both environments and make note of the NTID for the user in each environment
2. In the source environment, run the command

jobdump –d –o job –v UserName “DOMAIN\UserName” outputfile

3. Open the output file created by the command in a text editor
   1. Update any references to the NTID from the source system with the NTID of the destination system
   2. Make any directory structure changes as needed (i.e. change “D:\lsfprod to D:\lsftest”)
4. Copy the output file to the destination system
5. In the destination environment, run the command

jobload –c –o job inputfile

More on jobdump/jobload

The Data Iterator node can be used to loop through records.  One way to use this node is to loop through the lines of a TXT or CSV file so that the data can be manipulated and stored somewhere else, or used in Lawson programs.  Here is an example of a process using data iterators.  The first node accesses a csv file and loops through each line.  The second iterator takes the line from the first node, and splits it on a delimiter.  From there, it loops through each field in the line and makes an assignment.

1. The first node, which uses a file as the input
   1. Configuration name – select the configuration where the file resides (main is LSF, system is Landmark)
   2. Input file – the path to the file
   3. Parse by:
      1. Line – loop through each line
      2. Delimiter string – provide a character or string, the iterator will “split” on that string and loop through each item
      3. Length – use this for a fixed-length flat file
   4. Starting position – use this to determine which line the iterator should start on (so you could skip header rows if needed)
   5. Maximum read iterations – Use if you only want to read a certain number of lines/characters in a file
   6. Ignore trailing delimiter – will ignore the delimiter at the end of the line
   7. Accumulate output variables – Specifies whether records should be output into separate variables as they are parsed. If true (check box is selected), each record will be saved in the activity variable activityName_outputDataN, where activityName is the name of the activity and N is the record number.

1. The second node, which uses a file as the input
   1. Configuration name – select the configuration where the file resides (main is LSF, system is Landmark)
   2. Input data – the data to read into the iterator
   3. Parse by:
      1. Line – loop through each line
      2. Delimiter string – provide a character or string, the iterator will “split” on that string and loop through each item
      3. Length – use this for a fixed-length flat file
   4. Starting position – use this to determine which character the iterator should start on
   5. Maximum read iterations – Use if you only want to read a certain number of lines/characters in a file
   6. Bytes to read – used for fixed width files
   7. Delimiter string – the string that splits each field of the record
   8. Ignore trailing delimiter – will ignore the delimiter at the end of the line
   9. Accumulate output variables – Specifies whether records should be output into separate variables as they are parsed. If true (check box is selected), each record will be saved in the activity variable activityName_outputDataN, where activityName is the name of the activity and N is the record number.