This tech note describes steps to determine whether Transaction Analyzer is properly collecting data.
There are no specific requirements for this document.
The information in this document is based on these software and hardware versions:
Transaction Analyzer 1.95 or later
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
There are two different methods available to determine if Transaction Analyzer is collecting data.
You can run a report to determine if Transaction Analyzer is collecting data. Complete these steps:
Go to your report server, normally found at http://<report_server>/reports.
Go to the report, found at Home > Tidal Transaction Analyzer <report_server> > Tidal Transaction Analyzer Status.
Run the report, and you can find the number of records processed for any one SAP Server in the last day.
Another way to check is to review the Registry Editor. Complete these steps
Open the Registry Editor (regedit.exe) on your Transaction Analyzer server.
Go to the registry key for any particular SAP server, normally at HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > Tidal Software > Tidal Transaction Analyer > SAP for a 64 bit machine.
Note: If the machine is 32 bit, the registry path is the same minus the Wow6432Node component.
Inside this key, you see many GUIDs. Look in each one at the SystemId key for the server you want to track. You also see a date in the LastAuditPollTime key.
Refresh your registry (press F5) every so often, and the LastAuditPollTime continues to increment forward in time.
If you determine that your system is not collecting records, contact customer support as described in your TEO documentation.