Landmark Grid Node Types and Application Modules
Lawson delivers for Landmark a set of application modules and node types. Each node type represents a set of one or more application modules. Depending on the grid profile option you chose during Landmark installation, you will have one of several sets of bindings that define the node types for the grid host, and thus indicate how many nodes to start with which application modules.
All grid configurations for Landmark must include the following nodes to be running:
-
ManageLandmark
This node provides an interface point between Landmark-supplied commands and the grid. Examples of Landmark commands that execute partially or in full via ManageLandmark include
startlaw,stoplaw,adminlaw, andmanagegrid. -
Lads
This provides coordination and synchronization services for database structure change management as well as a point from which a client copy of the Infor Rich Client can be installed onto a client machine.
-
Lase
This hosts the Landmark security server process providing security authentication and authorization services.
-
A Landmark application router node
Optionally, if a Landmark application uses the integrated analytics feature, another node will be required to host the analytic cube engine. This node is configured during the application installation process through the managegrid enableanalytics command. Running this command creates a grid binding named LmrkLEA-dataAreaName. This binding executes the LmrkCalc node type, which includes the GridCalc module.
In addition to these nodes, a Landmark grid will have nodes for the grid registry, the grid administrative router, the grid agent, and the DSSOSessionProvider (which supports login processing for the Infor Rich Client). Your system will then have more nodes based on the profile specified when you installed Landmark. Over time, you may also modify the binding configuration and thus your system will contain perhaps different nodes, a different number of nodes, and different properties for the nodes.
Developer Grid Profile
This profile is targeted at 32-bit Java systems where available memory is constrained.
-
Landmark Nodes - 1
-
Maximum Heap Memory - 4 GB
-
Total Grid Nodes - 9
Minimal Grid Profile
This profile is essentially the same as the Developer profile.
-
Landmark Nodes - 1
-
Maximum Heap Memory - 4 GB
-
Total Grid Nodes - 9
Small Grid Profile
This profile represents the starting point for a production system at a smaller customer site. It assumes the system is 64-bit Java.
-
Landmark Nodes - 4
-
Maximum Heap Memory for Landmark Nodes - 13 GB
The memory settings for the nodes range from 1 GB to 4 GB.
-
Total Grid Nodes - 12
| Binding Name/Node Type | Application Module | Description |
|---|---|---|
| LmrkInteractiveS/LmrkInteractiveExecutor | BLExecutor | General business logic execution support |
| LmrkBLDoc/LmrkBLDoc |
BatchExecutor Document |
Business logic execution support for general usage as well as list retrieval and background set action processing. This also includes report document creation support. |
| LPA/LPA | LPA | Process automation engine. |
| Async/Async | AsyncStandalone | Background processing scheduler. |
Medium Grid Profile
his profile represents the starting point for a production system at a mid-sized customer site. It assumes the system is 64-bit Java.
-
Landmark Nodes - 5
-
Maximum Heap Memory for Landmark Nodes - 20 GB
The memory settings for the nodes range from 1 GB to 5 GB.
-
Total Grid Nodes - 13
| Binding Name/Node Type | Application Module | Description |
|---|---|---|
| LmrkInteractiveM/LmrkInteractiveExecutor | BLExecutor | General business logic execution support, but defined with two LmrkInteractiveM nodes starting from the same binding. |
| LmrkBkBLDoc/LmrkBkBLDoc |
BatchExecutor Document |
Business logic execution support for general usage as well as list retrieval and background set action processing. This also includes report document creation support. |
| LPA/LPA | LPA | Process automation engine. |
| Async/Async | AsyncStandalone | Background processing scheduler. |
Large Grid Profile
This profile represents the starting point for a production system at an enterprise scale customer site. It assumes the system is 64-bit Java.
-
Landmark Nodes - 6
-
Maximum Heap Memory for Landmark Nodes - 23 GB
The memory settings for the nodes range from 1 GB to 6 GB.
-
Total Grid Nodes - 14
| Binding Name/Node Type | Application Module | Description |
|---|---|---|
| LmrkInteractiveL/LmrkInteractiveExecutor | BLExecutor | General business logic execution support with maximum heap size of 6 GB, and defined with two LmrkInteractiveL nodes starting from the same binding. |
| LmrkListBatch/LmrkListBatchExecutor | BatchExecutor | Business logic execution support for list retrieval and background set action processing with maximum heap size of 4 GB. |
| LmrkDocument/LmrkDocument | Document | Report document creation services. |
| LPA/LPA | LPA | Process automation engine. |
| Async/Async | AsyncStandalone | Background processing scheduler. |
Procurement Grid Profile
This profile is useful if you have a large data volume, such as a high number of order lines being created in your Infor Lawson Supply Chain Management Landmark application and sent to Infor Lawson System Foundation. Be sure you have sufficient system resources for the heap sizes used in this profile.
-
Landmark Nodes - 6
-
Maximum Heap Memory for Landmark Nodes - 31 GB
The memory settings for the nodes range from 1 GB to 8 GB.
-
Total Grid Nodes - 14
| Binding Name/Node Type | Application Module | Description |
|---|---|---|
| LmrkInteractiveP/LmrkInteractiveExecutor | BLExecutor | General business logic execution support with maximum heap size of 8 GB, and defined with two LmrkInteractiveL nodes starting from the same binding. |
| LmrkListBatchP/LmrkListBatchExecutor | BatchExecutor | Business logic execution support for list retrieval and background set action processing with maximum heap size of 8 GB. |
| LmrkDocument/LmrkDocument | Document | Report document creation services. |
| LPA/LPA | LPA | Process automation engine. |
| Async/Async | AsyncStandalone | Background processing scheduler. |
Additional Bindings
There are two additional binding definitions created for all configuration profiles. These are LmrkProfiler and TraceLogger. They are configured to be available, but are not started by default and can be manually started if needed.