Archive for category: Frontpage Article

Candidates and suppliers from Landmark applications should not be synced to LSF. Services which allow users to register externally are services that should NOT be synced. If they were synced to LSF, follow the steps below to remove user and identity records from LSF.

Configure sync service lists to exclude candidates from sync – This process should be used if possible
Use Configure Services for Synchronization menu in ISS

Manual Sync service list configuration – This process may be used if not all services are shown in ISS
Export list of all services from LMK
 secadm -p <secadmpassword> service list
 The list outputs to the screen –copy the list from the screen into a text document
Determine which services from each system you DO want synced

Configure sync service lists for LSF and LMK in the LSF by adding the following lines to LAWDIR/system/lsservice.properties file:

 fed.LSFSERVERNAME.DOMAIN.COM;40000;40001;LSF. syncServiceList=YourListofLSFServicesToSync,SeparatedByCommas,NoSpaces fed.LMKSERVERNAME.DOMAIN.COM;10888;11888;LANDMARK. syncServiceList=YourListofLMKServicesToSync,SeparatedByCommas,NoSpaces

 Save changes and close lsservice.properties
Restart LSF and WAS

Configure tuning for sync*

1. Add the following line to the LAWDIR/system/lsservice.properties

file: Nthread=5

This value can be any number between 2 and 10. You can tweak the Nthread parameter until you find the optimized setting for your system. Do not go above 10 unless directed by Infor.

2. Adjust lase GRID node max heap to at least 3096

From the Grid Management main page go to Configuration Manager->Applications->Application->Landmark and the select the environment.
Select “Edit Properties.”
Under Grid Defined Properties -> Node Memory, select “Max Heap.”
Adjust the lase node memory to 3096 and then click Save
It may be set higher if number of users/identities indicates
-Restart the node for this environment or restart Landmark.

Follow these simple steps to learn how to include Report ID in LBI Maintain Reports

1. First, go into Tools when logged in as an admin and select “Reporting Services My Reports”.
   
2. Under the “All” section in the Report Lists on the left side dash, click “Edit List” on the top right of the screen.
   
   
3. Next, under “List Options” select “Columns”.
   
4. Then select “Report Id” and click the right arrow in the middle of the screen:
   
5. Click “Save and Exit” and then go to “Maintain Reports” in the Reporting Services Administration Report Management Menu.
   
6. Now you’ll see all the Report ID’s on the right hand column:
   

That’s all there is to it!

File channels in Lawson Infor Process Automation (IPA) are very useful for picking up flat files and processing them.

In Infor’s older Rich Client tool, this can be easily found under the Start button drop down.

However, based on user permissions, this might not appear properly so I will tell you two ways to access the Channel Administrator.

First should be the obvious way which is Administrator >> Channel Administrator

However, based on your _ST roles, this might’ve not been granted properly. So, the second way to access it is in the top right search box. You can search Channel Administrator and access it there.

After a fresh install of Lawson, you may receive a “file not found” error in LID when adding a batch job.  Or, inquiring on certain forms might time out.  The batch job itself may show an error message alluding to the LUU utilities (such as invalid fstab option).  The issue is potentially an incorrect LAW_COBRTS_PATH.

To resolve, open a command line utility with the Lawson environment variables set.  Type command “laconfig”.  The configuration window pops open.

Select your environment.

On the environment tab, check the LAW_COBRTS_PATH.  If it is incorrect, fix it.

Reboot the server, or restart the services, and try your batch job again.