Enabling ARM on WebSphere

You can configure WebSphere® to use the ARM library and send events to Transaction Tracking without having to instrument Transaction Tracking for your web application.

Tip: You can use WASTT to monitor WebSphere Application Server instead of configuring WebSphere separately to use ARM. If you use WASTT, the required variables and directories in WebSphere Application Server are configured automatically. See Configuring WASTT for further information.

Configuring WebSphere

You must set properties and Request Metrics before ARM is enabled on WebSphere. To set the properties and metrics:

Using the administrative console on WebSphere, set the Request Metrics. Select Monitoring and Tuning > Request Metrics. Set the following in each section:
1. Select Prepare Servers for Request metrics collection.
2. Components to be instrumented, select All.
3. Trace level. Select one of the following:
  - Hops - entry and exit only. Gives overall transaction performance. Hops is the preferred option.
  - Performance_Debug - Greater detail including session beans.
  - Debug - Most detail including entity bean get and set timings.
4. Request Metrics Destination to the ARM agent:
  1. Select Application Response Measurement (ARM) agent.
  2. Set Agent type to ARM40.
  3. Set ARM transaction factory implementation class name to com.ibm.tivoli.tt.ArmTransactionFactory.
Optional: If WebSphere and the Transaction Collector are located on separate servers, copy the tusupport directory and its contents from the server with the Transaction Collector installed, to the server on which WebSphere is installed. The tusupport directory can be found at the following locations:
- On UNIX systems, CANDLE_HOME/platform/tu/tusupport
- On Windows systems, CANDLE_HOME\TMAITM6\tusupport
Using the administrative console, set the custom properties:
1. Select Application servers > server1 > Java and Process Management > Process Definition > Java Virtual Machine > Custom Properties.
2. Set the ws.ext.dirs property to the location of the tusupport directory.
To see the ARM logs when the ARM library is used by WebSphere Application Server, use the administrative console and select Application servers > server1 > Process Definition > Environment Entries, and set the properties:
```
KBB_RAS1=ALL
KBB_RAS1_LOG=log file
CYTA_LOGGER=ttapi
```
If you are using DB2 and transactions are received from the WebSphere Application Server, set the following custom property to true: com.ibm.websphere.pmi.reqmetrics.PassCorrelatorToDB. If the custom property is not in the list, create a new property: enter the property name in the Name field, and a valid value in the Value field.
Restart WebSphere.
WebSphere now issues ARM calls and passes correlators to DB2.