Enabling ARM debug tracing for Robotic Response Time monitors

Use the following procedure to enable tracing for Robotic Response Time monitors that make ARM calls, such as Rational Performance Tester, Rational Functional Tester, Robot GUI, Robot VU and CLI Application:

Edit the t6-logging.properties file located in the following location:
```
<ITM_HOME>\TMAITM6 (Windows)
<ITM_HOME>/config (UNIX)
```
Locate the BWM.trc.arm.debug.logging parameter and set it to true:
```
BWM.trc.arm.debug.logging=true
```
Save your edit and restart the Robotic Response Time agent.
Look for the log files in the following location:
```
<ITM_HOME>\TMAITM6\logs (Windows)
<ITM_HOME>/logs (UNIX)
```
The files will be named similar to the following example:
```
<short hostname>_t6arm_4bcf2cab-01.log
```
For example, test1_t6arm_4bcf2cab-01.log

An XML file, kt6armenv.xml, containing logging configuration settings (such as the log level and the location of the ARM log files) is created the first time that ARM logging is enabled. This file is located in the following directory:

<ITM_HOME>\TMAITM6 (Windows)
<ITM_HOME>/config (UNIX)

The contents of the kt6armenv.xml file is similar to the following example:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties>
  <comment>T6 RAS1 Logging Properites for ARM</comment>
  <entry key="KBB_RAS1_LOG">
    KBB_RAS1_LOG=%<ITM_HOME>\tmaitm6\logs\%<computer_name>
    _t6arm_%<sysutcstart>-.log
    INVENTORY=%<ITM_HOME>\tmaitm6\logs\%<computer_name>_t6arm.inv
    COUNT=03 LIMIT=5 PRESERVE=1 MAXFILES=9
  </entry>
  <entry key="KBB_VARPREFIX">KBB_VARPREFIX=%</entry>
  <entry key="KBB_RAS1">KBB_RAS1=(COMP:ALL)</entry>
</properties>

To change the location or name of the log file, change the value of the KBB_RAS1_LOG entry element.

To change the log level, change the value of the KBB_RAS1 entry element. For example to log only errors, change <entry key="KBB_RAS1">KBB_RAS1=(COMP:ALL)</entry> to <entry key="KBB_RAS1">KBB_RAS1=ERROR</entry> and restart the Robotic Response Time agent.

Note: For CL1 Scripts/Apps that do not make ARM calls the Robotic agent makes the ARM call on their behalf. ARM logging should be enabled for the Robotic agent in this case by adding the following statement (COMP:ARM ALL) to the RAS1 logging configuration for the agent. In this case the ARM logs will be written directly to the agent logs.