Apama 10.7.2 | Deploying and Managing Apama Applications | Correlator Utilities Reference | Replaying an input log to diagnose problems
 
Replaying an input log to diagnose problems
 
Creating an input log file
Rotating an input log file
Performance when generating an input log
Reproducing correlator behavior from an input log
When you start the correlator, you can specify that you want it to copy all incoming messages to a special file, called an input log. An input log is useful if there is a problem with either the correlator process or an application running on the correlator. If there is a problem, you can reproduce correlator behavior by replaying the messages captured in the input log. Incoming messages include the following:
*Events
*EPL
*Java
*Correlator deployment packages (CDPs)
*Connection, deletion, and disconnection requests
If you are unable to diagnose the problem, you can provide the input log to Software AG Global Support. A support engineer can then feed your input log into a new correlator to try to diagnose the problem.
The information in the following topics describes how to generate and use an input log. See also Examples for specifying log filenames.
Regularly rotating log files and storing the old ones in a secure location may be important as part of your personal data protection policy. For more information, see Handling personal data "at rest" in the correlator input log file.