Moving Landmark from a Non-Clustered to a Clustered Setup

Use this procedure if you originally deployed Landmark to a non-clustered WebSphere application server and you want to move it to a WebSphere cluster. The advantage of having Landmark in a cluster is that you can create multiple application servers for Landmark and thus benefit from vertical scaling. This procedure assumes that you will also set up your web server for load balancing.

To move Landmark to a Clustered Setup

In the WebSphere administrative console, create the cluster. Accept defaults, supply name. Add a server using the existing app server for Landmark as the template.
1. Navigate to Servers > Clusters > WebSphere application server clusters.
2. Click New.
3. Provide a name for the cluster and click Next.
4. To create the first cluster member, accept the defaults except for the following fields: provide a name, select the "Create the member using an existing application server as a template" radio button, and click Next.
  
  Member name
  
  Specify a name for the first application server.
  
  Select basis for first cluster member
  
  Select the Create the member using an existing application server as a template" radio button and then select your existing Landmark application server as the template.
5. Click Next.
6. To create additional cluster members, provide a name for an application server and click Add Member. Repeat this step until you have created as many additional application servers as you need.
7. Click Next and then, on the Summary page, click Finish.
Change application server references in Landmark files. Change the entries in install.cfg for a couple of things from the name of the Landmark node to the name of the cluster.
1. In your Landmark file system, navigate to $LASYSDIR.
2. Open the install.cfg file in a text editor and change the value of the WS70_APP_SVR parameter to the name of the cluster you created. Then save the file.
3. In your Landmark file system, navigate to $LACFGDIR.
4. Open the environment.properties file in a text editor and change the value of the com.lawson.was.application-server parameter to the name of the cluster you created.
5. Add entries to the environment.properties file that set the initial and maximum memory sizes for the JVM for each of your new application servers in the cluster. The format of the entries is as follows:
  
  com.lawson.was.applicationServerName.jvm-init-mem=NNNN
  
  com.lawson.was.applicationServerName.jvm-max-mem=NNNN
  
  For example:
  
  com.lawson.was.server1.jvm-init-mem=3072
  
  com.lawson.was.server1.jvm-max-mem=6144
  
  com.lawson.was.server2.jvm-init-mem=3072
  
  com.lawson.was.server2.jvm-max-mem=6144
6. Save your changes to the environment.properties file.
Run adminlaw.
Deploy the Landmark environment to the application servers. At the Landmark command line, type

deployenvironment

Note:
At this point, you may want to start Landmark (startlaw) and check that the Environment runs correctly. If so, then re-run adminlaw before deploying your Landmark applications.
Deploy your Landmark applications to the application servers. For each application, at the Landmark command line, type

package4j2ee dataArea applicationName

deploy2j2ee dataArea applicationName
For example:

package4j2ee globalledger iefinapp

deploy2j2ee globalledger iefinapp
Start Landmark. At the command line, type

startlaw
Generate and propagate plug-ins, restart your web server(s), and restart WebSphere.
Verify the system using the standard smoke tests from the Infor Landmark Technology Installation Guide.