Running the configureDSCluster script to create a cluster

After you have augmented the default management profile, you can run the script that configures Rule Execution Server as a WebSphere® Application Server cluster.

1. Edit the configureDSCluster.properties file to set the cluster name and database values.

   You can find this file in the profiles/Dmgr01/bin/rules/ directory, where Dmgr01 is the name of the deployment manager profile. The configuration properties must contain values for the following keys:

   wodm.dsrules.clusterName

   The value can be the name of an existing cluster. If no cluster exists yet, a cluster is created. The default name is DecisionServerCluster.

   wodm.dsrules.rulesMgrServerName

   The name of the server that hosts the Rule Execution Server console. For example: RulesMgrSrv.

   wodm.virtualhost.name

   The target virtual host where the applications will be installed. The default is default_host.

   wodm.dsrules.db.type

   The database type: DB2®, Oracle, or MSQL. The default is DB2.

   wodm.dsrules.db.jdbcDriverPath

   The path to the JDBC drivers. Separate the driver names with a colon (;). For example: C:/drivers/db2jcc4.jar;C:/drivers/db2jcc_license_cu.jar;

   wodm.dsrules.db.name

   The name of the database. For example: MyDB.

   wodm.dsrules.db.hostname

   The name of the host where the database is hosted: For example: MyDB_server.

   wodm.dsrules.db.port

   The port number to establish the connection to the database.

   wodm.dsrules.db.user

   The user name to connect to the database. For example: db_user1.

   wodm.dsrules.db.password

   The password for the user to connect to the database. For example: db_user1_pwd.

2. Optional: Assign roles to users and groups.
   To set up permissions for Rule Execution Server and for testing and simulation, create two text files under the profileTemplates/rules/actions/scripts/was directory. The file names must match the application names that are used in the script: jrules-res-management.roles and jrules-ssp.roles. The file contents must respect the following format:

   #custom roles if needed (values separated by comma)
   custom_roles=<custom_role1>,<custom_role2>
   #list of users mapped with a role (values separated by pipe |)
   <role_name>.users=<user1>|<user2>
   #groups mapped with a role (values separated by pipe |)
   <role_name>.groups=<group1>|<group2>

   In the examples, the group names match the role names, but you can name your groups differently.

   For example:

   Configure the default users and dedicated groups for Rule Execution Server in jrules-res-management.roles:

   custom_roles=mycustomrole
   resAdministrators.users=resAdmin
   resDeployers.users=resAdmin|resDeploy
   resMonitors.users=resAdmin|resDeploy|resMonitor
   mycustomrole.users=Bill Smith
   resAdministrators.groups=resAdministrators
   resDeployers.groups=resDeployers
   resMonitors.groups=resMonitors
   mycustomrole.groups=mycustomgroup

   Configure the default users and dedicated groups for the testing and simulation feature in jrules-ssp.roles:

   resAdministrators.users=resAdmin
   resDeployers.users=resAdmin|resDeploy
   resAdministrators.groups=resAdministrators
   resDeployers.groups=resDeployers

3. Navigate to the profiles/Dmgr01/bin directory and start the configureDSCluster script with the required parameters.

   The script interpreter calls bash. If bash is not available on your system, an error is raised with the message Bad interpreter.

   The command line syntax is: configureDSCluster[.bat|.sh|.ksh] -ParameterName1 parameterValue1 -ParameterName2 parameterValue2 ... . If you make a mistake, such as a missing parameter or a wrong node name, you can execute the script again.

   • On Windows:

     <WAS_InstallDir>\profiles\Dmgr01\bin\configureDSCluster.bat -dmgrAdminUsername websphere -dmgrAdminPassword websphere -clusterPropertiesFile <WAS_InstallDir>\profiles\Dmgr01\bin\rules\configureDSCluster.properties -createNode -targetNodeName DecisionServerNode01
      -dmgrHostName localhost -dmgrPort 8879

   • On UNIX:

     <WAS_InstallDir>/profiles/Dmgr01/bin/configureDSCluster.sh -dmgrAdminUsername websphere -dmgrAdminPassword websphere -clusterPropertiesFile <WAS_InstallDir>/profiles/Dmgr01/bin/rules/configureDSCluster.properties -createNode -targetNodeName DecisionServerNode01
      -dmgrHostName localhost -dmgrPort 8879

   • On HP-UX:

     <WAS_InstallDir>/profiles/Dmgr01/bin/configureDSCluster.ksh -dmgrAdminUsername websphere -dmgrAdminPassword websphere -clusterPropertiesFile <WAS_InstallDir>/profiles/Dmgr01/bin/rules/configureDSCluster.properties -createNode -targetNodeName DecisionServerNode01
      -dmgrHostName localhost -dmgrPort 8879

   Table 1. Cluster configuration parameters

   Parameter name	Required	Description
   -dmgrAdminUsername	Mandatory	The WebSphere Application Server administrator’s user identifier
   -dmgrAdminPassword	Mandatory	The WebSphere Application Server administrator’s password.
   -clusterPropertiesFile	Mandatory	The path to the properties file.
   -uninstall	Optional	Removes all the applications and resources from the cluster. The cluster itself is not removed because it might contain other applications. See Uninstalling Rule Execution Server from a cluster.
   -createNode	Optional	If you specify this parameter, the script creates a default node profile with the name set in the -targetNodeName parameter.
   -targetNodeName	Optional	By default, the name of the target installation node is set to RulesNode01.
   -dmgrHostName	Optional	Use this parameter to specify the name of the host on which the deployment manager is located. This parameter is mandatory if you create the target node by setting the -targetNodeName parameter.
   -dmgrPort	Optional	The SOAP TCP port of the deployment manager. By default, 8879.