Important

   

This space contains documentation for TrueSight Server Automation 8.9.03 and the later service packs for 8.9. For earlier releases, see BMC Server Automation 8.9.

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.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...


Monitoring toolOperating systemSteps
bljconsoleLinux

No configuration required for the default base port.

For a non-default base port, you can use an additional parameter, -d, to monitor either the job deployment package or the config deployment package, as follows:

  1. Navigate to  /opt/bmc/bladeLogic/NSH/bin and open the bljconsole file using any text editor.
  2. Add the parameter, -d <jobDepPort> or -d <configDepPort> to the end of the following command:
    $JAVA_HOME/bin/java -javaagent:$STDLIB/aspectjweaver-1.8.5.jar -Dblx.cmrootdir=$BLADELOGIC_HOME/br com.bladelogic.om.infra.client.ui.genericconsole.Main "${@}"

    The updated command looks like the following:
    $JAVA_HOME/bin/java -javaagent:$STDLIB/aspectjweaver-1.8.5.jar -Dblx.cmrootdir=$BLADELOGIC_HOME/br com.bladelogic.om.infra.client.ui.genericconsole.Main "${@}" -d 10836
bljconsoleWindows

No configuration required for the default base port.

For a non-default base port, you can use an additional parameter, -d, to monitor either the job deployment package or the config deployment package, as follows:

  1. Navigate to C:\Program Files\BMC Software\BladeLogic\NSH\bin\ and open the bljconsole.bat file using any text editor.
  2. Add the parameter, -d <jobDepPort> or -d <configDepPort> to the end of the following command:
    call "C:\PROGRA~1\BMCSOF~1\BLADEL~1\appserver\NSH\bin\bljconsole.exe" %*

    The updated command looks like the following:
    call "C:\PROGRA~1\BMCSOF~1\BLADEL~1\appserver\NSH\bin\bljconsole.exe" %* -d 11836
JMXCLILinux
  • If you are running JMXCLI in the single parameter (properties file) mode:

A default properties file named bl_jmx_monitor.properties is provided together with the JMXCLI utility, in the br directory in the BladeLogic installation directory (typically /opt/bmc/bladeLogic/NSH/br).

Perform the following steps:

    1. Navigate to /opt/bmc/bladeLogic/NSH/br and open the bl_jmx_monitor.properties file using any text editor.
    2. Add the following parameter to the end of the file:
      use_ssl=true
    3. Navigate to /opt/bmc/bladeLogic/NSH/bin directory and invoke JMXCLI, as follows:
      • For a default base port, use the following command:
        jmxcli -a <hostName> /opt/bmc/bladeLogic/NSH/br/bl_jmx_monitor.properties
      • For a non-default port, you can use an additional parameter, -d, to monitor either the job deployment package or the config deployment package.
        • To monitor the job deployment package, invoke JMXCLI, as follows:
          jmxcli -a <hostName> -d <jobDepPort> -p <authPort> /opt/bmc/bladeLogic/NSH/br/bl_jmx_monitor.properties
          For example:
          jmxcli -a <hostName> -d 11836 -p 10840 /opt/bmc/bladeLogic/NSH/br/bl_jmx_monitor.properties
        • To monitor the config deployment package, perform the following steps:
          1. Navigate to /opt/bmc/bladeLogic/NSH/br and open the bl_jmx_monitor.properties file using any text editor and comment the following lines:

            monitor.job_count.mbean.name=Bladelogic:type=ApplicationServer,Job Manager=Job Manager,name=Job Manager
            monitor.job_count.attribute.name=NumberOfRunningJobs
            monitor.job_count.attribute.type=attribute
            monitor.job_count.sequence_id=7
            monitor.exec_wi.mbean.name=Bladelogic:type=ApplicationServer,Job Manager=Job Manager,name=Job Manager
            monitor.exec_wi.attribute.name=NumOfWorkItemsCached
            monitor.exec_wi.attribute.type=attribute
            monitor.exec_wi.sequence_id=8
          2. Invoke JMXCLI, as follows:
            jmxcli -a <hostName> -d <configDepPort> -p <authPort> /opt/bmc/bladeLogic/NSH/br/bl_jmx_monitor.properties
            For example:
            jmxcli -a <hostName> -d 10836 -p 10840 /opt/bmc/bladeLogic/NSH/br/bl_jmx_monitor.properties

  • If you are running JMXCLI in the multiple command line parameter mode:
    1. Navigate to /opt/bmc/bladeLogic/NSH/bin directory and invoke JMXCLI, as follows:
      jmxcli -a <hostName> -d <jobDepPort>/<configDepPort> -p <authPort> -u BLAdmin -r BLAdmins -e <encodedUserPassword (for SRP auth type only)> "Bladelogic:type=ApplicationServer,name=Application Server" getAppServerName use_ssl=true
      For example,

      • For a default base port, invoke JMXCLI uisng the following command:
        jmxcli -a <hostName> -d 9836 -p 9840 -u BLAdmin -r BLAdmins -e <encodedUserPassword (for SRP auth type only)> "Bladelogic:type=ApplicationServer,name=Application Server" getAppServerName use_ssl=true

      • For a non-default base port, invoke JMXCLI uisng the following command:
        jmxcli -a <hostName> -d 11836 -p 10840 -u BLAdmin -r BLAdmins -e <encodedUserPassword (for SRP auth type only)> "Bladelogic:type=ApplicationServer,name=Application Server" getAppServerName use_ssl=true

JMXCLIWindows
  • If you are running JMXCLI in the single parameter (properties file) mode:

A default properties file named bl_jmx_monitor.properties is provided together with the JMXCLI utility, in the br directory in the BladeLogic installation directory (typically C:\Program Files\BMC Software\BladeLogic\NSH\br).

Perform the following steps:

    1. Navigate to C:\Program Files\BMC Software\BladeLogic\NSH\br and open the bl_jmx_monitor.properties file using any text editor.
    2. Add the following parameter to the end of the file:
      use_ssl=true
    3. Navigate to C:\Program Files\BMC Software\BladeLogic\NSH\bin directory and invoke JMXCLI, as follows:
      • For a default base port, use the following command:
        jmxcli -a <hostName> C:\Program Files\BMC Software\BladeLogic\NSH\br\bl_jmx_monitor.properties
      • For a non-default port, you can use an additional parameter, -d, to monitor either the job deployment package or the config deployment package.
        • To monitor the job deployment package, invoke JMXCLI, as follows:
          jmxcli -a <hostName> -d <jobDepPort> -p <authPort> C:\Program Files\BMC Software\BladeLogic\NSH\br\bl_jmx_monitor.properties
          For example:
          jmxcli -a <hostName> -d 11836 -p 10840 C:\Program Files\BMC Software\BladeLogic\NSH\br\bl_jmx_monitor.properties
        • To monitor the config deployment package, perform the following steps:
          1. Navigate to C:\Program Files\BMC Software\BladeLogic\NSH\br and open the bl_jmx_monitor.properties file using any text editor and comment the following lines:

            monitor.job_count.mbean.name=Bladelogic:type=ApplicationServer,Job Manager=Job Manager,name=Job Manager
            monitor.job_count.attribute.name=NumberOfRunningJobs
            monitor.job_count.attribute.type=attribute
            monitor.job_count.sequence_id=7
            monitor.exec_wi.mbean.name=Bladelogic:type=ApplicationServer,Job Manager=Job Manager,name=Job Manager
            monitor.exec_wi.attribute.name=NumOfWorkItemsCached
            monitor.exec_wi.attribute.type=attribute
            monitor.exec_wi.sequence_id=8
          2. Navigate to C:\Program Files\BMC Software\BladeLogic\NSH\bin directory and invoke JMXCLI, as follows:
            jmxcli -a <hostName> -d <configDepPort> -p <authPort> C:\Program Files\BMC Software\BladeLogic\NSH\br\bl_jmx_monitor.properties
            For example:
            jmxcli -a <hostName> -d 10836 -p 10840 C:\Program Files\BMC Software\BladeLogic\NSH\br\bl_jmx_monitor.properties

  • If you are running JMXCLI in the multiple command line parameter mode:
    1. Navigate to C:\Program Files\BMC Software\BladeLogic\NSH\bin directory and invoke JMXCLI, as follows:
      jmxcli -a <hostName> -d <jobDepPort>/<configDepPort> -p <authPort> -u BLAdmin -r BLAdmins -e <encodedUserPassword (for SRP auth type only)> "Bladelogic:type=ApplicationServer,name=Application Server" getAppServerName use_ssl=true
      For example,

      • For a default base port, navigate to C:\Program Files\BMC Software\BladeLogic\NSH\bin directory and invoke JMXCLI uisng the following command:

        jmxcli -a <hostName> -d 9836 -p 9840 -u BLAdmin -r BLAdmins -e <encodedUserPassword (for SRP auth type only)> "Bladelogic:type=ApplicationServer,name=Application Server" getAppServerName use_ssl=true

      • For a non-default base port, navigate to C:\Program Files\BMC Software\BladeLogic\NSH\bin directory and invoke JMXCLI uisng the following command:

        jmxcli -a <hostName> -d 11836 -p 10840 -u BLAdmin -r BLAdmins -e <encodedUserPassword (for SRP auth type only)> "Bladelogic:type=ApplicationServer,name=Application Server" getAppServerName use_ssl=true


Note

In MultiApplication Server (MASsetup, if the second node doesnot have any configuration deployment, then you can not monitor the job server performance on the second node. This is applicable for bljconsole monitoring tool.

Was this page helpful? Yes No Submitting... Thank you

Comments