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

Making a new version of a library available to Message Broker project resources

You make the updated library available to the Message Broker projects by deploying the library to the runtime environment.

Before you begin

About this task

The company identifies an appropriate maintenance period during which they can update the Message Broker projects by deploying the updated library to the runtime environment.
Note: It is not possible to update resources that are associated with just one of the Message Broker projects. If the company wants only one of the Message Broker projects to use the new library, they must move one of the Message Broker projects to another execution group, or convert one of the Message Broker projects to an application. For more information, see Converting a Message Broker project to an application.

Complete the following steps to create a BAR file that contains just the MessageMappingLib library and deploy it to the execution group.

Procedure

  1. From the WebSphere® Message Broker Toolkit menu, select File > New > Bar File. The New Bar File dialog box opens.
  2. In the Name field, type MappingLib and click Finish. The BAR File editor opens.
  3. Click the Message flows, libraries and other message flow dependencies radio button. Any libraries and Message Broker project resources in the workspace are displayed.
  4. Select the MessageMappingLib check box and then click the Build and Save button. The message: Operation completed successfully is displayed.
  5. Click OK. The MappingLib.bar file is added to the BAR Files in the Application Development pane.
  6. Stop the Proj1Flow1 message flow in the runtime environment by right-clicking the message flow in the Brokers pane and clicking Stop. The Proj1Flow1 message flow is stopped.
  7. Stop the Proj2Flow1 message flow in the runtime environment by right-clicking the message flow in the Brokers pane and clicking Stop. The Proj2Flow1 message flow is stopped.
  8. Right-click the MappingLib.bar file, click Deploy, select the execution group and click Finish. The MessageMappingLib library is updated in the runtime environment.
  9. Restart the Proj1Flow1 message flow in the runtime environment by right-clicking the message flow in the Brokers pane and clicking Start. The Proj1Flow1 message flow is restarted.
  10. Restart the Proj2Flow1 message flow in the runtime environment by right-clicking the message flow in the Brokers pane and clicking Start. The Proj2Flow1 message flow is restarted.

Results

You have deployed your updated library to the runtime environment. You can see that the new map is included in the library that is deployed directly in the execution group. As a result, the new map is now available to both of the message flows from the Message Broker projects. However, the new map is not included in the libraries that are associated with the applications, and the applications do not have access to the new map within the library that is deployed directly in the execution group.
This screen capture is described in the preceding text.

What to do next

Redeploy one of the applications so that the application can use the updated library. See Making a new version of a library available to an application.