Grid Service Configuration for Landmark / Infor Lawson System Foundation Environments

To enable the most efficient use of your system's resources when a Landmark Environment is connected to an Infor Lawson System Foundation Environment and the Landmark Environment is set up as primary, you should make adjustments to the default Grid configuration. For example, when Landmark and Infor Lawson System Foundation are connected by using the same authentication service with the Landmark authentication service set as the primary one, on occasion users from both environments may attempt to access functionality that is processed through the same Landmark Grid node. If the Grid is not configured to handle this situation, users in one of the systems may experience severe performance issues.

More specifically, if a user of a Landmark application has initiated a resource-intensive task and at the same time Infor Lawson System Foundation users are attempting to log in to the system, the latter users may not be able to log in. This is because the authentication process for both Landmark and Infor Lawson System Foundation users in this scenario is through Landmark. If the authentication process requires the same Grid node as the resource-intensive process initiated by a Landmark application user, the authentication process may be delayed unacceptably.

As a general rule, to avoid this issue, you should monitor your system to identify occasions when performance degrades due to resource limitations. You can then adjust the Grid configuration to use more JVMs for one or more nodes, allot more memory to nodes, and set other parameters for individual nodes. For more information on Grid configuration, see Configuring the Grid.

In the specific case of performance issues with the authentication process, you can try the following recommendations for the LmrkInteractiveExecutor node type. This is the node type that handles business logic processing in Landmark for interactive (as opposed to batch) processes.

Grid Property Settings	Description
Max Heap	This recommendation of 4096 MB assumes your system has sufficient resources to allow a maximum heap size this large.
Throttling Memory Threshold	The throttle threshold is the percentage of the maximum heap size to use to determine when the JVM should go off-line to allow for memory usage recovery.

Binding Settings	Description
Initial node count	An initial node count of 2 creates two JVMs for the LmrkInteractiveExecutor node type. Two JVMs lessens that chance that resource-intensive tasks will prevent other processes, such as authentication, from having access to available resources.