A library is a logical grouping of related code, data, or both. A library typically contains reusable helper routines and resources such as subflows, ESQL modules, message definitions, maps, and Java™ utilities. You can use a library to group resources of the same type or function, and to aid the management and reuse of such resources
Two types of library exist in IBM® Integration Bus: shared libraries and static libraries.
Static libraries are represented by the static
library icon . Shared libraries are represented by the shared
library icon
.
A shared library can refer to other shared libraries only. Similarly, a static library can refer to other static libraries only.
mqsilist integrationNodeName -e integrationServerName -y sharedLibraryName
In
this example, the command lists the resources that are deployed in
a shared library, the integration server to
which that shared library is deployed, and any applications that refer
to the shared library.The following animation illustrates the difference between a static and shared library.
Shared library | Static library | |
---|---|---|
Support for libraries | Shared libraries are introduced in IBM Integration Bus Version 10.0. | The libraries that were introduced in WebSphere® Message Broker Version 8.0 are renamed as static libraries. |
Referencing libraries | If multiple applications reference a shared library, when the applications are deployed, each application uses the artifacts directly from the deployed shared library. | If multiple applications reference a static library, when the applications are deployed, each application has its own private copy of the library and the resources that are contained in it. |
Updating libraries | If you update and redeploy a shared library, all applications that reference that shared library see the updates automatically. | If you update a static library, you must repackage and redeploy each application that references that library, unless applications need to use different versions of that library. |
Deploying libraries | Shared libraries can be deployed directly to the integration server, or they can be deployed in the same BAR file as the applications that reference them. If a shared library is deployed in a BAR file, it can still be used by applications or shared libraries in other deployed BAR files. | Static libraries are packaged and deployed in the same BAR file as the applications that reference them. |