Chapter 5: Deploying Files and Executing e-Biz Impact Clusters

Using wrapper scripts

Unless otherwise stated, the wrapper scripts referenced in this section replace all command shells and environmental requirements in earlier versions of e-Biz Impact.

The ims wrapper script is used with each major component, including e-Biz Impact and Adaptive Server Anywhere executables. The ims script contains the core of the executable name and associated command line arguments. See “Additional ims commands”.

For example, the binary used to run an e-Biz Impact cluster is ims54cluster. The command line executable is:

ims cluster -cluster.name myCluster

where myCluster is the name of the cluster you want to run.

For Windows NT, you must specify the full executable name:

ims.nt ims54cluster -cluster.name myCluster

You can modify wrapper information to enable execution from different e-Biz Impact instance directories. Wrappers also enable you to seamlessly update e-Biz Impact regardless of version or executable name changes.

Before you execute the cluster, add the wrappers directory, installed by default in Sybase\ImpactServer_5-4\bin on Windows and in /usr/ImpactServer-5_4/bin on UNIX, to your PATH. See “Setting the ims wrapper script path”.

Starting e-Biz Impact on Windows

Enter the following at a DOS command line:

ims cluster -cluster.name <clusterName> -file <fileName>

-cluster.name clusterName

-cluster.mode clusterMode

-cluster.home homeDir

-domain.type domainType

-domain.name domainName

-env.snmp.port snmpPort

-env.trap.port trapPort

-file file name

**Table 5-1: Cluster command arguments**
Argument	Description
cluster.name	The name of the cluster you want to start. The cluster name is the name of the XML file.
cluster.mode	The mode in which to start the cluster. Valid values are cluster and manager. The default mode is cluster.
cluster.home	The directory in which the cluster.XML file exists. Used as the working directory for the cluster.
domain.type	The type of domain under which the cluster runs, providing a logical grouping under which clusters can be run. Domain types might include development, testing, or production. The default value is “Impact.”
domain.name	The name of the domain under which the cluster runs. Along with domain type, provides a logical grouping under which clusters can be run. Domain names might include sales, accounting, or marketing. The default value is “Impact.”
env.snmp.port	The custom SNMP port to which the cluster publishes telemetries. The default SNMP port is 161.
env.trap.port	The custom trap port to which the cluster publishes alerts. The default port is 162.
file	The name of the configuration file in which all or some of the command arguments are defined. The arguments made on the command line take precedence over a value in this file.

To install, configure, remove, stop, and start the cluster as a service on Windows, use the ims clustersvc executable:
```
ims clustersvc -home <homeDir> -file <config file name>
```
where <homeDir> is the directory where the cluster service starts. A cluster.home argument in the configuration file overrides this value. The -file argument indicates the name of the configuration file (for example, myCluster.cfg) where you defined argument values for the ims54cluster binary.
Once installed, use Start | Settings | Control Panel | Administrative Tools | Services to start and stop the service.

Starting e-Biz Impact on UNIX

Enter the following command on one line:
```
ims cluster -cluster.name <clusterName>
```
```
     -shell
```
```
     -mode {cluster | manager}
```
```
     -file xmlcfg
```
- -shell – optional. By default, the cluster runs as a daemon. To run a cluster in the foreground (so the process can be stopped using Ctrl+C, and the cluster exits when the terminal window is closed), use the shell option.
- -mode – determines the role or personality the cluster executable assumes. The options are cluster and manager.
- -file – the name of the cluster’s configuration file.
If you run e-Biz Impact without the -shell flag, use the UNIX kill command with the process ID of the appropriate application to stop the cluster.

View this book as PDF