Using the Resource Analyzer 4.0.x with WebSphere 3.5.5+ application servers

You can use the Resource Analyzer in WebSphere Application Server Version 4.0.2 with WebSphere Application Server Version 3.5.5 or later application servers. To do so, change the configuration and then run the Resource Analyzer as described below.

Configuration changes

Changes to the WebSphere Application Server 3.5.x runtime environment

Ensure that the WebSphere Application Server Version 3.5 environment is at WebSphere Application Server Version 3.5.5 or later.

Changes to the WebSphere Application Server Version 4.0.2 installation

1. Create a directory (for example, was3.5.5) under the directory WebSphere_installation_root/classes.
2. Copy the repository.jar and ejs.jar files from the WebSphere_installation_root/lib directory for Version 3.5.5 to the WebSphere_installation_root/classes/was3.5.5 directory for Version 4.0.2.
3. Copy the WebSphere_installation_root/bin/ra.bat file to WebSphere_installation_root/bin/ra355.bat.
4. Open an editor on the ra355.bat file and replace

   -Dws.ext.dirs=%WAS_EXT_DIRS%

   with

   -Dws.ext.dirs=WebSphere_installation_root\classes\was3.5.5;%WAS_EXT_DIRS%

Running Resource Analyzer with 3.5.5+

To monitor a Version 3.5.5+ application server with Resource Analyzer Version 4.0, you must specify the version parameter at the command line using the following format:

ra355.bat/sh    host    port    version

The following values are valid for the version parameter:

AE

Monitors WebSphere Advanced Edition 4.0.x application servers

EPM

Monitors WebSphere 3.5.5 or later application servers

To use the Resource Analyzer to monitor a 3.5.5+ application server, the version parameter must be set to EPM. For example:

ra355.bat madison 900 EPM

All three parameters are required when monitoring WebSphere Version 3.5.5 or later. The default administrative server port is 900. If the version parameter is left blank, it defaults to Version 4.0.x AE.

Note that there is no maximum level defined for Version 3.5.x so the maximum level for the Version 4.0 FixPak 2 Resource Analyzer matches to the high level in 3.5.x.

Also note that there is a known performance problem in the Resource Analyzer when enabling method level EPM data. If method level EPM data is enabled in 3.5.x, the Resource Analayzer might be slow to respond. The Resource Analyzer is extremely slow when the application server has a large number of beans. However, if you enable method level EPM data for a small number of beans, the Resource Analyzer response time should be reasonable. You can disable method level EPM data in the Version 3.5.x administrative console; use the performance control panel and disable enterprise bean methods (set the level to none). If possible, avoid changing the level for enterprise beans through the Resource Analyzer because you enable method level data when you do so.

For a list of PMI counters available in Version 3.5.5, refer to "PMI counters available in 3.5.5+."