Apama applications that are to run within the event correlator can either be built natively in the Apama Event Processing Language or in Apama's in-process API for Java (JMon), or graphically through Apama’s Event Modeler. (The Apama Event Processing Language is the new name for MonitorScript.)

Although Apama includes a suite of tools to allow EPL code to be submitted to the event correlator interactively, as well as submit events from text files, it is often necessary to go further and integrate the event correlator directly with other software. Often this is required in order to drive custom graphical user interfaces, or to deliver messages to and receive messages from the event correlator (such as market data and order management).

In environments that require the event correlator to be integrated with middleware infrastructure and data buses it is usually preferable to do this with Apama’s Integration Adapter Framework (IAF). For information on developing adapters with the IAF, see The Integration Adapter Framework.

If your environment needs to interface programmatically with the event correlator, Apama provides a suite of Client Software Development Kits. These allow developers to write custom software adapters that interface applications, event sources and event clients to the event correlator. These adapters can be written in C, C++, or Java, or as .NET applications. In Java, adapters can be written in one of four interface layers: the Java Client API, the Java EngineClient API, the EventService API, or the ScenarioService API.

This topic describes how to use these Client Software Development Kits.