APIs provide a secure way for unrelated applications to communicate with each other. IPA allows you to utilize third-party APIs to integrate applications with Lawson. It is a way to export data such as employee records or purchase requests, as well as importing data such as time records or third-party billing & revenue.
Learn how to use IPA to effectively communicate with third party applications in real or near-real time.
When performing an update of Lawson Core Technology, you may come across the error “LID port xxx already used”. If your services are stopped, and you know nothing is listening on the LID port, you may have to temporarily change the port to get the install to complete.
To change the port, open the command line as administrator and set the environment variables. Then, type the command “laconfig” to open the configuration screen. Change the “lalogin Port” to some other port that isn’t being used. Click “Apply” and “OK”. Continue with the technology update.
After the technology update, go back into laconfig. The port should have been set back automatically (based on the install.cfg file). If it isn’t, you can set it back manually.
Often, when you are having an issue with Lawson and/or Landmark, one of the questions Infor will ask you is whether your systems are federated. If you are unsure, there are a couple of simple ways to tell.
First, you could log into the WebSphere instance for your LSF application. Go to Applications > Application Types > WebSphere enterprise applications. If you see the application “scwebadminapp”, it is very likely that your systems are federated.
Another way to tell is to review the lsservice.properties file on either of your service (at LADIR/system for Landmark or LAWDIR/system for Lawson). If you see references to the remote server in these two files, and you see that there is an entry for “server.authservicename”, then your system is federated.
If you are running a Federation Sync in Landmark, and you get the below message “Socket timeout exception occurred”, you may need to increase the max heap on the lase node. This error message will also present itself in the security_authen.log on the Landmark server.
Sun Apr 25 17:07:26.438 EDT 2021 – 1584534648 – L(2) : Sync Analysis failed with exception. Details: Socket timeout exception occurred. (read timed out).
Stack Trace :
com.lawson.security.server.LawsonNetException: Socket timeout exception occurred. (read timed out).
at com.lawson.security.server.events.BaseEvent.readMsg(BaseEvent.java:235)
at com.lawson.security.server.client.ClientActorEvent.getNextActorIds2(ClientActorEvent.java:239)
at com.lawson.lawsec.authen.SyncAnalysis.getRemoteActorList(SyncAnalysis.java:2962)
at com.lawson.lawsec.authen.SyncAnalysis.loadActorsToSync(SyncAnalysis.java:1299)
at com.lawson.lawsec.authen.SyncAnalysis.performActorSyncAnalysis(SyncAnalysis.java:513)
at com.lawson.lawsec.authen.SyncAnalysis.run(SyncAnalysis.java:269)
at java.lang.Thread.run(Thread.java:748)
To update the lase max heap, open the Grid Admin window. Go to Configuration Manager > Grid Configuration > Grid Properties > Node Memory > Max Heap. Update the max heap to an appropriate level.
Save the setting and restart the lase node, or restart Landmark.
While you are running the federation sync, you can monitor the lase node in the grid’s topology view to see if your setting is appropriate for future syncs.
When dissecting the Object field of the comment (which contains the actual verbiage of the comment and other information) the first value is TYPE. This type determines the type of the comment that is stored.
The comment types for those added to an AP Invoice are as follows:
| Invoice Note/Report/Check Comments | Type=A |
| Invoice Notes | Type=N |
| Invoice Report Comments | Type=D |
| Invoice Check Comments | Type=C |
Keep in mind that to have the comments print on a check, not only would you need to have an Invoice Note/Report/Check Comments or Invoice Check Comments the users need to make sure that when the payment processing jobs (AP155/AP160 or AP161) needs to be set to Print or Include Comments.
If you have to open an Infor ticket for any Lawson product, such as EDI or EMSS, one of the first questions is going to be which version of the application you are using. Here are some quick ways to find your versions.
Navigate to LAWDIR/<prodline>/edi/install/install.cfg and look for “COMPONENT.EDI.VERSION”
Open the shopping screen (or any RQC screen) and select the down arrow in the far right corner. Click “About”.
Open any Infor-delivered EMSS screen and click the down arrow in the upper right corner. Click “About”.
Open the System Configuration menu item and make note of the “application fileversion”.
When installing a new IPA product line using the intall-lpa.pl command in Landmark, you may encounter the error “Security Class does not exist.” This will prevent the IPA environment from completing the install. To resolve this error, first run the command “scupdate <product line>”. This command will generate all the security classes needed for the new IPA product line. Then, rerun the install-lpa.pl command, and it should complete successfully.
Error messages (on the command line, and also found at LALOGDIR/managelpa_<pdl>.log)
Run the scupdate command and verify no errors
Complete the IPA product line install
