Integration

Infobus

Types of EAI

Data Level

Technique of moving data between data stores E.g.: Querying data from one or more table and writing to one or more tables Sharing methods existing in applications E.g.: Accessing methods exposed in EJB/Application Server Use the APIs provided by custom or packaged applications E.g.: SAP, PeopleSoft and BAAN

Method Level

Application Interface Level

The Middleware

A software that facilitates communication between two or more software systems Point-to-Point integration creates a spaghetti of connections between applications Accomplish integration using a Middleware Each application is an island of information

The Middleware
A B C E D A B

Middleware

Middleware - Advantages

Organizes Integration Hides complexities of the source and target systems Eases the maintenance and accommodates change seamlessly Creates a common communication protocol
5

Middleware - Components

Message

A unit of data, which may or may not contain header or additional information Messages usually have a structure (a schema) and content (data) Where the message is stored/persisted for a certain amount of time (Ideally till the subscriber receives it)
6

Message Queue

Middleware - Components

Publisher

Publishes the message from an application Usually done with the help of the applications API
Publisher
Database

Application API

Publisher Caller

Middleware - Components

Subscriber

Subscribes the message and sends it to the application using API or to the database

Subscriber

Listener

Callback

API

Application

Database
8

Middleware Features

Facilitate Asynchronous and Synchronous Communication Asynchronous Communication

An application or process, makes a call or passes data to another application and continues its process without waiting for a reply from the called application Disconnects after the call is made
9

Middleware Features

Synchronous Communication

An application or process, makes a call or passes data to another application and waits for reply Connection is not terminated until a reply received or timed out

10

Middleware - Features

Publish

The Applications that makes the call or sending the data is said to be publishing data Hence it is called a Publisher An Applications that receives the data is subscribing to that data And is called a Subscriber
11

Subscribe

Publisher - Subscriber
Publisher Subscriber

Publishes

Subscribes

Publish Subscribe is usually an Asynchronous communication

12

Request Reply

Is achieved through synchronous communication Publisher makes a Request to Subscriber and waits for Reply Times-out when there is no-reply in a pre-defined time
13

Request - Reply
Publisher
Request

Subscriber

Reply

14

Middleware - Features

Addressing Mode

Unicast Multicast Broadcast

15

Addressing Mode

Unicast

Publisher

One Publisher, publishes a message/data to one known Subscriber If the message/data needs to be sent to another subscriber, the data has to be sent again When the subscriber does not receive the data then it is sent again , until it receives the data
Subscriber

Publishes

Subscribes 16

Addressing Mode

Multicast

One publisher publishes a message/data to two or more known subscribers When a subscriber does not receive the message, it is sent again, until it receives the data

Publisher

Subscribes

Publishes

Subscribers

17

Addressing Mode

Broadcast

Publish messages to more than one known/unknown subscribers When the subscriber misses the message, it is lost not guaranteed
Subscribers

Publisher

Publishes 18

Middleware Types of Models

Logical Middleware Model

Point-to-Point

Ideal for two applications Example: RPCs Not fit for more than 2 applications Links many applications to many other applications Is the best fit for EAI
19

Many-to-Many

Middleware Different Models

Physical Middleware Model

Bus Model Hub-Spoke Model Multi-Hub Model

20

Hub-Spoke Model

App 1 Hub-Spoke

App 2

App 3

App 4

Is a Centralized configuration The Hub acts like a server All messages flow through the hub All messages are queued in the server Communication Protocol is Publisher-to-Server & Server-to-Subscriber E.g.: WebMethods
21

Bus Model

App 1

App 2

App 3

Bus

App 4

App 5

Decentralized Architecture Network bus acts as the message carrier Truly Distributed Middleware Communication pattern is peer-to-peer Messages are queued by Publishers E.g.: TIBCO
22

Multi-Hub Model
App 1 App 2 App 5

Hub
Hub

Hub
App 6 App 3 App 4

Multiple Hubs are linked together Load Sharing Provide Fail-safe service Complex to configure and maintain
23

Messaging Standards

The messaging standards are used by EAI and B2B integration. In fact, it is quite predominant in B2B integrations Following are some of the widely used standards

XML Extensible Markup Language EDI - Electronic Data Interchange RosettaNet Standards for Electronic Industry IDOCs Intermediate Document used by SAP OMG Open Management Group Standards OAG Open Applications Group Standards
24

Summary

Integration is essential for exchanging data between Applications and external enterprises Middleware delivers the following

Messaging Services Message Routing Rules Engine Middleware Models Hub and Spoke Bus Multi-hub Process Automation

25

Thank you

26