Receiving and storing debug information
Use the TestDriver API to set up a test driver instance that receives debug information from specified solution agents and caches the information. You can load test entities into the grid and submit test events for processing. From a test driver instance, use the DebugReceiver interface to capture outbound information from the events for debugging and problem determination.
About this task
The testdriver.properties file contains connectivity and server properties to set up the test driver instance, control which solutions and agents send information, and limit the amount of information that is cached. You can set several key properties to enable the test driver instance to receive debug information, including debugServers and debugAgentList in the properties file, and debugPort on the server. In a server topology, use the debug socket to enable the logging of debug messages. Both the debugServers test driver property and the debugPort system property must be set. On a cisDev server, a web socket for debugging is enabled by default. This socket uses the iaDevelopment feature and the iaSolutionDeveloper security role, which are included in the server.xml file by default.
The TestDriver API helps you monitor and capture event debug information that is generated by an external system and then picked up by an Insight Server. If a test driver instance is connected to the server and the agent that processes events is listed in the testdriver.properties file, then the debug information from the events is received and stored regardless of where the debug information originated.