Archive for category: News

When you journalize a Recurring Journal Entry, it goes through the standard JE approval flow. There is no delivered flow that looks at the Recurring Journal.

If you want the Recurring Journal Entry to be approved once when it is created and not approved each time it is journalized, a Custom IPA will need to be created to do that.

If you want changes on the Recurring Journal Entry to be re-approved when generated, make sure your custom trigger kicks off the IPA every time the Recurring Journal Entry is released.

You may then want to modify your JE approval flow to exclude transactions with the RJ system code since it was already approved – both initially and when it was changed.

You may find the need to install or update DSP for your SSO applications, such as LBI or MSCM.  DSP allows these external web application to authenticate against Lawson for Single Sign-On.

Information you will need:

• The password for ssoconfig
• The passkey used to install your current DSP version (if applicable)
• FQDN’s for your LSF server and the server that hosts the application for which you are installing DSP
• Credentials for an admin account (usually lawson)

 

First, download the latest DSP jar file from InforXtreme.

It is best practice to back up your ldap instance before you begin the install.

On the server of the SSO application, open a command prompt as administrator.  Navigate to the directory where you saved the DSP install file.

Type command java -jar <DSP file>.jar.  This will open the install wizard.

Enter a new configuration passkey.  NOTE that if you are updating an installed DSP, you will need to know what passkey was used to install it.

 

Give your DSP instance a meaningful name

 

Set the location where you want the install files saved, and set the java location.

 

Mingle DSP install is a different process not addressed in this article.

 

Provide the FQDN of your LSF server.  The standard and secure ports can be found in your LSF install log.  Enter the password that you use to run ssoconfig.

 

Enter account information with administrative privileges in Lawson

 

Enter the appropriate values for the server that hosts your SSO application

 

Click Install

 

Update the JVM custom properties with the new install information (if necessary)

 

Install or update your security application in WebSphere.  The install file lawsec.ear can be found in <DSP install directory/jar/secondary

 

Run a smoke test against the new DSP install at https://<application base url>:<port>/sso/SSOConfig

Here is a list of known IPA errors and their solutions as provided by Infor.

1. Email attachment does not exist – Attachment: Drive:/Path/To/File/filename.ext does not exist.Solution:
   When adding attachments to a IPA email node, you must first ensure the file you wish to attach resides on the Landmark Environment Server.• If the file exists in LASYSDIR/LPS/emailattachments, simply list the file by filename.ext
   • If the file exists in any other Landmark Server Directory, list the file by it’s full absolute directory path
   • If you are using Multi-tenant Cloud, the file needs to be added PfiFileStorage, list the file by its full name in PfiFileStorage 
2. SSOCfgInfoServlet was not successful – Login error: com.lawson.security.authen.httpclient.LawsonHttpClientException: Login: The call to SSOCfgInfoServlet was not successfulImportant to note that any failing path connecting from IPA to LSF server can throw an identical error as stated above. The solution below should only be applied if the following can be seen in WebSphere’s system.out log:REQUIRED SUBSEQUENT ERRORjava.net.UnknownHostException: <server>

   at java.net.InetAddress.getAllbyName0(InetAddress.java:1302)

   Solution: Try adjusting the java.security file to disable caching while troubleshooting the problem on the DNS server. In order to modify this value, open JAVA_HOME/jre/lib/security/java.security and change the networkaddress.cache.ttl line to:

   networkaddress.cache.ttl=0

3. IPA Designer: Lawson Query Builder – Error Generating Process Query String

This error can pop up upon pressing “Build” in IPA Designer LawsonQuery node.

Solution: This silly error may be caused by using a IPA variable (such as <!appProdline>) for your dataarea in the query string. Instead, just remove the variable and type in the dataarea manually instead.

Before: PROD=<!appProdline>&FILE=EMPLOYEE&INDEX=EMPSET1&KEY=<!Company>=<!Employee>&FIELD=ADD-ALLOW-AMT;AUTO-DEPOSIT;BIWEEKLY-RATE;COMPANY;EMPLOYEE&OUT=CSV&DELIM=

After:
PROD=lsapps&FILE=EMPLOYEE&INDEX=EMPSET1&KEY=<!Company>=<!Employee>&FIELD=ADD-ALLOW-AMT;AUTO-DEPOSIT;BIWEEKLY-RATE;COMPANY;EMPLOYEE&OUT=CSV&DELIM=

The Data Iterator node is commonly used to loop through records but it can also read a file into IPA. (For more on the Data Iterator Node, visit: https://www.nogalis.com/2017/05/04/ip-designer-series-the-data-iterator-node/)

Based on the responses of seasoned IPA developers on the Infor/Lawson forums, the best way to ‘load’ in a file to an IPA flow is to use a FileAccess node followed by a DataIterator node. This speeds up the flow considerably as the FileAccess node would read the file into memory and then the DataIterator node can use the data from the memory instead of reading and closing the file multiple times.

First ‘load’ or ‘read’ the file into IPA using the FileAccess node. Then set DataIterator to process the Data (and not File) and set the source to be the FileAccess_outputData. This should noticeably improve the performance of the flow as the data is just being loaded into memory once by the FileAccess.