Apama Documentation : Developing Apama Applications : Developing Apama Applications in EPL : Using Correlator Persistence : Description of state that can be persistent
Description of state that can be persistent
A correlator that is running with persistence enabled automatically stores state on disk and automatically recovers state when it restarts. Saved state includes the following:
*For a persistent EPL monitor, all of that monitor's state is saved. This includes all events, strings, primitives, sequences, dictionaries, action variables, closures, and global variables. It also includes all the state of listeners, streams and queries — local variables captured by them and all active listeners, sublisteners and queries, including the events currently flowing through them.
*All source code that was injected into the correlator, including any non-persistent EPL monitors and JMon monitors. EPL files that were injected from a Correlator Deployment Package are not stored in plain text.
Code that is not injected includes the following:
*Correlator plug-ins, which are imported at runtime. The actual plug-in file must be on a specified path that the correlator can load it from.
*Any Java class files on the correlator's classpath but not injected.
*The correlator runtime itself.
*Contents of all context queues.
*Some correlator-global state including integer.getUnique() IDs and context IDs.
Note:  
In general, chunks cannot be persistent. However, chunks used by the Apama Time Format correlator plug-in and the Apama MemoryStore plug-in can be persistent.
Copyright © 2013-2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback