IBM Tivoli Composite Application Manager for Transactions, Version 7.4.0.0

How to configure and gather Rational Performance Tester trace logs

The problem: When you have script problems related to Rational Performance Tester (RPT), you might need to collect appropriate trace logs for resolving these issues.

The solution: The following sections guide you through the process of configuring trace logging so you can collect the right information to assist you in troubleshooting RPT script issues.

Identifying the Rational Performance Tester runtime package

Use the following procedure:

Log onto the Application Management Console (T3) host.
Navigate to %CANDLE_HOME%\kt1depot\T3\RPT.
Open script-name.zip, where script-name is the name of your Rational Performance Tester script in a text editor.
The runtime version is identified in the runtimeVersion property. For example:
```
runtimeVersion=7.2.154.v20090225_2153_26737781
```

Configuring, generating, and collecting trace logs

Use the following procedure to configure, generate and collect trace logs:

Stop the Robotic Response Time (T6) agent.
Delete the following log files on the Robotic Response Time host:
- The following log files under %ALLUSERSPROFILE%\ibm\tivoli\common\BWM\logs:
  - trace-robotic*.log
  - msg-robotic*.log
- All log files under %ALLUSERSPROFILE%\ibm\tivoli\common\BWM\logs\RPT\rpt-runtime-version, where rpt-runtime-version is the value of the runtimeVersion property found in the previous section. These files include trace-rpt*.log.
For each of the following logging properties files on the Robotic Response Time (T6) host, make a backup of the file and then modify the files to change the following entries:
- %CANDLE_HOME%\TMAITM6\t6-logging.properties
  Change the following entries:
  - BWM.trc.rpt.pc.level=DEBUG_MAX
  - BWM.trc.rpt.pm.level=DEBUG_MAX
  - BWM.trc.rpt.rpttest.level=DEBUG_MAX
  - BWM.trc.rpt.event.level=DEBUG_MAX
  - BWM.trc.rpt.util.level=DEBUG_MAX
  - BWM.trc.rpt.managed.level=DEBUG_MAX
- %CANDLE_HOME%\TMAITM6\app\RPT\config\itcamrt-logging.properties
  Change the following entries:
  - BWM.trc.rpt.pc.level=DEBUG_MAX
  - BWM.trc.rpt.pm.level=DEBUG_MAX
  - BWM.trc.rpt.rpttest.level=DEBUG_MAX
  - BWM.trc.rpt.event.level=DEBUG_MAX
  - BWM.trc.rpt.util.level=DEBUG_MAX
  - BWM.trc.rpt.managed.level=DEBUG_MAX
  - BWM.trc.rpt.external.level=DEBUG_MAX
  Note: These trace parameters do not configure the agent to generate the execution history (msg-rptHistory*.log).
  You set the BWM.trc.rpt.pc.level property to DEBUG_MAX in this itcamrt-logging.properties file to generate the Common Base Event (CBE) log files. The RPT playback engine generates the CBE log files in the following directory, where rpt-runtime-version is the version number of the RPT Runtime package:
```
%CANDLE_HOME%\TMAITM6\app\RPT\runtimes\rpt-runtime-version
```
  The CBE log files use the filename CommonBaseEvents##.log. These files will show any errors that are not in the execution history files.
- In addition to the above changes in the itcamrt-logging.properties file, set the following level parameters to DEBUG_MAX, and set the logging parameters to true:
```
#-----------------------------------------------
# RPT
#-----------------------------------------------
# RPT Playback Controller TRACE
BWM.trc.rptHistory.pc.level=DEBUG_MAX
BWM.trc.rptHistory.pc.logging=true
BWM.trc.rptHistory.listenerNames=BWM.handler.file.trc.rptHistory

# RPT Playback Controller MSG
BWM.msg.rptHistory.pc.level=DEBUG_MAX
BWM.msg.rptHistory.pc.logging=true
BWM.msg.rptHistory.listenerNames=BWM.handler.file.msg.rptHistory

# RPT Event TRACE
BWM.trc.rptHistory.action.level=DEBUG_MAX
BWM.trc.rptHistory.action.logging=true

# RPT Event MSG
#BWM.msg.rptHistory.action.level=DEBUG_MAX
BWM.msg.rptHistory.action.level=ALL
BWM.msg.rptHistory.action.logging=true

#=======================================================================
# END FILE tmtp-logging.properties
#=======================================================================
```
On the Robotic Response Time host, make a backup copy of %CANDLE_HOME%\TMAITM6\kt6env, then edit the file and add the following entry to the end of the file:
```
ARM_KEEP_DATA_FILES=Y
```
This option retains the ARM data files under %CANDLE_HOME%\TMAITM6\arm\log\kt6\delete until you remove the ARM_KEEP_DATA_FILES=Y option and restart the Robotic Response Time agent.
Restart the Robotic Response Time (T6) agent and reproduce the issue.
Add the following logs to an archive file and upload the file to ecurep. Select the options to include pathnames and recurse subdirectories.
- From %ALLUSERSPROFILE%\ibm\tivoli\common\BWM\logs:
  - trace-robotic*.log
  - msg-robotic*.log
  - T6-SystemOut.log
  - T6-SystemErr.log
- All logs from %ALLUSERSPROFILE%\ibm\tivoli\common\BWM\logs\RPT\rpt-runtime-version, where rpt-runtime-version is the version number of the RPT Runtime. These files include trace-rpt*.log.
- The execution history (msg-rptHistory*.log) files in the %ALLUSERSPROFILE%\ibm\tivoli\common\BWM\logs\[application name[\[script name] directory. These execution history logs include the events that occurred when the script ran.
- The CommonBaseEvent*.log files located under %CANDLE_HOME%\TMAITM6\app\RPT\runtimes\rpt-runtime-version. These files include errors that are not in the execution history files.
- The *.dat ARM data files from %CANDLE_HOME%\TMAITM6\arm\log\kt6\delete.
- A copy of the current T6 trace logs under %CANDLE_HOME%\TMAITM6\logs. These trace logs are named in the format: hostname_t6_*.log.
On the TEMS host and on the Robotic Response Time agent host where this script is running, navigate to %CANDLE_HOME%\InstallITM. Run the kincinfo command, naming the output file appropriately to identify the host, such as tems_host.txt, or t6_host.txt. For example:
```
kincinfo -i > tems_host.txt
```
Provide the name of the script that is not behaving correctly.
Provide a screen capture of the Help > About dialog box in the Rational Performance Tester workbench that you used to create the script.
IBM Software Support might ask for additional logs, depending on the issue.

Last updated: September 2014