IBM App Connect Enterprise Architecture | SNSEduHub

IBM App Connect Enterprise Architecture

In simple words Information packaged as a message will flow between different applications using IBM app connect enterprise. The IBM App Connect Enterprise Architecture is divided into two halves. The IBM Integration Bus Architecture does not have an Independent Integration Server only Integration Node that exists when compared to IBM App Connect Enterprise. Where Integration Node is also called as Broker. The Architecture is given below:

Once we install IBM App Connect Enterprise software we will get the IBM App Connect Enterprise Toolkit and Console with the help that we will create an Integration Node / Broker. Through IBM ACE Console we will use the command to create the Broker.

Integration node / Broker:

The Broker hosts one or more message flows for routing, transformation, and enrichment of messages.

 

Integration server:

Each integration server runs as its own operating system operation, providing an isolated runtime environment for a collection of deployed message flows.

Independent Integration Server:

The Independent Integration server is also the same as the integration server but it doesn’t depend on Integration Node and it implements all the operations which are done by the Integration Node. Used to deploy on Cloud Environment and as well as deployment on On-Premise made easy.

IBM App Connect Enterprise WebUI:

The IBM ACE WebUI inherits whenever we create the independent Integration Server and Integration node dynamically it is provided with the ports which are able to access the IBM ACE WebUI. 

Application:

An application is a container that holds all of the resources needed to build an Integration Solution. Flows, message definitions, libraries, and JAR files are in IBM App Connect Enterprise.

Message Flow:

It is a sequence of processing steps that run in the integration node when an input message is received, Develop an integration solution to the respective flow.

Library:

Libraries are two types in the IBM App Connect Enterprise i.e 

1. Static Library

2. Shared Library

The Libraries are key for application development factors for which we can create exception handling or database queries and set those as a shared or static library then we can use for multiple applications. Whenever we referred our respective application with the Shared Library then we need to deploy the library before the deployment of the application.

NOTE: With the Integration Server or Independent Integration Server able to expose service or can deploy to external systems like Cloud and On-Premise. So that End-User can access the application.

Comparing Architecture Of IIB and IBM ACE

In the IIB the architecture is simple and there is no cloud deployment but we can deploy IIB to the On-Premise. The IBM ACE also can be deployed to the On-Premise But here we have Cloud Deployment option and IBM Cloud is more friendly to the IBM ACE as compared to the IIB. The main key difference that can be visible is as I already mentioned in the above paragraph i.e the Independent Integration Node. 

stay safe and happy learning.