Using a replay log to diagnose problems
When you start the correlator, you can specify that you want it to copy all incoming messages to a special file, called a replay log. Incoming messages include the following:
Events
MonitorScript
Java
Correlator Deployment Packages (CDPs)
Connection, deletion, and disconnection requests
A replay 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 replay log. If you are unable to diagnose the problem, you can provide the replay log to Software AG Global Support. A support engineer can then feed your replay log into a new correlator to diagnose the problem.
The information in the following topics can help you implement and use a replay log:
Copyright © 2013
Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or Terracotta Inc., San Francisco, CA, USA, and/or Software AG (Canada) Inc., Cambridge, Ontario, Canada, and/or, Software AG (UK) Ltd., Derby, United Kingdom, and/or Software A.G. (Israel) Ltd., Or-Yehuda, Israel and/or their licensors.