The following classes represent the data types used to interact with the event correlator. EPL monitor and event type definitions (expressed as UTF-8 encoded strings of EPL code in C++) need to be created and manipulated through objects of the class com::apama::engine::MonitorScript in C++ and com.apama.engine.MonitorScript in Java. Both monitors and event types can be deleted explicitly from the correlator through the deleteName method of the EngineManagement object.

Event instances of a type that has already been defined with the correlator need to be created and encoded as com::apama::event::Event or com.apama.event.Event objects. EngineManagement itself implements an EventConsumer and defines a sendEvent method. This is used to inject Event instances into the correlator.

In C++ the developer is responsible for deleting both types of object (MonitorScript and Event) after they have been used.

If your application uses a locale that does not use UTF-8 encoding, any strings passed to the event correlator need to be converted to UTF-8. For conversion purposes use the following functions:

These functions convert between UTF-8 and what they assume to be the local character set. If this assumption is incorrect, unpredictable results may occur.