In Linux and Solaris systems, the BeanConnect Management Console generates the scripts cs-start-all.sh and cs-stop.sh for a BeanConnect proxy every time the communication service's configuration changes. These scripts are generated on saving and make it possible to start or stop the proxy component in a command line.
If all the proxy components are located on the same host then the scripts are located in the directory <Proxy_Home>/shsc, where <Proxy_Home> is the proxy container's home directory.
In contrast, if the openUTM-LU62 Gateway and communication service are running on separate hosts then the script is made available in the MC-CmdHandler which the Management Console uses for the administration of these proxy components. In this case, the script is located in the directory <MC-CmdHandler_Home>/shsc, where <MC-CmdHandler_Home> is the home directory of the MC-CmdHandler.
Starting the communication service
Proceed as follows to start the communication service in a command line:
Open a shell on the host on which the communication service is installed.
Go to the proxy container's home directory (installation on proxy host) or to the MC-CmdHandler's home directory (installation on separate host).
Call the script:
shsc/cs-start-all.sh
Stopping the communication service
Proceed as follows to stop the communication service in a command line:
Open a shell on the host on which the communication service is installed.
Go to the proxy container's home directory (installation on proxy host) or to the MC-CmdHandler's home directory (installation on separate host).
Call the script:
shsc/cs-stop.sh