This guide explains how to modify settings for Lawson Portal options, affecting how applications display on your computer.

  1. Open the Navigation Menu and from the General group, select User Options.

  2. From the General tab, make the following selections:
    Option Meaning
    Locale The language that Lawson Portal uses. Default is U.S. English.
    Note: After changing the Locale, you must refresh the page for the change to take effect.
    Note: This option is not available to privileged online-only users.
    Data Area A defined storage place within a Lawson product line.
    A product line can have one or more data areas, allowing you to separate access to different sets of data within the product line. If you have more than one and are unsure which to select, consult your system administrator.
    Note: After changing the Data Area, you must refresh the page for the change to take effect.
    Value Separator Defines the character used to separate values in CSV files. The options are comma, tab, or semicolon.
    Default Report Type Select the default report format for Lawson system reports. Options include Text, PDF, and LSR.
    Note: For correct rendering of all data, only the LSR output format is enabled on the Arabic platform.
    See: Enabling Infor Lawson Smart Reports (Optional) in Lawson Administration: Jobs and Reports.
    Default Printer The default printer for Lawson system reports. Available printer names and locations are created by your system administrator. The selected printer name will be shown on the right of the drop-down list.
    Note: This option is not available to privileged online-only users.
    Tab Recovery Controls how tabs from your previous session are recovered: Ask (default): Lawson will prompt you to recover or start fresh when the system loads. Always: Automatically recover tabs from the last session. Never: Always start fresh without recovering tabs. Note: Tab Recovery saves the last session per browser, but data from the session is not saved.
    Show Product Line in Page Header Displays the current product line after the tab title. This option is disabled by default.
    Auto Select Required Fields Automatically prompts available data when processing a record.
    Display Field Help Shows help for a field when it is in focus. Useful for new users unfamiliar with the applications.
    Allow Logging to Console Logs browser console information related to Lawson Portal requests, including context messages and workstation state.
    Use Data Entry Field Advance Automatically moves the cursor to the next field without needing to click or press Tab.
    Note: Form customizations can affect the behavior. For example, if fields have been reordered in Design Studio, Lawson follows the original order when moving to the next field.
    Lawson Portal advances the cursor based on field type: Text and non-decimal numeric fields: Cursor advances when the maximum number of characters is reached.  Signed fields: For decimal signed fields, the cursor moves when the maximum number of decimal places is entered.
    Advance on 6-Digit Date Entry Indicates that a date entry is complete after typing six digits (e.g., “093024” for 09/30/2024). This option is only available if Use Data Entry Field Advance is enabled.
    Enable Accessibility Behaviors Enables various usability features designed for assistive technologies.
    Use Client Machine Time Zone When enabled, Lawson Portal uses the time zone of the client machine when submitting jobs and displaying timestamps in Print Manager and Job Schedule.
    Frequent and Recent Forms Enables the use of frequent and recent forms on the Lawson Portal homepage and navigation menu.
    Click Clear data to reset the data.
    Default Token View Selects the default view for applications: Form View: Full field layout, requiring a key field search for data display. Ideal for frequent data entry. List View: Displays application records in a list. You can apply filters, create custom views, and select records for inquiry. List Mode: A wizard-based mode that guides you through required fields to locate and display records.
    List View Configure settings for List View: Number of Records: Maximum number of records displayed in List View. Maximum List View Edits: Maximum records that can be edited in a single transaction.
    Note: This option is not available to users without edit permissions. You can also exclude forms from List View by entering form tokens, separated by a semicolon.
    List Mode Sets the maximum number of records displayed in List Mode.
    Highlight Key and Required Fields Highlights required or key fields with a color swatch, matching the user’s accent color.
    Shrink Forms to Fit on Screen Shrinks forms to fit the screen without scrolling. Supported on Chrome, Firefox, Safari, and Microsoft Edge browsers.
  3. After making your selections, click OK to save your changes.

 

When running Lawson Security Administrator (LSA), you may get stuck on the authentication screen even after going through the two-factor sign-in. Here is how to resolve this issue.

 

Run LSA as Admin and login

Ping ID Authenticates

 

Script Error pops up, clicking yes, no or closing leads to same result:

Doesn’t connect after:

LSA Logging gave me these results 9/20 when last tested (logs not updating now):

LSA Version 10.0.3.01065

 

Installing LSA Version 10.0.3.01069 Resolves this issue. And that’s it!

IPD  enables you to debug your processes. To activate the Debug view, go to the Infor Process Designer menu bar and select Window > Show View > Other

From there select Infor Process > Debug and click on OK.

The Debugger feature set includes:

  • Breakpoint management- can be enabled for any activity node within a process, and causes a running process to pause at the point before the specified activity node. When the process pauses, process variables can be examined and/or modified. Process execution can be resumed at the breakpoint, or at any other activity node if desired.

To set this up, right mouse click on the node to debug and select Debug

The Run to this activity breakpoint is temporary and only valid for the current execution of the process. A “run to” breakpoint can be useful when you want to pause at a specific activity node during the current execution, but you do not want it to stay in effect for any subsequent executions. All temporary breakpoints are cleared before a process starts execution.

This feature is available only when running the process locally.

  • Process execution controls

The run process control starts the execution of a process and is available if the process is currently not running or paused. The Run Mode option gives you the option to run the process either locally or on the server. The flow can be run on the server from the designer and provide you with the status and log information.

Specify Input data can be used to pass data to a process. The data will be added to the workunit once the workunit has been created. You can select from these options when specifying the input data:

  • No input data: Select this option if you do not want to pass any specific data to the process.
  • Use data from Workunit: You must specify the workunit number. The process will fetch the input data from that workunit and use the same data in the current process. If the workunit or input data does not exist, then the input data will be null.
  • Use connector: You can select between two options. The first one is Specify input data where you can specify the data that you want to pass to the process. The second is Input data file where the data will be read from the given file and be used in the process.
  • Runtime variable examination and modification

This feature is available only when running the process locally (that is, Run Mode is set to Local).

Once a running process is paused at an activity node, the current value of variables in the process can be examined and modified if needed.

The Debug view shows a list of currently running processes. The variables accessible to the activity node at the pause point is shown, organized by variable category and activity node. Selecting a variable shows its current value, and a new value can be specified.

These 5 tips could make applying patches that much less stressful and are also good practice in general.

 

Tip 1: Check existing patch logs to see if a patch has already been applied previously and current versioning. This is good to check after a patch has been applied as well.

These logs can be found and generated here in LID:

perl %GENDIR%\bin\patches_installed_report <productline>

perl %GENDIR%\bin\source_versions_report <productline>

 

Tip 2: Restart the LSF server (or services) to ensure no processes are being held up and when it boots up, turn off Websphere LSF Appserver service before applying a patch to ensure users cannot log on, especially if patch needs to be applied during or close to work hours.

 

Tip 3: Run dbdef command to make sure there is a connection to the database before patching

 

Tip 4: When activating or staging multiple patches, run this command to speed up the post compile process:

qcontrol -jlocal,4  – This will set the servers cores to 4 when processing form compiles. Set it back to 2 when done. You can also check the status of the compiled jobs with command: qstatus | head -5

 

Tip 5: If a Plus dictionary is created after patching, its typically good practice to compile the entire product line with the command: cobcmp (be aware this can take up to 20-30 minutes to complete, tip 4 helps with this). This ensures that all programs are functioning correctly before passed to testers.

 

Bonus Tip: Verify security is on before sent to the testers!  Hope these were helpful.

 

If you found this article helpful, Nogalis provides managed services and expert technical resources to assist with Lawson patching and system maintenance. If applying patches feels overwhelming or time-consuming, our team can simplify the process by managing everything from version checks to database connectivity and post-compile optimizations. Let us help ensure your patches are applied efficiently and your system is running smoothly. Contact us to learn more about how we can support your Lawson environment.

The message “lase_server logging issue – Invalid message is received and size” indicates that an error message that is too large has been sent from the security server.

Example full message text

default.SEVERE server.SecurityEventHandler.run(): SecurityEventHandler #816 got exception. com.lawson.security.server.LawsonNetException: Got exception while reading from connection Socket[addr=/127.0.0.1,port=64706,localport=450000].

Stack Trace : com.lawson.security.server.LawsonNetException: Got exception while reading from connection Socket[addr=/127.0.0.1,port=6406,localport=50000].

at com.lawson.security.server.AbstractDefaultEventSource.read(AbstractDefaultEventSource.java:339)

at com.lawson.lawsec.server.SecurityEventHandler.run(SecurityEventHandler.java:151)

Caused by: java.io.IOException: Invalid message is received and size:300095616

at com.lawson.security.server.AbstractDefaultEventSource.readMsg(AbstractDefaultEventSource.java:351)

at com.lawson.security.server.AbstractDefaultEventSource.read(AbstractDefaultEventSource.java:352)

 

Resolution

The parameter server.readMsgMaxSize must be added to lsservice.properties.

The MsgMaxSize parameter ensures that a logging message that occurs when a vulnerability scan is run does not become so large that it causes the system to hang. The parameter catches very large messages and replaces them with shorter sample messages.

Perform these steps to add the parameter.

  1. Stop the Infor environment and the application server.
  2. Open the lsservice.properties file for editing.
    On Landmark, the location is: LASYSDIR/lsservice.properties
    On LSF, the location is: LAWDIR/system/lsservice.properties
  3. Add the parameter server.readMsgMaxSize=[size number in Bytes] to the end of the file. The default size is 20MB. Infor recommends not setting the size larger than 40MB.
    Example: server.readMsgMaxSize=20
  4. Restart the Infor environment and the application server.

 

Note that the below information is reproducible on a cloud client via jumpbox or local PC connected to VPN.

 

If your Lawson Security Administrator is stuck on authenticating after two-factor sign-in, follow these steps to reproduce and get a solution (this is to make sure you’re experiencing the same issue):

Run LSA as Admin and login.

Ping ID or Two-factor equivalent Authenticates

Script Error will pop up. Clicking yes, no or closing the window leads to the same result:

Doesn’t connect after, stuck on Authenticating.

This occurred on LSA Version 10.0.3.01065 in a Infor Cloud Environment.

 

Resolution:

Installing LSA Version 10.0.3.01069 Resolves issue and LSA is able to authenticate after the two-factor.

 

Follow the steps below to add a new context app in Infor OS Portal.  In this example, we will enable the app for Infor Lawson S3.

Log into Infor Portal and Click on User Settings > Admin Settings

Go to the Manage Context / Utility Apps tab and select “ADD CONTEXT/UTILITY APP”

Enter a Type, Name, Description, and URL.  Click Save.

 

Now, add the application(s) that will be using this context app.  At the bottom of the screen, select the Applications tab and select “Add/Remove Applications”.

Select the application(s) and click Done

Be sure to Enable to application and then click “Save”

Your context app now shows up in the right side menu

 

Need an Access Lawson database to reside on the desktop of select users without having to relink all the tables each time?

If so, see the below query for the DSN-less connection with a function to relink all the tables and pass-through queries. This also just works for databases in general. Good luck!

 



 

If this process seems too complex or time-consuming, Nogalis offers expert managed services to help you manage and optimize your Lawson databases, including handling table linking and other database configurations. Whether you’re looking to simplify data management across multiple machines or improve overall system performance, our team can provide the support you need—without the overhead of a full-time, in-house staff. Contact us to learn more about how we can assist with your Lawson environment.

This article will give you all the information you need to know about the Infor OS decommission, as well as what you will need to migrate from Infor OS on-prem to Infor LTR on-prem.

What is happening?

Infor OS and Infor OS Lite on-premises are moving to sustaining maintenance on March 31, 2025.  Sustaining maintenance means that there will be no new patches, updates, or fixes for Infor OS.  The pre-existing patches and documentation will remain available.

Reason for the Change

On-premises Infor OS installations are currently running on outdated software components, including outdated versions of Windows, Java, SQL Server, and .Net Framework.  The new product, Infor LTR, will allow all for all of these components to be upgrade to newer and more secure versions.

What are my Options?

On-premises customers have three options for handling this change:

  • Purchase a new MT Infor OS license tier (SaaS)
    • This is a cloud offering from Infor that would create a hybrid environment for clients. Infor OS would run in the cloud, and can still be used for SSO authentication, and your remaining Infor applications could stay on-prem.
  • Upgrade to Infor LTR
  • Take no action and continue to use Infor OS (this contains risks)

What are the Risks of Staying on Infor OS?

Keeping Infor OS can cause your organization to miss out on important security updates.  It also would require your organization to maintain an application on outdated technology, which can be a security risk.

What is Infor LTR?

Infor LTR is a core technology runtime service, that is a “wrapper” for Infor applications.  It serves as a single hub where users can log into one URL and then access all their Infor applications from a menu.  Infor LTR will be supported until at least 2029.

How to Upgrade

To upgrade from Infor OS to Infor LTR, it is possible to do an in-place upgrade procedure.  For a one-step upgrade, you must currently be on Infor OS 2021.12 or higher.  If you’re not on a compatible version of Infor OS, you’ll need to first upgrade Infor OS to one of those versions, and then you can upgrade to Infor LTR.

The upgrade process has the exact same look & feel, and the same installer as Infor OS, so if you have previously done an Infor OS upgrade, you will not have any learning curve.

Server & Compatibility Specifications

Before starting any kind of Infor upgrade, please first read the installer document for the exact specifications.  As of the writing of this article, these are the specifications for Infor LTR:

  • Microsoft SQL Server 2022, 2019, or 2017
  • Windows 2022 or 2019
  • .NET Framework 4.8
  • AWS Corretto JDK 17 (Infor LTR requires a very specific minor version, so be sure to check your documentation before downloading)
  • Minimum Hardware
    • 4 CPU Cores*
    • 32 GB of RAM*
    • Install drive of 50GB+
    • Data/content drive of 300GB+

*NOTE: These are minimum hardware recommendations.  If you are going to use Infor LTR for SSO authentication, it is recommended that you increase the CPU cores and RAM.

Using Infor LTR with Web Applications

Infor LTR offers the same Infor web application utilities as Infor OS.  You can set up menu widgets for applications such as Lawson, LBI, and MSCM.  You can still use the direct URL to access these applications.  Infor LTR is not required the access your Infor web apps, but it is required for compliance with your Infor licensing.  Infor LTR is required if you want your Infor applications to authenticate using an identity provider other than ADFS.

Here are some basic screenshots of setting up and application in Infor LTR:

Infor LTR as STS

Infor LTR can be used as the SSO authentication application for all your Infor web applications.  You can authenticate using multiple different identity providers (IdP).  For instance, you can configure Infor LTR to authenticate with Azure AD, MS Entra, AD FS, or Okta.

Where do I get Infor LTR?

Check your product downloads under Technology > Infor Local Technology Runtime (LTR).  If you do not see LTR in your product downloads, reach out to your Infor account rep