IBM Integration Bus v10 has introduced many new features. One of the important feature, from my point of view, is the introduction of Shared Library concept.
We all know that WebSphere Message Broker v8 provided new ways of organizing resources in toolkit by introducing
Application container, as per the info-center, is a container for all the resources that are required to create a solution.
Provides run-time isolation –> resources inside the application are not visible to other resources
Used when updates to one group of deployed resources should not affect another group of deployed resources
Library container, for organizing resources for re-usability. Can be referenced by applications or services or integration projects.
WMB v8 introduced Static library
The behavior of the library container introduced in WMB 8 and used in IIB v9, as per info-center are provided below
Drawback of Library used in WMB 8 / IIB 9: Owing to Application / Service’s run time isolation behavior, we solution developers faced major challenges on deciding whether to organize our solution using Applications / Services or using Integration Projects.When solutions were organized using Applications / Services and the reusable artifact(s), like Common Error Handling framework / logging framework, organized using libraries, each application / services carried copy of library within themselves. As a result, any changes made to these reusable artifact always resulted in need to re-deploy all applications / services.
In that regards, organizing the resources as Integration Projects was better and very much appealing.
But IIB v10 has addressed this concern / problem by introducing Shared Libraries. Now the Applications / Services do not take copy of the Shared Library within themselves. As the Shared Libraries are deployed directly at the Integration Server level.
Advantages of Shared Libraries
Shared Libraries can be added to the BAR file independently of referencing Applications / Services
Deployment of updated Shared Library results in the changes immediately picked up by all referencing applications / services at run-time. Hence no need to redeploy all referencing applications / services
Enables using / referencing to multiple XML or DFDL schema files that declare the same elements and types, by having them stored in separate Shared Libraries
Shared Library vs Static Library from Toolkit to Run-time
In the New Library window, specify the name for the library and selecting the library type as “Shared Library”, click Finish
Below Images shows the Shared and Static libraries in the toolkit
Referencing to Shared Library / Static library from Application is shown below
When adding to the BAR file, Shared Libraries are displayed in the BAR Editor separately and have to be selected explicitly for adding to the bar file. This is not the case with Static Library as they are added automatically when application referencing them is added to BAR file.
After deployment, you could notice the difference between Shared & Static library. Static library copy will be present within the application container, where as the Shared Library is outside the application container and directly under the Integration Server.
Hope this blog provides insight into Shared Library feature of IIB 10.
For any corrections / suggestions / query please do drop a note to firstname.lastname@example.org (or) email@example.com.