Availability of command line utility
Global Mailbox offers command line utilities to modify default configuration with Sterling B2B Integrator, configure Cassandra database, configure data centers, scheduler, and storage passphrase.
appConfigUtility
schedulerConfigUtility
storagePassphrase
dbConfigUtility
dcConfigUtility
masterPassphrase
Availability or unavailability of some Global Mailbox components impact the availability of command line utilities. The following sections explain the same in detail:
How Cassandra impacts availability of command line utilities
For command line utilities to function, 50% + 1 number of Cassandra nodes must be available in the data center where you run the command.
For masterPassphrase
, 50% + 1 number of Cassandra nodes must be available in
each data center in the Global Mailbox topology.
How ZooKeeper nodes impact availability of command line utilities
During normal functioning of the Global Mailbox, to use the command line utilities, a minimum of 2 ZooKeeper servers must be operational across the data centers. The ZooKeeper watchdog process must also be running on all ZooKeeper nodes so that ZooKeeper failures can be detected, and recovery with a reduced ensemble can be initiated. While the watchdog is setting up the reduced ensemble, there is a window of time when the utilities cannot be used. However, the utilities can be used after the reduced ensemble is started. If the number of running ZooKeeper servers reduces to 1 or 0, the command line utilities cannot be used until the number of ZooKeeper servers comes back to 2 or more.
How shared disk impacts availability of command line utilities
The command line utility uses the configuration files that are stored in the shared disk. Therefore shared disk must be available in the data center where you run the command.
How replication server impacts the availability of command line utilities
Command line utilities are not dependent on replication server .
How WebSphere MQ impacts command line utilities
Command line utilities are not dependent on WebSphere® MQ.