What is EAI?

-
From Wikipedia's definition the Enterprise application integration (EAI ) is the use of software and computer systems' architectural principles to integrate a set of enterprise computer applications.

But what it exactly mean? Before going to definition of EAI, think of legacy banking computer systems connected to each other in Ad hoc manner. Inventory component is storing large database of users. Accounting component manages complex calculations of end users. Front end components are consumed by bank officials and bank users. Each of this component is connected and requesting each other for information. Those components are used to connected point to point or one to many manner.


Front end components used to call inventory components for querying users details and then it calls accounting component for managing fund transfers etc. This leads to complex system interconnection. Debugging and fixing such system used to become hectic. This system was prone to failure due to point to point contact and no main backbone systems.

EAI provided solution for above problem. Each of the component is connected to backbone component called ESB(Enterprise Service BUS). ESB is implemented using Java Messaging Service(JMS). The each components call other component via ESB. The routing and processing logic is implemented using ESB services. ESB encapsulates buisness logic from front end components. The ESB services are implemented using SOAP/HTTP, JMS, REST and expose APIs to front end services via RESTful APIs(JSON). The main advantage of ESB that it provides error handling and fault tolerance capability. The messaging between ESB services is done via XML/IDOC(For SAP CRM Systems). Front end system uses much more lighter messaging format JSON.

Below diagram shows the difference between legacy systems and EAI implementation using ESB.


Comments

Post a Comment

Popular posts from this blog

Spring | Using TIBCO EMS with Spring framework

-
TIBCO EMS can be use with Spring Framework to support message publishing and subscription. Spring provides JMS template to send JMS messages and @JmsListener/ MessageListener to subscribe it. Steps 1 : Create new project in eclipse or IntelliJ Idea Create new project with Spring dependency. We can use maven to add all required libs for this project. Maven takes care of adding referred java libs to build path. TIBCO JMS jars need to be added to build path. Pom.xml will be as follows. As you can see in above pom file we have added TIBCO JMS and Spring JMS dependency. Step 2 : Create JMS bean configuration file(Jms-conf.xml) Next we will create bean configuration file. It will set JNDI and JMS properties. We can use same JMS listener class to subscribe multiple queues and topics. Spring bean configuration take care of JMS transport setup. Env variables values can be provided via properties file. Step 3 : Create JMS Queue/Topic sender and Listner ...
Read more

TIBCO | For Loop - Accumulate output

-
Image
In this post we will check how TIBCO for loop works. TIBCO provides Group Activity to iterate over processes or activities. Loops can be different types eg. For Loop, While util loop, if loop, repeat on error etc. TIBCO group can loop over sub-process and accumulate output in end activity to be used by next activities. TIBCO For loop with Accumulate output repeats over process/activity and return output of each iteration in output activity. This is helpful where we want to call sub-process repeatably with different input parameters and store each output in some variable.
Read more

TIBCO | JNDI Server & JMS Instance creation

-
Image
In this post we will be creating TIBCO JNDI server and other instance pointed to JNDI server. First lets see what is mean by JNDI. It is   Java API for a directory service that allows Java software clients to discover and look up data and objects via a name. TIBCO EMS uses JNDI concept to lookup for EMS objects and its relations in messaging service. While developing enterprise level TIBCO solution it is advise or say standard practice to create one JNDI server(also one backup JNDI server) and other instance servers according to the functionality or domains. In this tutorial we will be creating one JNDI server and two domain servers.
Read more