Migrating development resources to IBM Integration Bus Version 10.0

You cannot migrate the IBM® Integration Toolkit or WebSphere® Message Broker Toolkit from previous versions, but you can install IBM Integration Bus Version 10.0 to coexist with a previous version, and migrate the development resources to the IBM Integration Toolkit Version 10.0

Before you begin

Be aware of the following restrictions that apply after you migrate resources to IBM Integration Toolkit Version 10.0.
  • You cannot share the development resources with previous versions of the WebSphere Message Broker Toolkit or IBM Integration Toolkit. When you create a new project in IBM Integration Toolkit Version 10.0, it is created in a format that cannot be used in previous versions of the WebSphere Message Broker Toolkit or IBM Integration Toolkit. You can take the following steps to manage development with different versions of the WebSphere Message Broker Toolkit or IBM Integration 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 an integration node at a version before Version 10.0, you must retain a WebSphere Message Broker Toolkit or IBM Integration Toolkit at the previous version.
    • If you need to continue development of the same project for integration nodes on both Version 10.0 and a previous version, ensure you use the WebSphere Message Broker Toolkit or IBM Integration Toolkit from the previous version for all your development.
  • You cannot deploy resources from IBM Integration Toolkit Version 10.0 to integration nodes at a previous version to Version 10.0.
  • If any of the following actions cause an error in the project, the IBM Integration 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
    For more information, see Applying a Quick Fix to a task list error. However, if you have different user-defined nodes that depend on different resources that have identical names, the BAR file compiler produces an error that indicates a naming conflict in the dependent resources.

About this task

You can continue to use resources from a previous version of WebSphere Message Broker or IBM Integration Bus by importing them into an IBM Integration Toolkit Version 10.0 workspace. After you import resources, you can no longer use them in a previous version of the WebSphere Message Broker Toolkit or IBM Integration Toolkit.

Message flow projects are replaced by integration projects in IBM Integration Bus Version 9.0 and later. When you import message flow projects into the IBM Integration Toolkit, they are converted automatically to integration projects. You cannot create a message flow project in IBM Integration Toolkit.

To migrate your projects by using a project interchange file, or to convert your message flow projects to integration projects, complete the steps in the following topics:

Results

You can now view and modify existing resources, and create new resources. You can deploy your workspace resources to IBM Integration Bus Version 10.0 integration nodes.

What to do next

If you migrated from WebSphere Message Broker Version 7.0 or WebSphere Message Broker Version 8.0, you might want to reorganize your resources by using the containers provided in IBM Integration Bus Version 10.0. 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 instructions about converting your migrated resources to applications and libraries, see Converting existing projects to applications and libraries.