Apama 10.15.3 | Connecting Apama Applications to External Components | Working with IAF Plug-ins | The Integration Adapter Framework
 
The Integration Adapter Framework
 
Overview
Architecture
The transport layer
The codec layer
The Semantic Mapper layer
Contents of the IAF
This section describes how to use the Apama Integration Adapter Framework (IAF). The IAF is a middleware-independent and protocol-neutral adapter tailoring framework designed to provide for the easy and straightforward creation of software adapters to interface Apama with middleware buses and other message sources. It provides facilities to generate adapters that can communicate with third-party messaging systems, extract and decode self-describing or schema-formatted messages, and flexibly transform them into Apama events. Vice-versa, Apama events can be transformed into the proprietary representations required by third-party messaging systems. It provides highly configurable and maintainable interfaces and semantic data transformations. An adapter generated with the IAF can be re-configured and upgraded at will, and in many cases, without having to restart it. Its dynamic plug-in loading mechanism allows a user to customize it to communicate with proprietary middleware buses and decode message formats.
There are two ways of integrating with Apama through software. The first is to use the low-level Client Software Development Kits (SDKs) to write your own custom software interface (see Developing Custom Clients). The second is to instantiate an adapter with the higher-level Integration Adapter Framework (IAF). This is described in the topics below.
Note:
The IAF architecture is superseded by connectivity plug-ins. Therefore, Software AG strongly recommends choosing connectivity plug-ins over the IAF when creating new adapters and connectivity. Non-capital markets use of the IAF is deprecated.