See information about the latest product version
Context
A company has developed a library that contains resources that are used in a number of WebSphere® Message Broker integration solutions. The company now wants to update the library resources and make the updated resources available to a number of the deployed integration solutions.
The company uses WebSphere Message Broker to develop and manage a number of integration solutions that transform and communicate payment data between source and target systems.
Some of the integration solutions were developed in WebSphere Message Broker Version 7.0 and are implemented as Message Broker projects. A Message Broker project is a container for all of the message flows and other resources that make up an integration solution. When you deploy a Message Broker project to the runtime environment, the resources are deployed directly into the execution group. After a Message Broker project is deployed, you can update and redeploy individual Message Broker project resources and the updates are immediately available to other resources in the Message Broker project. For more information about Message Broker projects, see Message Broker projects.
The rest of the integration solutions were developed in WebSphere Message Broker Version 8.0 and are implemented as applications. An application (a feature that was introduced in WebSphere Message Broker Version 8.0) is also a container for all of the resources that make up an integration solution. However, an application differs from a Message Broker project in that, when you deploy an application, the resources are deployed to the execution group in a self-contained environment. The application's self-contained environment provides runtime isolation for the resources within the application. Runtime isolation means that an individual application can be stopped, restarted, or updated without affecting, or being affected by, other resources that are deployed in the execution group. With runtime isolation you can control whether, and when, applications pick up updates to any resources that are shared with other integration solutions. For more information about applications, see Applications.
The company has developed a message map that describes how the payment data is mapped between the source and target systems. To make it easy to reuse the message map within all the integration solutions, the map and associated resources are stored in a library. A library is a container for a set of related resources that are typically used by more than one Message Broker project or application. By using a library, you can define and develop a single instance of a resource and then reuse it in several integration solutions. The library that contains the map and associated resources is referenced in all of the integration solutions in the scenario. For more information about libraries, see Libraries.
The company is about to start processing payments for a business partner, and the data structure of the business partner's payments is in a different format to other payments. A new message map is required to process these payments successfully. The new message map is developed and added to the library.
This scenario explains how to deploy the updated library so that the new message map is made available to the relevant integration solutions.