Example: Conversion of Versión 7.0 resources to applications and libraries

You can convert individual WebSphere Message Broker Versión 7.0 resources to applications and libraries manually, or you can run the Convert Projects to Applications and Libraries wizard. This example shows how resources that have been created in WebSphere Message Broker Versión 7.0 can be converted to applications and libraries.

The Versión 7.0 resources

Resources have been created in Versión 7.0 to implement two solutions: "MyFirstSolution" and "MyOtherSolution".

MyFirstSolution consists of the following resources:
  • A message flow project called MyFirstSolution
  • A message set project called MyFirstSolutionMessageSet
  • A message flow project called CommonSubFlows, which might also be used by other solutions
  • A message set project called SharedMessageSet, which is also used by MyOtherSolution
MyOtherSolution consists of the following resources:
  • A message flow project called MyOtherSolution
  • A message set project called MyOtherSolutionMessageSet
  • A message set project called SharedMessageSet, which is also used by MyFirstSolution
The following images show how the resources for the two solutions are represented in the Versión 7.0 WebSphere Message Broker Toolkit.
The graphic illustrates how solution A consists of the message flow project called "MyFirstSolution", which depends on message flow project "CommonSubFlows", and message set projects "MyFirstSolutionMessageSet" and "SharedMessageSet". Solution B consists of the message flow project called "MyOtherSolution", which depends on message set projects "MyOtherSolutionMessageSet" and "SharedMessageSet".
The graphic shows the Broker Development view of the Versión 7.0 WebSphere Message Broker Toolkit and is described in the surrounding text.

The problems and the solution

The organization of the resources in the Versión 7.0 WebSphere Message Broker Toolkit does not make it clear which projects apply to which solution.

Similarly, deployed resources are shown as a flat list in the Brokers view of the WebSphere Message Broker Toolkit, and in WebSphere Message Broker Explorer. When it is time to deploy a solution, you need to know exactly which resources to add to your broker archive (BAR) file.

A lack of isolation is also an issue in this example. Both solutions use the message set project, SharedMessageSet. If you deploy a new SharedMessageSet message set project, the change affects both solutions. To use different versions of the SharedMessageSet project with each solution, you could deploy each solution to its own execution group, which might not be appropriate in your environment.

To resolve these issues, you can use one application to encapsulate all the resources required for MyFirstSolution, and another application to contain all the resources for MyOtherSolution. You can use libraries to contain the resources that are used by other solutions (the CommonSubFlows message flow project, and the SharedMessageSet message set project).

Conversion to applications and libraries

The following table lists the steps that are taken to convert the Versión 7.0 resources to applications and libraries.
  Conversion step Results
1. Import Versión 7.0 resources into the Versión 8.0 WebSphere Message Broker Toolkit. To convert the Versión 7.0 resources to applications and libraries, they are first exported from the Versión 7.0 WebSphere Message Broker Toolkit and imported into the Versión 8.0 WebSphere Message Broker Toolkit. The imported resources are initially listed under the Independent Resources category in the Versión 8.0 WebSphere Message Broker Toolkit. Message flow projects do not exist in Versión 8.0. Therefore, the Versión 7.0 message flow projects are converted automatically to Message Broker projects when they are imported.
This graphic shows the imported resources under the Independent Resources folder in the Versión 8.0 WebSphere Message Broker Toolkit.

At this stage, you could use the Convert Projects to Applications and Libraries wizard to analyze all the projects in the Independent Resources category and decide how to convert them. The wizard describes how it will convert the resources so that you can decide if the conversion is appropriate. For example, the wizard might decide to convert all message set projects to libraries in case any of them are required by other projects in the future. However, if you know that that message set project will only ever be used in one solution, you might choose to include that message set project in the application rather than making it a separate library. For the purposes of this example, the resources will be converted individually.

2. Convert shared projects to libraries. Dependent resources are converted first. The Versión 7.0 message flow project, MyFirstSolution, depends on the CommonSubFlows message flow project, which was converted to a Message Broker project automatically when it was imported into Versión 8.0. An application cannot refer to a Message Broker project. Therefore, MyFirstSolution cannot be converted to an application until CommonSubFlows has been converted. CommonSubFlows and SharedMessageSet are used by both solutions, therefore they are converted to libraries.
This graphic shows that CommonSubFlows and SharedMessageSet have been converted to libraries.
3. Convert the main projects to applications. If the message set projects, MyFirstSolutionMessageSet and MyOtherSolutionMessageSet, might be used by other solutions in the future, you would convert them to libraries at this point. This example assumes that the message set projects will be used in their associated solutions only. Therefore, the MyFirstSolution and MyOtherSolution Message Broker projects can now be converted to applications. You can see from the following image that the message set projects that were not converted to libraries are included in the relevant applications. The projects that were converted to libraries are listed as references for each application.
This graphic illustrates how the converted resources are displayed in the Versión 8.0 WebSphere Message Broker Toolkit.

The Versión 8.0 resources

After conversion, you can see more clearly which resources are used by each solution. At deployment time, you do not need to know exactly which resources are required by your solution. The following image shows how, on the Prepare tab of the BAR File editor, you select the application, and all required resources are deployed.

This graphic shows the Prepare tab of the BAR File editor, showing how all the resources to be deployed are listed under each application.

Similarly, the organization of resources is obvious when you are administering brokers in WebSphere Message Broker Explorer.

This graphic shows the deployed application and its associated resources in WebSphere Message Broker Explorer.

The following topics contain detailed instructions about how to complete these conversion steps: For a demonstration of how to convert resources to applications and libraries, see IBM Education Assistant module: Applications and Libraries conversion.
Avisos | Marcas registradas | Descargas | Biblioteca | Soporte | Comentarios

Copyright IBM Corporation 1999, 2013Copyright IBM Corporation 1999, 2013.

        
        Última actualización:
        
        Última actualización: 2013-09-23 03:03:08


Tema de conceptoTema de concepto | Version 8.0.0.3 | bc23822_