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.
Before you begin
Before creating clusters and configuring
the IBM Business Monitor components, ensure that you have performed
the following tasks:
- You have installed IBM Business Monitor.
- You have created the IBM Business Monitor deployment manager profile or augmented an existing deployment manager profile with IBM Business Monitor.
- You have created the MONITOR database.
- You have started the deployment manager.
- You have created and federated at least one IBM Business Monitor custom profile or augmented an existing custom profile with IBM Business Monitor.
- You have started the custom profile or profiles.
If you are using Solaris, you must additionally
update the app_server_root/bin/wsadmin.sh file
to set the MaxPermSize Java virtual machine (JVM)
parameter to an appropriate value. Although tests have shown that
a value of 256M is sufficient for the monConfig.sh script
to run, your system resources and requirements might require you to
set a different MaxPermSize value. In the wsadmin.sh file,
modify the PERF_JVM_OPTIONS line to set the MaxPermSize value,
as shown in the following example:
PERF_JVM_OPTIONS="-Xms256m -Xmx256m -XX:MaxPermSize=256m" ;;
About this task
These files are formed of name-value pairs of configuration settings for the IBM Business Monitor clusters and cluster members to be created. You can customize a copy of the properties file with your required settings to create a deployment environment with a single cluster topology or three cluster topology.
Procedure
Results
The deployment environment is created with a single cluster or three clusters to support the deployment of applications and the messaging and support infrastructures.