Developing Apama Applications > Developing Clients > The Client Software Development Kits
The Client Software Development Kits
Apama applications that are to run within the event correlator can either be built natively in The Apama Event Processing Language (EPL) or in Java, 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 (like 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 in Developing Adapters.
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 applications that interface existing enterprise applications, event sources and event clients to the event correlator. These custom applications can be written in C, C++, Java or .NET. In Java, applications can be written in one of four interface layers. The Java and .NET interfaces, in order of increasing abstraction are:
*Raw, low-level Java/.NET Client API — Base layer upon which the other Java/.NET API layers are built. This is equivalent to the C++ SDK.
*Java Beans API/.NET Engine Client API — More powerful and provides extensive higher level functionality.
*EventService API — Use when attaching a listener to a named channel or when using events as a messaging transport for synchronous or asynchronous pseudo RPC mechanisms.
*ScenarioService API — Used to provide an interface to scenarios that have been built with Event Modeler.
This section of the documentation describes how to use these Client Software Development Kits.
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.