Creating a deployment environment by using the monConfig script

You can use the monConfig.sh or monConfig.bat script to create a deployment environment for the clusters and servers across which the IBM® Business Monitor components and monitor models can be deployed.

PERF_JVM_OPTIONS="-Xms256m -Xmx256m -XX:MaxPermSize=256m" ;;

1. To create your own properties file for a single cluster topology, make a copy of the monconfig_singleCluster.properties sample file and save it to the current or another location. To create your own properties file for a three cluster topology, make a copy of the monconfig_threeCluster.properties sample file and save it to the current or another location. The sample files are stored in the following directory:
   • app_server_root\scripts.wbm\monConfig
   • app_server_root/scripts.wbm/monConfig
2. Use a text editor to edit the newly created file and customize it with the configuration settings for the clusters and cluster members to be created.

   In the set of properties that are provided at the end of the file, numbers (for example, 1, 2, and 3) are used as identifiers for each cluster and associated cluster member and node, as in clusterName.1.memberName.1.memberNode.1. Although you can replace these numeric values with string values as indicated in the comments, for simplicity, you might prefer to retain the numbers in the property names. You must specify a value for each property. You can also replicate the properties if you want to specify configuration settings for additional cluster members and nodes.

   The following table describes the required values for each property. The # character in the property name represents an identifier such as a number or string, which is used to associate cluster members with a cluster and node.

   Table 1. Entries for defining the clusters and cluster members in the deployment environment

   Property	Description
   clusterName.#	Specify a unique name that identifies the cluster. A clusterName.# entry is required for each cluster to be created, where # is unique for each cluster.
   clusterName.#.capabilities	Specify a value that identifies the cluster type. For a three-cluster topology, a clusterName.#.capabilities property is required for each cluster to be created. The values for the three clusters are application, messaging, and support. For a single-cluster topology, you can specify any of the following values: application, support, or messaging.
   clusterName.#.memberName.#	Specify a name for the application server that you are defining as a cluster member. The name must be unique within the node. A clusterName.#.memberName.# entry is required for each cluster member to be created in a cluster. By default, the workload (or weight) is evenly distributed across all members in a cluster.
   clusterName.#.memberName.#.memberNode.#	Set this value to the name of an existing node on which you want to configure and run the cluster member. A clusterName.#.memberName.#.memberNode.# entry is required to associate each cluster member with a federated node.

   For examples of how you can customize the property names and values for a single and three-cluster topology, see Example: Property settings for creating deployment environments with a single cluster or three clusters.

3. Save and close the properties file.
4. From the command line, change to the following directory where the monConfig script is located:
   • app_server_root\scripts.wbm\monConfig
   • app_server_root/scripts.wbm/monConfig
5. Run monConfig by using the following syntax:
   • monConfig.bat -d dmgr_profile_name -u dmgr_was_admin_username
     -p dmgr_was_admin_password -c directory_path\\customized_monconfig.properties

   • monConfig.sh -d dmgr_profile_name -u dmgr_was_admin_username
     -p dmgr_was_admin_password -c /directory_path/customized_monconfig.properties
   where:

   • dmgr_profile_name represents the name of the deployment manager profile.
   • dmgr_was_admin_username represents the user ID for a WebSphere® Application Server administrator.
   • dmgr_was_admin_password represents the password for dmgr_was_admin_username.
   • directory_path/customized_monconfig.properties represents the fully qualified path to your customized properties file for a single or three cluster topology.
     Notes for specifying directory paths in the syntax:

     • Directory paths that have spaces must be enclosed in double quotation marks. You must also use the escaped Windows directory separator (\\).
     • Directory paths that do not have spaces can alternatively use the UNIX directory separator (/).

   For more information about running the monConfig script, and example usage, see monConfig script.

6. Review the log file for the monConfig script, which is written to the following location on the deployment manager node, to confirm that there were no errors:
   • app_server_root\logs\monConfig\monConfig_timestamp_out.log
   • app_server_root/logs/monConfig/monConfig_timestamp_out.log