The Adaptris Embedded Mediation Framework (EMF) is a highly productive environment for building Mediation Plugins that connect applications, communication mechanisms, data sources, and data structures within a Service Oriented Architecture (SOA).

OVERVIEW

Adaptris Mediation Plugins are built around our Embedded Mediation Framework. The Adaptris EMF is the architecture within which the Mediation Plugins are built and executed.  The EMF provides Eclipse-based development and configuration tooling which can be embedded within your ESB or other integration vendors' tools.  The EMF provides libraries of pre-built services for connecting to, and mediating between many different IT assets.  Whilst we provide a large number of pre-built Mediation Plugins, where none exists for a specific task, a new Mediation Plugin can be quickly configured using the Adaptris Mediation Framework Builder tool and selecting from the palette of integration services we provide.  These integration services can be extended with your own custom built services hosted within the EMF or via external services.

ADAPTRIS EMF ARCHITECTURE

The EMF is a design pattern for creating Mediation Plugins that connect and mediate the differences between two endpoints in a SOA environment.  The Adaptris EMF is designed to work either stand-alone or embedded into an Enterprise Service Bus.

Container

The Adaptris EMF features an elegantly simple architecture hosted within a container that can be deployed within an ESB, an AppServer or stand-alone.

Channel 

Within the container a connection is made to the systems being integrated.  A library of existing connections exist to simplify connection to the most remote systems.  This library includes connections to Web Service, JMS, File System, FTP, HTTP(S), JDBC, email, MQ Series, MSMQ, SAP Business COnnector, TIBCO RV amongst others.

A channel forms a one way communication mechanism between the consume and produce connections. Multiple channels allow for bi-directional communication.

Workflow

Once a connection has been established to each of the systems being integrated and a channel is in place to allow the messages to flow between them, the task of processing the messages falls to the workflow system.  In its simplest form the workflow may consist of a one step process. Alternatively, comprehensive service collections and branching logic can be applied to handle the most complex of integration tasks.

Transit Services

Transit services can then be applied to the messages that flow across the Mediation Plugin under the control of the workflow system. These transit services provide many functional capabilities including error and event handling, security and message transformation. These services manipulate messages in transit across the Mediation Plugin. Libraries of existing services are supplied and these can be extended by developing custom services or by invoking external web services.

Mediation Plugin Architecture

This elegantly simple architecture combined with the pre-built library of connection and transit service allow new Mediation Plugins to be built and deployed extremely quickly.

CONNECTION TYPES

Several connection types are supplied with the Mediation Framework.  Some of the more commonly implemented connection types are listed below.

• File System
• FTP
• HTTP(S) and Web Services
• JMS
• JDBC
• Email
• Odette File Transfer Protocol (OFTP)
• MQ Series / WebSphere MQ
• Microsoft Message Queuing (MSMQ)
• SAP Business Connector
• TIBCO Rendevous

TRANSIT SERVICES

Perhaps the greatest strength of the Adaptris EMF is in the diversity of connection types and services that it provides.

• Metadata Services
• Transformation Services
• Security Services
• Inline Connection Services
• Miscellaneous Services. branching, compression, splitting, etc

Further information on the Adaptris EMF Architecture can be found in our Embedded Mediation Framework whitepaper.