WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Comparison of libraries in applications and libraries in Message Broker projects
A summary of the differences that are associated with the use of libraries within applications and the use of libraries within Message Broker projects.
The following table compares ways in which tasks associated with managing libraries are implemented when you are working with applications and when you are working with Message Broker projects.
Task | Applications | Message Broker projects |
---|---|---|
Adding library references during resource creation. | You can add references to libraries when an application is created by selecting library names from the "Specify dependencies on libraries" panel. | You can add references to libraries when a Message Broker project is created by selecting library names from the "Specify dependencies on other libraries" panel. |
Adding library references to existing resources. | You can add references to libraries by right-clicking an existing application name and clicking Manage Library references in the Application Development pane in the WebSphere® Message Broker Toolkit. | You can add references to libraries by right-clicking an existing Message Broker project name and clicking Manage Library references in the Application Development pane in the WebSphere Message Broker Toolkit. |
Viewing library references in the development environment. | You can see the libraries that are referenced in an application from the application's References section in the Application Development pane in the WebSphere Message Broker Toolkit. | You can see the libraries that are referenced by a Message Broker project by right-clicking the Message Broker project and clicking Manage Library references in the Application Development pane in the WebSphere Message Broker Toolkit. |
Viewing library references in the runtime environment. | You can see the libraries that are referenced in a deployed application listed below the application name in the Brokers pane of the WebSphere Message Broker Toolkit. | You cannot see whether libraries are referenced by deployed Message Broker project resources. However, if a library is deployed directly to the execution group, the library's resources are available to any Message Broker project resources that are deployed to the same execution group. |
Updating a referenced library in a single application or Message Broker project. | Because of the runtime isolation that is provided by applications you can update and deploy the library in an application without affecting any other runtime resources (applications or Message Broker projects) that use the same library. | If you update and deploy a library that is used by multiple Message Broker project resources, the updated library is
automatically available to all of the Message Broker project resources in an execution group. To make updates to a library so
that the updates are only available to a single Message Broker project, you must do one of the following:
|
Deploy an updated library so that the updates are available to every application or Message Broker project that references the library. | Because of the runtime isolation that is provided by applications, you cannot deploy an updated library and have the updates available to every application. Instead you must rebuild and redeploy each application individually. | You can create a BAR file that contains just the updated library and deploy that to the execution groups where the Message Broker projects are deployed. |