Repository Loading Options
The Landmark system and its applications require the loading of repositories. These repositories contain the information needed at runtime to present and work with the forms and data. The loading of the repositories occurs by default when users first log in. However, you can modify this behavior. Whether it makes sense do to so for your system depends on several variables, include the available resources of your system, the size of the Landmark applications you use, the number of Landmark applications you use, and whether the loading of the repositories is having a significant impact on your system.
By default, the loading of repositories is done at first use. You have two options for changing this behavior: load the repositories at the startup of a grid node for any product lines that are configured for that grid node, or load the repositories at the startup of the application server for any product lines configured to run for that application server. Note that loading the repositories at the startup of grid nodes strongly impacts scaling scenarios because it could take a very long time to scale out a new node.
Grid Node Repository Loading
To load repositories for a grid node at startup, you set the Auto-preload Repositories property to true. This property is located in the Grid Management tool at Configuration Manager > Applications > yourLandmarkApplication > Edit Properties > Application Defined Properties > Service Execution > Common Settings.
If you set this property to true, the node will not report as ready until the repository for each product line is loaded. Note that loading the repositories at the startup of grid nodes strongly impacts scaling scenarios because it could take a very long time to scale out a new node. To reduce this impact, you can set the Auto-preload Repositories property to true only for the nodes for the LMRKInteractive binding or node type.
Application Server Repository Loading
To load repositories for a application server at startup, you set the com.lawson.ServletStartupListener.enableStartup parameter to true in $LACFGDIR/environment.properties. Note that setting this parameter to true will increase resource use at startup for the application server.