Updating the configuration file

To run the Cluster Setup automation, you will need to add values to the configuration file.

  1. Navigate to $LAWDIR/system.
  2. With a text editor, open the WASMasterConfig.cfg file.
  3. Under Common Configurations, specify this information:
    WAS_CLUSTER_NAME

    Specify the name of the cluster you want to create.

    WAS_DMGR_NAME

    Specify the WebSphere Deployment Manager name.

  4. Under Cluster Setup, specify this information:
    WAS_MEMBER_NAME
    Use one of these options:
    • Specify the name of each cluster member separated by a comma. For example: Clust_App1, Clust_App2.
    • Specify the number of cluster members you want to create and the script will create the names for you. For example: if you specify 3, the script will generate 3 cluster member names.
    WAS_NODE_NAME
    Specify the WebSphere Node name.
    BUS_SECURITY
    Optional. By default, bus security is set to false. If you want to enable bus security, specify true.
    APPLICATION_SERVER_TEMPLATE
    Specify the name of the server that will be used as a basis for first cluster member.
    JVM_CLASSPATH_#

    JVM classpath for the application server where you will deploy Lawson.

    Do not change the existing default values.

    If you need to add an additional value, add a new line using this information as a guideline:

    JVM_CLASSPATH_<new number> = Environment Name+extension

    MESSAGE_STORE_DIRECTORY
    Specify the logging/store path for the message engine. As a best practice, Infor recommends placing the message store under the application server’s directory.

    For example: C:\IBM\WebSphere\AppServer\profiles\AppSrv01\tranlog\CellName\NodeName

    Use this example to update your WASMasterConfig.cfg.

    ##########################################################################################
####################### C O M M O N   C O N F I G U R A T I O N S ########################
##########################################################################################

# WAS Cluster Name e.g. "tip10Cluster"
WAS_CLUSTER_NAME = 

# WAS Dmgr(Deployment manager) name e.g. "Dmgr01"
WAS_DMGR_NAME = Dmgr01
    ##########################################################################################
############################### C L U S T E R   S E T U P ################################
##########################################################################################

# Cluster Members Name e.g. "TIP10_APP1,TIP10_APP2,TIP10_APP3"
# or you can put a digit for the script to automatically generate names 
# e.g. if you put 3, the script will generate 3 cluster members name.
WAS_MEMBER_NAME = 

# Node Name e.g. "PHLSFREL10Node01"
WAS_NODE_NAME = 

# bus Security
BUS_SECURITY =

#this server will be used as a basis for first cluster member
# if no name is passed "default" will be used
APPLICATION_SERVER_TEMPLATE = 

#JVM classpath for the application server where you will deploy Lawson
#for additional value just increase the number and create one
#e.g. JVM_CLASSPATH_<new number> = Environment Name + extension 
JVM_CLASSPATH_1 = WAS_HOME+\plugins\javax.j2ee.jta.jar
JVM_CLASSPATH_2 = WAS_HOME+\plugins\javax.j2ee.servlet.jar
JVM_CLASSPATH_3 = WAS_HOME+\plugins\javax.j2ee.jsp.jar
JVM_CLASSPATH_4 = WAS_HOME+\plugins\javax.j2ee.el.jar
JVM_CLASSPATH_5 = GENDIR+\java\jar\lawsonrt.jar
JVM_CLASSPATH_6 = GENDIR+\java\jar\lawsec.jar
JVM_CLASSPATH_7 = GENDIR+\java\thirdParty\secLS.jar
JVM_CLASSPATH_8 = LAWDIR+\system

# Message Store Paths
# Since each messaging engine is associated with an application server, it would make sense to place the
# logging/store of the messaging engine under the application server’s directory.
# e.g.  C:\sandbox\tools\IBM\WebSphere\AppServer\profiles\AppSrv01\tranlog\CellName\NodeName
MESSAGE_STORE_DIRECTORY =
  5. Save and close the file. Do not move the file or rename it.