Running the Oracle WebLogic monitoring extension


The Oracle WebLogic monitoring extension monitors and reports activity from WebLogic servers. The information is then passed to the MVMM Extensible Agent.

For information on installing this extension on the various supported platforms, see Installing-the-Oracle-WebLogic-monitoring-extension.

If you have not already distributed your 

MVMM 

 Extensible Agent and monitoring extension files, then do so now. See Using-Deployments-to-distribute-the-agent-and-extensions-packages.

Controlling the Oracle WebLogic monitoring extension on Windows or UNIX

This section describes how to start, stop and otherwise control the Oracle WebLogic monitoring extension.

(UNIX only) The Oracle WebLogic 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.

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

    To list all available command parameters, enter:

    For Windows: qpwlmon --help
    For UNIX: ./qpwlmon.sh --help

    For example, in Windows qpwlmon --start starts the monitoring extension; in UNIX ./qpwlmon.sh --start starts the monitoring extension.

Note

BEFORE STARTING: Change to the agent installation directory and enter qpea --status to check if the 

MVMM 

 Extensible Agent is running. If it is not running, enter qpea --start

Note

If you have not installed the monitoring extension as a Windows service, enter qpwlmon --console to start the monitoring extension in the foreground.

Note

Although nearly any shell can be used with 

MainView Middleware Monitor

, many of the script files are written for the Korn shell.

 

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