WebSphere

Configuration

Before using the WebSphere monitor, several of the WebSphere server jars must be installed in NeoLoad jmxlib/websphere directory.

WebSphere 6.0

To connect NeoLoad to WebSphere 6.0, copy the following files from the WebSphere directory to the <install-dir>/jmxlib/websphere directory:

After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.

WebSphere 6.1

To connect NeoLoad to WebSphere 6.1, copy the following files from the WebSphere directory to the <install-dir>/jmxlib/websphere directory:

With the FixPack 11 or later, it is required to copy also the following file:

After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.

WebSphere 7.0

To connect NeoLoad to WebSphere 7.0, copy the following files from the WebSphere directory to the <install-dir>/jmxlib/websphere directory:

After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.

WebSphere 8.0

To connect NeoLoad to WebSphere 8.0, copy the following files from the WebSphere directory to the <install-dir>/jmxlib/websphere directory:

After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.

WebSphere 8.5

To connect NeoLoad to WebSphere 8.5, copy the following files from the WebSphere directory to the <install-dir>/jmxlib/websphere directory:

After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.

WebSphere Liberty 8.5 - 9.0

You first need to activate monitoring in WebSphere Liberty to configure the monitor.

In the <websphere_liberty>/usr/servers/serverName/server.xml file, locate the <featureManager> section and add the two features below:

<feature>monitor-1.0</feature>
<feature>restConnector-1.0</feature>

To connect NeoLoad to WebSphere Liberty, copy the following file from the WebSphere Liberty directory to the <install-dir>/jmxlib/websphere_liberty directory:

<websphere_liberty>/clients/restConnector.jar

After copying the file, it is unnecessary to restart NeoLoad.
The files are automatically synchronized with the Monitoring Agent once the changes have been made.

Supported versions

The WebSphere monitor supports WebSphere 6.0.X, WebSphere 6.1.X, WebSphere 7.0.X, WebSphere 8.0.X and WebSphere 8.5.X.

Connection settings

Defining a monitor for a WebSphere server requires the name or IP address of the machine to be monitored, as well as the connection port (the default port is 8880). The port is the WebSphere server SOAP connection port (SOAP_CONNECTOR_ADDRESS in the administration console). In addition to these settings, a valid user account must be provided with which to connect to the WebSphere Administration Console.

Create a WebSphere monitor

NeoLoad makes it possible to create a new monitor either using the monitored machine creation wizard, as described in Create and configure a monitored machine, or from an existing monitored machine, as described in Create and configure a monitor.

NeoLoad automatically selects the most appropriate counters available on the server, for example, failed transactions, data pool states...

Available counters

WebSphere counters are automatically determined, based on all the Manageable Objects available. Since WebSphere counters are dynamic, retrieving all the counters can take several seconds. Clicking on a counter displays its description. These are the most common categories.