Configuring an MC-CmdHandler as a service on Linux systems
If you had installed an init.d service for the MC-CmdHandler in a previous version, you should first delete the file /etc/init.d/bcmccmdhandler.sh and all files with the pattern /etc/rc*/*bcmccmdhandler if you no longer need the MC-CmdHandler of the previous version.
If the MC-CmdHandler is to be started as a service then it must be configured.
Call the following script with system administrator authorization inside the installation directory of the container:
shsc/create-bcmccmdhandler-service.sh
This creates a file bcmccmdhandler.version.userid.containername.service in the directory /etc/systemd/system and starts the service. The user ID userid, under which the MC-CmdHandler should run and the installation path of the proxy container are interactively queried by the script. The script uses this to determine the name and version of the container. A separate service must be configured and started for each MC-CmdHandler. Only one MC-CmdHandler Service can be configured on a system for each user ID, container name and version.
The following commands are available to manage the service:
systemctl status bcmccmdhandler.version.userid.containername.service
Display of the current status of the service
systemctl start bcmccmdhandler.version.userid.containername.service
Starting the service
systemctl stop bcmccmdhandler.version.userid.containername.service
Stopping the service
systemctl enable bcmccmdhandler.version.userid.containername.service
Enable automatic start of the service at system startup
systemctl disable bcmccmdhandler.version.userid.containername.service
Disable automatic start of the service at system startup
To delete a service, call the script shsc/delete-bcmccmdhandler-service.sh.
For the administration of the service you need system administrator permissions. For more instructions on how to delete a service, see Uninstalling the BeanConnect tools.
Configuring an MC-CmdHandler as a service on Windows systems
If the MC-CmdHandler is installed without a BeanConnect proxy container, then the MC-CmdHandler is entered as a service at installation time under the name BeanConnect MC-CmdHandler <port-number> with autostart type Manual.
If the MC-CmdHandler is installed together with the BeanConnect proxy container, then you must subsequently explicitly enter the MC-CmdHandler as a service. You do this using the script shsc/MCCmdHandler_InstallSrv.cmd in the proxy container's home directory. Call the script with administration authorization:
<Proxy_home>/shsc/MCCmdHandler_InstallSrv.cmd
This script enters the service with autostart type Manual.
If you want to use the MC-CmdHandler to administer a proxy container that is installed on a remote host then it can be necessary under certain circumstances to run the service under the corresponding user account and not under the system account (default value on the installation of the MC-CmdHandler). You change the user account setting via the Windows Control Panel (Control Panel/Administrative Tools/Services).
You can use the script shsc/MCCmdHandler_UnInstSrv.cmd (called with administrative permissions) to remove the service again.