September 23, 2014
By Dan Alex Solis, IPA Development Team Lead
Infor Lawson System Foundation (LSF) 184.108.40.206+ has the ability to use Infor Process Automation (IPA) as the business process automation engine instead of the default (and older) Infor ProcessFlow Integrator. In LSF version 10.x Infor Process Automation becomes the default business process automation engine. This article provides information on debugging integration issues between LSF and IPA. As always, your first source of information on this topic should be the published Infor user guides. Specifically, you should read the “Infor Lawson System Foundation Using Infor Process Automation Configuration Guide”. But if you are a system administrator and still experiencing issues with the integration, read on!
General LSF-IPA Connectivity Issues
When something fails between LSF and IPA, the following can be used as the initial steps in debugging the problem. We are assuming you are creating workunits correctly in LSF but they are not being sent to IPA. We are also assuming you have read and performed the steps in the Configuration Guide mentioned above (such as synchronizing the security .jar files between the servers).
The first thing to check will be the required software services for the connection to happen. Second would be the LSF logs as they will contain the necessary information on why the connection is failing. Possible corrections can then be made via the pfserv command on LSF and the Infor Lawson configuration settings in IPA configuration sets.
Required LSF and IPA services/server components
- LSF Services:
For LSF to be able to communicate to IPA the LSF RMI (Remote Method Invocation) and EM (Event Manager) services should be running.
Windows and unix/iSeries OSes have different commands that can be run to check if these services are running. It is important to remember here that EM is dependent on RMI so RMI should be up before EM is started.
Here is a list of the commands:
- Infor Java Framework GRID and IPA Node:
For IPA, the Infor Java Framework Grid should be up and running and the IPA node up and running as well within GRID. The status of GRID can be determined by the command ‘manage grid list’ or by using the Grid Monitor client. IPA (listed as “LPA” application)should also be listed as started.
The LSF RMI Service has the pfrmi.log and EM has the EM.out, EM.trc and EM.log logs (all can be found in <LAWDIR>/system.)
You will need to look out for LPSConnectionExceptions in the logs as these indicate a problem with the connection. A description of why the LPSConnectionException is happening is included and the message will help in debugging the issue.
For example, an exception of com.lawson.bpm.netutils.LPSConnectionException: Unable to create LPSGridSession – Process Server is not running for data area: <data area name> would mean that either that data area is not existing in IPA or is not configured properly.
Any LPSConnectionExceptions concerning the user credentials or wrong host/port values can be corrected by running pfserv config lps (discussed in the next topic)
When the PFI workunit has a status of either 27 (LPS trigger Request Failed) or 28 (LPS Cancel Request Failed), the reasons for the failure is recorded in em.out and em.log as well as the workunit error records.
IPA settings in LSF via pfserv command
LSF connectivity to IPA settings can be defined via the ‘pfserv config lps’ command. This command is run under the command line or console, or on LID. The command will have 10 interview questions. These are as follows:
- Is LPS used instead of PFI? – (LSF 9.0.1.x only) LSF 9.0.1.x comes prepackaged with a default business process automation tool in the form of ProcessFlow Integrator (PFI). IPA is the next generation of PFI and comes with a lot of improvements. To configure LSF to use IPA instead of PFI, this should be set to Y.
- LPS Grid Host Name – The name (or IP address) of the server where the Infor Java Platform GRID and IPA reside on
- LPS Grid Port – The port number to where GRID is attached to. The quickest way to get this is to do a manage grid list on the IPA console. This is the value listed as ‘Registry on port <grid port>’ at the top of the results.
- LPS User – LPS username to connect to grid
- LPS Password – Password of said user
- Remaining Workunits for processing – (LSF 9.0.1.x only). This tells the server to finish processing waiting workunits in PFI before shutting down ad switching to IPA.
- Disable PFI Inbasket – (LSF 9.0.1.x only) This will disable the portal bookmark for PFI Inbasket for ALL portal users.
- Disable LPS Tracking – This will disable the portal bookmark for IPA Tracking for ALL portal users
- Disable LPS Admin – This will disable the portal bookmark for IPA Administration for ALL portal users.
lpsDataArea in bpm.properties – The lpsDataArea property in <LAWDIR>/system/bpm.properties sets the default data area to use when connecting to IPA if none is provided by a trigger or logan was used.
LSF settings in IPA via Configuration Sets
IPA also has settings in IPA to set the server details of the LSF server connecting to it. This is normally used by inbasket for linking custom forms/ to Start -> ProcessFlow Adminstration -> System Configuration -> Main.
Issues with Triggering from LSF Applications
Infor Lawson applications have the capability to trigger Processes in IPA. This section discusses the things to look at when the triggers do not create a workunit in IPA.
These are the logs to look at whenever a trigger does not work with a Infor Lawson application form. The logs can be found in <GENDIR>/bpm
LPSforLSF_n.log : This log covers the actual trigger calls from LSF to IPA.
wfapi_n.log: This log covers api calls that the trigger uses to work with the LSF applications. This is not generated by default. To enable wfapi logging, add a record in PFI’s Configuration property with System Name: WFCONFIG, FieldName: DEBUG and Field Value: 1
JNI/Socket modes of trigger communication
The Infor Lawson application trigger has two modes of communication. The first, JNI, allows LSF to connect to IPA java APIs directly. The second is socket mode where the LSF communicates by socket messages to the event manager and the event manager acts as a middleware to the trigger and IPA. JNI being the default mode sometimes has problems with loading the necessary libraries to communicate with IPA depending on the platform and supporting library versions. Switching IPA to use socket mode will resolve this issue. To switch the application trigger to use socket mode, add the property useLPSBridgeSocket=true in <LAWDIR>\system\bpm.properties and restart the RMI and Event servers.