Configuring JConsole and JMXCLI to enable encrypted connections with Application Server

This topic describes the steps to configure the include JConsole (bljconsole) and JMXCLI monitoring tools to enable encrypted communication with an Application Server.

Prerequisite

Based on your security requirement you must specify the values for the UseSSLSockets and RequireClientAuthentication to specify which connections your Application Server can accept. An Application Server accepts connections encrypted using SSL if the UseSSLSockets parameter is set to true. Furthermore, client-side authentication using SSL certificates can also be enabled by setting the RequireClientAuthentication parameter to true. For more information about setting these parameters, see Managing-the-Application-Server.

Configuring bljconsole and JMXCLI to enable encrypted connections with the Application Server

The procedure to configure the bljconsole and JMXCLI monitoring tools to enable encrypted communication with an Application Server is different for the following scenarios..

If UseSSLSockets parameter is set to true, the Application Server only accepts encrypted connections. For more information about setting these parameters, see Managing-the-Application-Server.

Perform the procedures listed in the table below based on the following parameters:

  • Monitoring tool – bljconsole or jmxcli
  • Operating system – The platform on which the monitoring tool runs on (Windows or Linux)

Use the table filters to narrow down the procedure for the monitoring tool, and operating system used in your environment.



Note

In a Multi-Application Server (MAS) setup, if the second node does not have any configuration deployment, then you can not monitor the job server performance on the second node. This is applicable for bljconsole monitoring tool.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*