Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Configuring the Management Console command handler (MC-CmdHandler)

The Management Console Command Handler (MC-CmdHandler) is a stand-alone Java application that enables the Management Console to administer remote proxies, proxy components, resource adapters or the Log4j configuration.

An MC-CmdHandler is installed for each BeanConnect proxy. In addition, you can also install the MC-CmdHandler separately on computers other than the proxy computer. This is necessary in the following cases:

  • If it is not possible to access required files such as the deployment descriptor ra.xml in the BeanConnect RAR archive or the resource adapter's Log4j configuration because they are present on different computers and/or under different IDs.

  • If it is not possible to access components such as openUTM-LU62 or communication services because they are present on different computers and/or under different IDs.

The MC-CmdHandler is a socket listener that waits at a listener port for orders given by the Management Console. The MC-CmdHandler is able to perform basic file transfer tasks such as listing directories, supplying information about files, fetching and updating files. Beyond this, it is also possible to execute scripts on a remote system.

The following conditions must be met before the above-mentioned components can be administered on remote hosts:

  • The MC-CmdHandler must be started on the host on which the proxy or the components to be administered are running (resource adapter, openUTM-LU62 and communication service).

  • The Management Console must be able to access the MC-CmdHandler.