Running the WebSphere Application Server monitoring extension

This monitoring extension monitors and reports activity from WebSphere Application Server.

For information on installing this extension on the various supported platforms, see Installing the WebSphere Application Server monitoring extension.

If you have not already distributed your TMTM Extensible Agent and monitoring extension files, then do so now.

This section includes:

Controlling the WebSphere Application Server monitoring extension on Windows or UNIX

  1. Open a command prompt and change to the directory containing the distributed files.
  2. Enter the monitoring extension command qpwasmon (Windows) qpwasmon.sh (UNIX) followed by the required command parameter.

    To list all available command parameters, enter:
    For Windows: qpwasmon --help
    For UNIX: ./qpwasmon.sh --help

    For example, in Windows qpwasmon --start starts the monitoring extension; in UNIX ./qpwasmon.sh --start starts the monitoring extension.
    (UNIX only) WebSphere Application Server monitoring extension runs as a Java process. If you want to work directly with the process, use the ps command to find the active Java processes.

    Note

    (UNIX only) - If you use the kill -9 command to stop the WebSphere Application Server monitoring extension, remove the .lock files (qpea.lock and qpwas.lock). If the TMTM Extensible Agent or monitoring extension did not shut down gracefully, remove the .lock files (qpea.lock, and qpwasmon.lock) before starting it again. The lock file prevents multiple processes from running at the same time. Starting the monitoring extension. If you have not installed the monitoring extension as a Windows service, enter qpwasmon --console to start the monitoring extension in the foreground. Although nearly any shell can be used with TrueSight Middleware and Transaction Monitor, many of the script files are written for the Korn shell.

    The WebSphere Application Server (WAS) type description may not reflect the version monitored (for example, a WAS Cell will be described as a “WAS6 Cell” in the physical tree in the Monitor Console).

Controlling the WebSphere Application Server monitoring extension on i5/OS 

  1. To start the WAS Extension on i5/OS: at a command prompt, enter wrkactjob to ensure that the agent is running. If it is not running, start it.
  2. Enter . WASInstallDir/bin/setupClient to configure your WebSphere Application Server environment. WASInstallDir is the location of your WebSphere Application Server installation.
  3. Enter . WASInstallDir/bin/setupCmdLine to further configure your WebSphere Application Server environment. WASInstallDir is the location of your WebSphere Application Server installation.
  4. From a Qshell, enter qpwasmon.sh --start.
  5. To stop the WAS Extension on i5/OS: at a command prompt, enter wrkactjob to ensure that the agent is running. If it is not running, start it.
  6. From a Qshell, enter qpwasmon.sh --stop.

Pruning the monitored types

To reduce the number of types monitored and potentially save on system resources, you can edit ComMQSoftwareWASMonitor.xml to restrict the number of types qpwasmon monitors. ComMQSoftwareWASMonitor.xml is delivered with a complete list of all monitored types and a number of MonitoredType categories, all of which are commented out by default. The composition of the monitored type categories is based on customer requests.

This procedure can be applied to ComMQSoftwareWASMonitor.xml for each separate platform.

  1. Open ComMQSoftwareWASMonitor.xml in a text editor.
  2. Uncomment the MonitoredType categories that contain the types you want to monitor. Do this in each category by moving the close comment (-->) from the end of the category to the end of the category title line as shown in the examples below.
  3. Comment in or comment out any of the individual monitored types within the category depending on whether you want them monitored (uncomment) or not monitored (comment out).

    The first example shows the supplied, unedited database category in ComMQSoftwareWASMonitor.xml. The second example shows an edited version where the entire category has been uncommented and the third monitored type has been commented out. These edits mean that the first and second types only are monitored.

    Note

    Once any category of monitored types is uncommented, none of the types listed outside an uncommented category are monitored. This includes the entire superset of types not included in an uncommented category.


    Supplied, commented-out database category in ComMQSoftwareWASMonitor.xml

    <!-- Database Category
    <MonitoredType name="ComMQSoftwareWASJDBCConnectionPool" typeId="200063" desc="WAS6 JDBC Connection Pool" jmxKey="connectionPoolModule">
    </MonitoredType>
    <MonitoredType name="ComMQSoftwareWASJDBCProvider" typeId="200065" desc="WAS6 JDBC Provider" jmxKey="JDBCProvider">
    </MonitoredType>
    <MonitoredType name="ComMQSoftwareWASJDBCDataSource" typeId="200064" desc="WAS6 JDBC Data Source" jmxKey="JDBCDataSource">
    </MonitoredType>
    -->

    Edited database category

    <!-- Database Category -->
    <MonitoredType name="ComMQSoftwareWASJDBCConnectionPool" typeId="200063" desc="WAS6 JDBC Connection Pool" jmxKey="connectionPoolModule">
    </MonitoredType>
    <MonitoredType name="ComMQSoftwareWASJDBCProvider" typeId="200065" desc="WAS6 JDBC Provider" jmxKey="JDBCProvider">
    </MonitoredType>
    <!-- <MonitoredType name="ComMQSoftwareWASJDBCDataSource" typeId="200064" desc="WAS6 JDBC Data Source" jmxKey="JDBCDataSource"
    </MonitoredType>
    -->


  4. To add a type to monitor, copy and paste it from the superset of types in the file into any of the MonitoredType categories. Change the name from Type to MonitoredType and close the line with </MonitoredType>.
  5. Save ComMQSoftwareWASMonitor.xml.

Note

If all types are already being monitored and it is decided to prune types afterwards, it is recommended that you stop the qpwasmon extension and unregister the WAS Network Deployment Cell under the WAS Server, as described in the procedure below. Otherwise the types which are not monitored show up as orphaned objects in the Monitor Console Agent tree and could cause confusion.

To remove a WAS Network Deployment Cell from monitoring

  1. Stop the qpwasmon extension.
  2. Navigate to the agent folder and run qpreg to unmonitor the WAS Cell or Server. For example:
    ./qpreg -u "ComMQSoftwareWASMonitor" " ComMQSoftwareWASCell" "yourCellName" 
Was this page helpful? Yes No Submitting... Thank you

Comments