No Robotic data in the workspaces

The problem: No Robotic data is displayed in the workspaces. This problem might occur for any of the following reasons:

The robotic script is not playing back as expected.
There are no client definitions in the Application Management Configuration Editor that match the system on which one or more monitoring agents are running.

The solution: To resolve this problem, you can do the following:

Verify that the robotic script is playing back.
All robotic components use ARM to store the data. Check the ITM_HOME/tmaitm6/arm/log/kt6 for *.dat files. ARM writes out these .dat files when it is collecting data. Make a copy of the *.dat files and view the copy to see what data is collected.
Check the Agent Configuration workspace (right-click Robotic Response Time -> Workspaces -> Agent Configuration) to verify that the application and transaction patterns are correct. If needed, use the Application Management Configuration Editor to modify the application and transaction patterns in the profile configuration.
Enable ARM debug.
ARM debug is enabled by creating a file called debug_all.txt or debug_[process ID].txt in the ITM_HOME/tmaitm6/arm/log/kt6 directory.
The creation of the ARM debug log depends on your version of ITCAM for Transactions:
- For versions of ITCAM for Transactions up to and including version 7.1.0.2, you need to ensure that the ARM configuration file armconfig.xml is created in ITM_HOME/tmaitm6/arm, and includes the traceenabled parameter, set to true. When this condition is met, logging is enabled and messages are saved to ITM_HOME/tmaitm6/logs/trace_armdebug.log.
- For newer versions of ITCAM for Transactions from version 7.2 and later, the traceenabled parameter is replaced by the KBB_RAS1_LOG and KBB_RAS1 environment variables, which enable KBB logging. If a process such as a web server creates a child process, the environment variables might not be inherited. To enable logging in this situation, create a file named KBBENV in the current working directory of the process and add the following lines:
```
KBB_RAS1_LOG=path to log files
KBB_RAS1=ERROR (COMP:ARM ALL)
```
For more information on these log configuration steps, see the topic, "Updating the location of a remote Transaction Collector" in the Installation and Configuration Guide.

You typically create new client definitions to meet your specific needs. However, this problem might occur if none of the client definitions that you created in the Application Management Configuration Editor match the system where one or more monitors are running in your environment. This can occur even when there are valid transactions running on that system. Check the contents of trace-debug.log for the message:

Ignoring transaction because it did not match a client definition.

Example:

2009-08-11 07:58:27.079:843:946 (3012:1540) - This is an edge
transaction.
Testing transaction against profiles, transaction properties are:
=
AgentType = T6
ApplicationGroup = IBM Rational Functional Test
ApplicationInstance =
ApplicationName = RFT_WRTPlants01
Hostname = cam71-rpt1
IP = 192.168.219.208
IPV4ClassASubNet = 192*
IPV4ClassBSubNet = 192.168*
IPV4ClassCSubNet = 192.168.219*
IPV6 = 192.168.219.208
ServerName = cam71-rpt1
TransactionName = RFT_WRTPlants01
URI =
2009-08-11 07:58:27.080:006:228 (3012:1540) - ENTER
ConfigManager::find(..)
2009-08-11 07:58:27.080:149:484 (3012:1540) - Transaction matched
Transaction Definition [RFT_WRTPlants01RFT_WRTPlants01] Testing against
client patterns
2009-08-11 07:58:27.080:278:772 (3012:1540) - Ignoring transaction
because it did not match a client definition.

ITCAM for Transactions provides a single default client group named All Clients that uses the IP filter value *. Leave this definition active so it can catch any transaction data that does not match other Client definitions.