Configuring WASTT

Configure WebSphere Application Server properties for WASTT by running the wsadmin script, called configure_wastt.py, included in the installation. The script configures the default configuration properties and library paths in a WebSphere Application Server profile, and configures the PMI Request Metrics settings to enable ARM.

Before you begin

Ensure that WASTT is installed.

About this task

The configure_wastt.py wsadmin script is installed with WASTT. Call the script by running the following configuration script that is installed to wastt.install.dir:

On UNIX systems, configure.sh
On Windows systems, configure.cmd

The configuration script sets the logging levels and the log file location for WASTT. WASTT logs ERROR (COMP:arm ALL) and log files are stored in the WebSphere Application Server log directory.

Because PMI Request Metrics are configured across profiles, all servers are configured by the configuration script provided with WASTT. The configuration script sets the PMI Request Metrics for WASTT to HOPS.

Note: To monitor EJB transactions with WASTT, change the PMI Request Metrics level from HOPS to Performance_debug.

Important: If you configure WASTT in a WebSphere Application Server Network Deployment installation, ensure that you also configure the Dmgr profile. The Dmgr profile contains configuration settings that control the level of monitoring in the WebSphere Application Server servers. If you do not configure the Dmgr profile, no data will be collected.

Procedure

To configure WASTT:

If required, set the Transaction Collector address. Open configure_wastt.py in a text editor and change the value of the TRANSACTION_COLLECTOR_ADDRESS variable. A default value is used if you do not set a Transaction Collector address.
On UNIX systems, run the following command from the command-line interface:
```
./configure.sh path-to-WAS-profile
```
On Windows systems, run the following command from the command-line interface:
```
configure.cmd path-to-WAS-profile
```
Repeat for each WebSphere Application Server to which WASTT is installed.
To run WebSphere Application Server with WASTT enabled, all required libraries must be in the system library search path:
1. Run the following commands to add the path to the system library search path:
  - On Linux or Solaris systems, run LD_LIBRARY_PATH= /opt/IBM/ITM/platform/tj/wastt:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH. Also run CANDLE_HOME=/opt/IBM/ITM; export CANDLE_HOME.
  - On AIX® systems, run the above commands for LIBPATH instead of LD_LIBRARY_PATH.
  - On HP-UX systems, run the above commands for SHLIB_PATH instead of LD_LIBRARY_PATH.
  - On Windows systems, append %CANDLE_HOME%/TMAITM6/ktj/wastt to the Path environment variable. CANDLE_HOME is set automatically by the IBM® Tivoli® Monitoring installer.
2. Restart the WebSphere Application Server.

What to do next

If required, you can modify the address of the Transaction Collector after you have configured WASTT. Using the WebSphere Application Server Admin console, modify the Java™ system property, com.ibm.tivoli.tt.collector. Ensure that you restart WebSphere Application Server for the changes to take effect.

The default profile All Maximo URLs via ARM is included in V7.2 and later. This profile extracts Maximo-specific request parameters such as target id and uses them to enrich the transaction names. This enables the identification of different transaction types within Maximo®.

Construct additional WASTT transactions that you want to monitor by using the Application Management Configuration Editor. See Using the Application Management Configuration Editor in the Administrator's Guide for further information.

For WASTT V7.2.0.1 and later, you can enable KBB RAS1 logging in WebSphere Application Server. To enable KBB RAS1 logging when you want to debug a problem:

In the WebSphere® Administrative Console, select Application servers > server1 > Process Definition > Environment Entries.
Set the property CYTA_LOGGER_DISABLE=0
For performance reasons, when you have finished debugging, set the property CYTA_LOGGER_DISABLE=1 to disable KBB RAS1 logging.