IBM App Connect Enterprise Architecture
IBM App Connect Enterprise V11.0 is one of the IBM product it is a latest version, it provides platform to integrate applications and services and it provides connectivity support with App Connect Professional and the App Connect Connectors on IBM Cloud and independent integration servers added into to the IBM app connect enterprise architecture not only under integration node
On Cloud also IBM App Connect Enterprise offers flexible integration. It delivers a fully managed Integration environment providing integration across all platforms. It provides secure integration without maintain IT infrastructure.
• It provides simplified delivery and flexible integration instead of complex point-to-point connectivity
• Introduced Graphical, configuration-driven development model and Subscription-based consumption
• Now exclusively available IBM-managed integration environment on IBM Soft Layer
• Maintenance of Cost is reduced.
• It allows business to deliver solutions faster
• It Provides loosely couple architecture for SOA.
• It delivers faster time to value for multiple hybrid integrations
The integration servers are added, if you are planning to run the App Connect Enterprise with a container framework such as Kubernetes or IBM Cloud Private, so in this situation using independent integration servers would be the better choice.
Integration node is set of execution group that are host one or more message flow to Routes, transforms, and enriches in-flight messages, Can be many integration nodes.
Integration server is named grouping of message flows that are assigned to an integration node, each integration server is a separate operating system process.
Message flow is sequence of processing steps that run in the integration node when an input message is received
Application is a container of resources that are required to create a solution such as message flow, sub flows, message definition (DFDL, XSD files) Reference message models that describe the data
A library is a logical grouping of related code, data, or both. A library typically contains reusable helper routines and resources such as sub flows, ESQL modules, message definitions etc. it consist of two types
If you want to deploy and manage just one copy of those common resources, use a shared library. A shared library can be deployed directly to an integration server. Any application can reference the resources in that deployed shared library. If that shared library is updated, the changes are immediately visible to all referencing applications.
If you want each application to use a different version of the contained resource, use a static library. Each application that references that static library is deployed with its own private copy of that library. If a static library is updated, each application that references it must be repackaged and redeployed with the updated static library.