monConfig script

You can use the monConfig.sh or monConfig.bat script to create a deployment environment.

Description

The monConfig script requires input from a properties file that is customized with the configuration values for your deployment environment. Two sample properties files, which you can copy and customize, are provided for a single cluster and three-cluster topology. These files are named monconfig_singleCluster.properties and monconfig_threeCluster.properties. Each sample file is formed of name-value pairs and includes comments to help you complete the values and run the script.

The monConfig script and sample properties files are stored in the following directory where IBM® Business Monitor is installed:

app_server_root\scripts.wbm\monConfig
app_server_root/scripts.wbm/monConfig

Before you run the monConfig script to create the deployment environment, the deployment manager and custom profiles must be created and augmented. The nodes must also be federated into the deployment manager cell, and the deployment manager must be running.

Messages that are related to the running of the monConfig script are recorded in the following file:

app_server_root\logs\monConfig\monConfig_timestamp_out.log
app_server_root/logs/monConfig/monConfig_timestamp_out.log

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

Parameters

-d

Specifies the name of the deployment manager profile.

-u

Specifies a WebSphere® Application Server administrator ID for connecting to the server.

-p

Specifies the password for the user ID.

-c

Specifies the fully qualified path to the properties file that provides input to the monConfig script. The location of the properties file can be the default app_server_root/scripts.wbm/monConfig directory or another directory to which a customized copy of the file was saved.

Notes for specifying directory paths:

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 (/).

Examples

The following example depicts the command-line syntax for creating a deployment environment with a single cluster topology by using a customized copy of the monconfig_singleCluster.properties file, which is saved in the C:\My dir directory.

monConfig.bat -d Dmgr01 -u wsadmin -p mypword -c "C:\\My dir\\monconfig_singleCluster.properties"

The following example depicts the command-line syntax for creating a deployment environment with a three-cluster topology by using a customized copy of the monconfig_threeCluster.properties file, which is saved in the C:\propsfiles directory.

monConfig.bat -d Dmgr01 -u wsadmin -p mypword -c C:/propsfiles/monconfig_threeCluster.properties

For UNIX operating system For Linux operating system The following example depicts the command-line syntax for creating a deployment environment with a three-cluster topology by using a customized copy of the monconfig_threeCluster.properties file, which is saved in the /u/workdir directory.

monConfig.sh -d Dmgr01 -u wsadmin -p mypword -c /u/workdir/monconfig_threeCluster.properties