Websphere

This agent returns performance metrics for an IBM Websphere application server.

Local/Remote Modes

The agent supports both local and remote modes. A requirement is that at least Websphere Client Environment must be installed on the machine where the agent is deployed.

Supported Versions

The agent supports Webpshere versions 5.0.x, 5.1.x and 6.0.x.

Configuration

The following configuration options are available:

  • Proxy RMI port: The RMI port used by the agent proxy. Must be unique for every websphere agent running on the local machine.
  • Connector: type of connector to be used, either SOAP or RMI.
  • Security: check this option if Websphere global security is enabled.
  • WebSphere home directory: path to the location where Websphere is installed.
  • WebSphere library classpath: contains a list of all jars required for monitoring Websphere.
  • Trust store: location of the WAS certificate store, relative to the WAS home directory (above).
  • Key store: location of the WAS key store, relative to the WAS home directory (above).
  • Trust store password: Password to the WAS certificate store. Defaults to WebAS.
  • Key store password: Password to the WAS key store. Defaults to WebAS.
  • soap.client.props file location: location of this configuration file required by WAS client, relative to the WAS home directory (above).
  • sas.client.props file location: location of this configuration file required by WAS client, relative to the WAS home directory (above).
  • Username: user name to use when connecting to Websphere
  • Password: password to use when connecting to Websphere
  • Port: Websphere port number to connect to.

Contents

Will vary depending on the version of Websphere system installed. Please refer to Websphere documentation for details regarding its performance metrics.

Note: due to a known issued in Sun's JRE (see bug #4496398), the agent cannot monitor Websphere systems installed in a path which contains spaces (eg c:/Program Files).