Troubleshooting the Transaction Tracking installation and configuration

If you are experiencing difficulties after installing Transaction Tracking, review this section first to help you resolve any problems.

• The Transaction Tracking workspaces are not displayed in the Navigator.

  If the Transaction Tracking workspaces are not visible at all, check that you have installed Tivoli Enterprise Portal Server support on the computer running the Tivoli Enterprise Portal Server.

• The Transaction Tracking workspaces are displayed in the Navigator, but have unusual names.

  If the workspaces are visible but have names starting with kto, check that you have installed Tivoli Enterprise Portal Desktop Client support on the computer running the Tivoli Enterprise Portal.

• The Transaction Tracking workspaces are not available.

  If the workspaces are visible but not available, the Data Collector plug-in has successfully run in the past but conditions have changed: either the Data Collector plug-in or Transaction Reporter are not running now or the connection information to the Tivoli Enterprise Monitoring Server has changed. Check the Data Collector plug-in and Transaction Reporter services in the Manage Tivoli Enterprise Monitoring Services window.

• The Transaction Collector and Transaction Reporter are not available in the Navigator after updating IBM Tivoli Monitoring.

  Always restart both the Transaction Collector and Transaction Reporter after updating IBM Tivoli Monitoring.

• When does polling start and when should I see data in the workspaces?

  After you have installed a Data Collector plug-in you should start to see data from that node within a few minutes. If you do not see any data, check that all components, including the Data Collector plug-in are running. Also check the connection to the Tivoli Enterprise Monitoring Server and other ktoenv configuration settings using Manage Tivoli Enterprise Monitoring Services.

  If you installed on a distributed system, check that you installed the correct support files on each computer.

• There is no data in the history workspaces

  Check that you have configured the historical data collection for the data source. In addition, check that you have configured pruning and summarization of the data.

• A node running the Data Collector plug-in is not displayed in the Navigator.

  If the node is not visible at all, the connection between the Data Collector plug-in and the Tivoli Enterprise Monitoring Server is not configured correctly. Reconfigure the Data Collector plug-in on that node.

  This may also occur when data from one Transaction Collector overwrites that from another. Ensure that the time for all Transaction Collectors is synchronized.

• After editing a context mask file, some column titles are missing.

  By default in the context mask file (contextmask_default.cfg), the entry Application exists and is copied to both BusinessApplication and Component columns in workspaces. You can edit the context mask file so that distinct component and business application names are displayed. To do this you must provide both BusinessApplication and Component entries. If you only provide one entry the other column will be blank in the workspaces.

• MQ Tracking events are not displayed in the Tivoli Enterprise Portal.

  Ensure that the path you specified using itmcmd config -A tu to the context mask directory is correct. The path should not contain a trailing slash. For example, on Windows the path should be C:\IBM\ITM\TMAITM6 by default.

• The Transaction Collector won't start on UNIX systems using itmcmd.

  The agent cannot be started on UNIX systems using itmcmd if the current working directory is not writable.

• Topologies are not displayed.

  If the topology viewer is not initialized properly in the Tivoli Enterprise Portal Server, topologies may not be displayed. Reconfigure the Tivoli Enterprise Portal Server.

• Why can't I see any data from WebSphere®?

  Ensure that you have enabled ARM, see Enabling ARM on WebSphere.

  If Java™ 2 security is enabled in WebSphere, ensure that you have set Java 2 security policies. If you do not set the Java 2 security policies for ARM libraries, the libraries cannot be loaded, and you will see an error similar to the following in the logs: SECJ0314W: Current Java 2 Security policy reported a potential violation of Java 2 Security Permission.

• KBB RAS1 logging is not working on a Windows 64-bit system.

  On all Windows 64-bit systems, the Microsoft Visual Studio 2008 runtime, msvc90.dll, must be installed for KBB RAS1 logs to be generated. If msvc90.dll is not installed, download and run the Microsoft Visual C++ 2008 Redistributable Package (x64).

• When I attempt to install a Transaction Tracking agent, my AIX platform is not listed in the OS or component support category list.

  You can install Transaction Tracking agents to AIX 6.1 systems, even though the operating systems are not listed. In the OS or component support category list, select the number corresponding to AIX R5.3 (32 bit) or AIX R5.3 (64 bit) instead. The agents will install successfully, but the architecture code will be aix533 instead of the expected aix613 or aix616.