The JMX client usually requires additional application server specific Java libraries to communicate with the application server.
In all cases, you must configure these additional Java libraries in the Management Console. To do this, it is necessary to copy thiese Java libraries into application server specific directories and to extend the Management Console's classpath. The scripts mc.cmd (Windows systems) and mc.sh (Linux systems) for starting the Management Console, contain suitable statements for several application servers. In this scripts you also find the names of the application specific directories.
In Windows systems, the script mc.cmd is located under <MC_home>/bin, where <MC_home> is the Management Console's installation directory.
In Linux systems, the script mc.sh is located in the installed BeanConnect's Console/bin directory.
To use the Management Console as a JMX client, you must additionaly set an application server specific option when starting the Management Console.
In Windows systems the Management Console will be started with the script mc.cmd, as a JMX client with mc.cmd -appServerType.
In Linux systems the Management Console will be started with the script startconsole.sh, in the Management Console's installation directory, as a JMX client with startconsole.sh -appServerType.
If the predefined statements do not fit for your application server or the version of the application server requires different settings, you can change the mc.cmd file on the Windows system accordingly for your application.
On Linux systems, you should make the required changes in the file startconsole.sh in the Management Console's installation directory. Alternatively, you can also create your own script to start the Management Console.