Installing the Oracle WebLogic monitoring extension

This monitoring extension is distributed as a zip file. It must be extracted before you can use it.

Before you begin

Best practice
When reinstalling or upgrading, make sure you first backup the existing files (such as qpwlmon.bat on Windows). See also Backing-up-before-an-upgrade-or-reinstall.

Related topics

Running-performance-and-availability-monitoring-extensions

Running-the-Oracle-WebLogic-monitoring-extension

Running-application-transaction-tracing-transaction-monitoring-extensions

Uninstalling-TMTM-performance-and-availability-monitoring-extensions

To install the Oracle WebLogic monitoring extension on Windows or UNIX 

  1. At a command prompt, change to the directory where the TMTM Agents and Extensions are installed
  2. Unzip the contents of the pkg_*_qpwlmon.zip package, as appropriate for your platform, to a sub-directory of the TMTM Agents and Extensions (e.g. into a directory named qpwlmon).
  3. If you are using the provided Java Runtime Environment (JRE), proceed to the next step.

    If you need to use a different JRE, for example where the provided JRE is no longer current and BMC is not able to provide updates, ensure that JAVA_HOME is set in your environment. See also Defining-alternative-JREs-for-Java-extensions. Note that on Windows the qpwlmon.bat file will require editing to change the JRE location to be used, unless you want to use the system JAVA_HOME setting.

    (UNIX only) After installing 8-1-00-Agent-Fix-Pack-E, QPWLMON_JAVA_HOME is used if set, then JAVA_HOME if set. If neither is set, on platforms where a JRE is included in the package that default JRE will be used.

  4. (UNIX only) Use chmod +x filename to make the following files executable:

    qpwlmon.sh

    Depending on your monitoring needs other files might need to be executable. The binary files and the *.ksh files for your operating system must be executable.

  5. Edit the ExtensionConfiguration.xml file as follows:

    • In the <Connection> stanza, replace the URL value with the location of your WebLogic server.
    • Replace the principal (user name) and credential (password) values with a user account and password with access to the WebLogic server.
    • To receive accurate server status updates (to ServerLifeCycleRuntime) if the server is stopped, perform the following in the clustered or non-clustered section as appropriate (but not both):

      • Uncomment both <ConnectionStatusAtributes> stanzas in the clustered or non-clustered section.
      • Insert the admin server name as the instanceName value for both the integer and string types of <ConnectionStatusAttribute>. For example, instanceName=twins2009

      • All other attribute values remain unchanged.

        Modify only the URL, principal (user), and credential (password) settings in the <Connection> stanza and the instanceName in the <ConnectionStatusAtributes> stanzas. Modifying any other element or attribute values can produce unwanted results.

    • Save the ExtensionConfiguration.xml file.

      Note

      To monitor more than one WebLogic server, duplicate the <Connection> stanza below the current <Connection> stanza and modify each copy to reflect element and attribute values for the added servers. You cannot monitor multiple versions of WebLogic with the same monitoring extension. You must set up separate monitoring extensions on different hosts running different versions of the WebLogic server.

  6. For WebLogic 10 or higher, refer to the WebLogic documentation for information about how to build a full client. When built, copy the client into the monitoring extension's working directory.
  7. In a text editor, review the files qpwlmon.conf (Windows) and qpwlmon.sh (UNIX) and comment in or out settings related to the target WebLogic version. For WebLogic 10 or higher, ensure that the file wlfullclient.jar is in the same directory as qpwlmon.conf or qpwlmon.sh. For WebLogic 9, copy weblogic.jar, wljxmclient.jar and webservices.jar into that directory. To use WebLogic 10.3 with Java 1.5 the file wlfullclient5.jar must be in that directory.
  8. Check that the TMTM Extensible Agent is running by entering qpea --status. If it is not running, enter qpea --start.
  9. To set the TMTM Topic Service host, change to the directory where you extracted the Oracle WebLogic monitoring extension files and:
    • For Windows enter:
      qpwlmon --ts-host host --ts-port port
    • For UNIX enter:
      ./qpwlmon.sh --ts-host host --ts-port port

      where:
      host is the host name or the IP address.
      port is the port on the host for the TMTM Topic Service. Omit the port clause to set the port to the default number 15001.
  10. (Windows only) Enter qpwlmon --install to install the Oracle WebLogic monitoring extension.
  11. (Optional) Set the logging level by opening and modifying the qplog.props file. Your options are info, debug, and warn. Info and warn can be used every day, but debug contains a large amount of data and might not be useful for continuous logging.
  12. Start the monitoring extension, change to the directory that contains qpwlmon.bat or qpwlmon.sh and:
    • For Windows enter qpwlmon --start
    • For UNIX enter ./qpwlmon.sh --start
  13. (Optional) Set the sample interval by opening framework.props in a text editor. Change the line:

    com.bmc.mmpa.eaapi.framework.waitstate.SampleInterval=60

    This sets the sample interval to 60 seconds, the default.
  14. (Optional) Using the Windows Service Manager, configure the Oracle WebLogic monitoring extension to start automatically when the computer is restarted. 

Where to go from here

 

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