See information about the latest product version
Migrating development resources to WebSphere Message Broker Toolkit Version 8.0
You cannot migrate the WebSphere® Message Broker Toolkit from previous versions, but you can install WebSphere Message Broker Toolkit Version 8.0 to coexist with a previous version, and migrate the development resources that you created in your workspace.
- You cannot share the development resources with previous versions
of the WebSphere Message Broker Toolkit. When you
create a new project or open an existing project in WebSphere Message Broker Toolkit Version
8.0, it is converted to
a new format, which cannot be used in previous versions of the WebSphere Message Broker Toolkit. You can take the
following steps to manage development with different versions of the WebSphere Message Broker Toolkit.
- If you are using a version control system, create a new stream for use with the new version of your project.
- If you expect to continue development of a project for a broker at a version before Version 8.0, you must retain a WebSphere Message Broker Toolkit at the previous version.
- If you need to continue development of the same project for brokers on both Version 8.0 and a previous version, ensure you use the WebSphere Message Broker Toolkit from the previous version for all your development.
- You cannot deploy resources from WebSphere Message Broker Toolkit Version 8.0 to brokers at a previous version to Version 8.0.
- If any of the following actions cause an error in the
project, the WebSphere Message Broker Toolkit flags the
error, and you can use a Quick Fix to rectify the error.
- Creating the metadata information for the user-defined node project
- Correcting the plug-in identifier if it does not match the project name
- Ensuring all the user-defined nodes are in the same category
- If you have a deployable JAR file (for a user-defined node) that was created in a version before Version 8.0, you cannot migrate this file to Version 8.0.
You can continue to use resources from a previous version of WebSphere Message Broker by migrating or importing them into a WebSphere Message Broker Toolkit Version 8.0 workspace. After you import resources, you can no longer use them in a previous version of the WebSphere Message Broker Toolkit.
Message flow projects are replaced by Message Broker projects in WebSphere Message Broker Version 8.0. When you import message flow projects into WebSphere Message Broker Version 8.0, they are converted automatically to Message Broker projects. You cannot create a message flow project in WebSphere Message Broker Toolkit Version 8.0.
Migrating your WebSphere Message Broker Toolkit workspace
To migrate your WebSphere Message Broker Toolkit workspace to WebSphere Message Broker Version 8.0, complete the following steps.
- Install WebSphere Message Broker Toolkit Version 8.0 in a different location from the current version of WebSphere Message Broker Toolkit. For detailed instructions, see Installing the WebSphere Message Broker Toolkit, or refer to the Installation Guide.
- When you start WebSphere Message Broker Toolkit Version 8.0 for the first time, you are prompted to enter a workspace location. Enter the directory that contains the WebSphere Message Broker Toolkit workspace that you want to migrate and click OK. The workspace and resources are now available in WebSphere Message Broker Toolkit Version 8.0.
- In the Broker Application Development perspective, select to ensure that all views and menus are updated for WebSphere Message Broker Toolkit Version 8.0.
- You must migrate any user-defined node source projects that were developed in a previous version. An error is displayed on all projects that require migration. You can use a Quick Fix to clear these errors. See Applying a Quick Fix to a task list error.
Importing resources in a Project Interchange file
To import resources in a Project Interchange file, complete the following steps.
Results:
You can now view and modify existing resources, and create new resources. You can deploy your workspace resources to WebSphere Message Broker Version 8.0 brokers.
After migration, your resources are contained in a Message Broker project. You can then decide how you want to organize your resources. Applications are typically used to contain all the resources that are required for a particular solution. Libraries are typically used to contain resources that you might want to reuse. So you might decide to store your main message flow in an application, and store your reusable resources in a library. For an example of how you might convert your resources, see Example: Manual conversion of Version 7.0 resources to applications and libraries. For instructions about converting your migrated resources to applications and libraries, see Converting existing projects to applications and libraries.
Next: