Disabling Custom Configurations in Infor Web Applications

When troubleshooting issues, you can look at the base UI of Infor applications temporarily without configurations by simply modifying the URL.

It is important to note that the URL addition must go on the Landmark URL (not Ming.le).

To open up the landmark URL, first right-click on any of the menu items on the side panel and select “Open link in new tab”.


Next, you will need to add the text &csk.disableuiconfigs=true to the URL.  Keep in mind that this will only work for the HTML4 web  UI.

That’s all there is to it. You’ve successfully disabled custom configurations in Infor web applications.

How to update certificates in Lawson & Landmark


The process to update web certificates in Lawson & Landmark is virtually the same.  First, change the selected certificate in the “Bindings” on the website.  Restart the World Wide Web Publishing service for the change to take effect.


Some sites use the default WebSphere generated certificate, which auto-renews.  In the event that your organization has configured WebSphere to use an organizational server or wildcard certificate, you will also need to replace that certificate in WebSphere.  First make sure that you have a pfx file stored locally on the server, and that you have the private key for that file.

Open the console manager and navigate to Security > SSL certificate and key management

Select the CellDefaultKeyStore

Select Personal Certificates

Import the new certificate first.

Set the path to where you have saved the file locally, and enter the password.  Click “Get Key File Aliases” to get the certificate information.  Enter a meaningful alias for the certificate.


Select the old certificate and click “Replace…”.

Select the new certificate as the replacement.  Check the boxes to Delete the old certificate and signers.

Follow these same steps for the NodeDefaultKeyStore

Save the changes to the master configuration.

Validate that the Trust Store certs were updated by going into NodeDefaultTrustStore and CellDefaultTrustStore > Signer certificates

Web Server

Copy the new certificate to the Web server.  In console manager, go to Server Types > Web servers.

Click “Plug-in properties” on the right under Additional Properties.  Select “Copy to Web server key store directory”

Generate and propagate the plugins for the web server.

Run an iisreset command, or restart the WWW publishing service.

Your certificates are updated!  You can validate this by going to the web site and looking at the certificate (click the little lock).  You can compare the thumbprint of the website certificate to the new certificate you just added.

WorkUnits Not Running

Problem Description

WorkUnits are not moving forward after a user takes an approve action in the inbasketRoot



The Lawson user was set to have “Run as” disabled. This prevents WorkUnits from successfully updating their PfiQueueTask records to move forward. This occurred as part of a sync that was executed a week before. The ISS SCWebAppAdmin had the Lawson user flagged as run as “No“, when the sync occurred the Landmark Lawson actor was updated. This did not impact the system until a week later when the Landmark system was restarted after applying windows patches.



Change the Lawson user to “run as enabled”

and push that new setting and do a rolling restart on LPA/LmrkAll node to restore functionality.




Landmark Command to get Product Line Status

The listprod -d command shows information about the product line’s status.  The -a option shows information about all product lines.

For Example:

D:\\>listprod -ad
prodline data area Status

gen gen active
prod prod active
test test active
dev dev active


Here are descriptions of the statuses:


The data area has an active dictionary


The data area has a pending dictionary


The data area is being upgraded


The framework version used to build the most recent dictionary for the data area does not match the framework version used to build the most recent “GEN” dictionary


The framework version used to build the active dictionary for the data area does not match the framework version used to build the active “GEN” dictionary


There is no data area configuration file


The data area configuration file is newer than the newest dictionary for the data area


There is no source for the product line


The source for the product line has changed since the newest dictionary for the product line’s data area was built






Tips & Tricks in Configuration Console


Infor’s Configuration Console is a tool that can be used to configure Landmark applications.  It can be used to create new user interface components, or customize existing user interface components.  It is a very useful tool for customizing and enhancing the user experience in Landmark applications.  The tool uses a proprietary language called “Landmark Pattern Language” (LPL).

To get to the Configuration Console in Rich Client, go to Start > Configure > Application.  Or, you can ctrl+shift+click on a Landmark form and click the “Configure” link.



The “empty sheet” button is used throughout Landmark applications to create a new item.  Configuration Console is no exception.  Press this button to create a new configuration.  The save and delete buttons are also intuitive.  When you click the delete button, remember you are deleting the configuration only, not the Infor-delivered component!

In most cases, the “pencil” button indicates editing the configuration LPL directly, and the “Configure” button is for editing the component using a graphical interface.


Configuring menus is pretty straightforward.  Menu items can be deleted, and menus can be hidden from user view.  Note that if a menu is hidden in Configuration Console, this setting takes precedence.  So, if the menu is available via security, it still can’t be viewed.


There are a few options available in configuring pages.  Mostly you can add different fields, including computed fields.  This is one example where the pencil button does not indicate LPL configuration.  On the main configuration screen for a page, the pencil button takes you into the page editor.  At the bottom of that screen, you will have to option to edit the LPL code.

Web Applications

Web Applications have a few options for configuration.  One thing that can be customized is the home landing page for the web application.  Just make sure the page exists in the correct location on your server!

User Fields

User Fields are probably one of the most widely-used configurations available.  The value in a User Field will be saved in the database, so that it can be accessed later in Landmark queries or Spreadsheet Designer.  There are several types of fields available to allow you much flexibility in form customization.

A snapshot is sort of what it sounds like.  It is a copy or a “snapshot” of another field from a related business class.

A condition field is a way to test a condition without having to rewrite code over & over.  A condition field should always return true or false.

A compute fields allows you to do mathematical and date computations on one or more fields in the business class.

Derived fields are the most flexible option, and can be used in place of all of the above field types.  They can be used to convert data types, take substrings, or write more complex bits of code to return the desired information.


Forms are another highly configurable component.  User Fields can be added to forms.  Fields can be hidden, actions can be disabled, and basic checks can be done to customize the flow of a form.  Here are some examples for setting default values on a Form.


Relations are another very useful tool in the Configuration Console arsenal.  They can really open up your forms and other components to allow you to get data from other areas in the application that isn’t readily available.  Relations are a way of relating two business classes on key fields.  A one-to-one relationship requires all of the key fields to be populated.  A one-to-many relationship does not, but be aware that this could return a list of values instead of one value!

These are examples of relating the Candidate business class to the Employee an WorkAssignment business classes.


Actions can be configured with Entrance Rules (things that happen when the action loads), Exit Rules (things that happen when the action is released), and User Parameters.  The User Parameters would follow the action into the next step, such as an IPA approval flow.  Some of the fields on an action can be configured to be required, or not required.


All configuration changes are version and stored each time the configuration is saved.  This means that you can compare current state to any of the previous states to the beginning of the configuration, as well as the base LPL.  This is highly useful, and a great feature!  To get to the history, on the main page of any component, select “Vew History”.  On the left side is the historical configuration.  On the right side is present-day.  You can click the dropdown to select the configuration you want to compare.  If you are ready to go back to that configuration, click the “revert” button.  If you are satisfied, don’t forget to save your changes!

Helpful Links

Infor’s documentation site is a great jumping-off point for learning about Configuration Console and LPL.


Also, check out the webinar that our very own Sr Technical Consultant Desi hosted on this topic!


Tips & Tricks in Configuration Console (April 28th, 9 AM PST)

Learn how to customize the user experience in all your Landmark applications with the Configuration Console.  We’ll show you how to create user fields, how to bring data from a related business class into a form, and more!

When: Thursday April 28, 2022

9:00 AM to 10:00 AM PST

This webinar is free to attend. Register Here

How to tell if Lawson and Landmark are Federated

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 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.

Updating Bouncy Castle after Java Update on Landmark Server

Similar to LSFCT, when Java is updated on the Landmark server, you will need to place the Bouncy Castle provider in the LAW_JAVA_HOME/jre/lib/ext directory.  To get the latest Bouncy Castle release, navigate to  Select the latest release, or the release that corresponds to your version of Java.  Download the signed JAR file.

Stop all the IBM processes and Lawson.  Also, check your task manager for any running java processes.  Kill any java process.  Place the file at LAW_JAVA_HOME/jre/lib/ext.  Start all the services, or reboot the machine.


Updating Bouncy Castle After Websphere Fix Pack

Similar to Lawson System Foundation, when WebSphere is updated in Landmark, the Bouncy Castle provider might also need to be updated.  If this is the case, you will notice an error message similar to the one below in the SSOCfgInfoServlet page.

Also, there will be messages logged in the ssocfginfoservlet.log and security_authen.log.  One of the biggest indicators of a bouncy castle issue is the error “No provider: BC”.

Ssocfginfoservlet.log, security_authen.log

Tue Dec 22 12:10:05.323 CST 2020 – default–1864609923 – L(2) : tid{DEFAULT} lid{13vdos3oj0u2br08s6qstv1pnv}. Error encountered while processing the request. Additional information: {Error decrypting data.

Stack Trace : Error decrypting data.








                at javax.servlet.http.HttpServlet.service(



To update the Bouncy Castle provider, open a Landmark command window, or open a command line window and set the environment variables.  Navigate to WAS_JAVA_HOME, and run the command

java -jar %LAENVDIR%/java/jar/bcinstall.jar

This will put the correct provider file in your java home location.  Then, bounce the application server or reboot the machine.