Migrating deployable resources
You can continue to use legacy resources in IBM® Integration Bus. However, if you want to continue developing resources created in previous versions, you must migrate them.
Before you begin
- Read the concept information about applications, libraries, and integration projects: Resource management overview.
- Read the concept information about subflows: Subflows.
- You can migrate message flow projects or integration projects by following the instructions in Importing resources from previous versions.
About this task
- Message sets: See Migrating message sets.
- Maps: See Migrating message maps.
- ESQL files: See Migrating ESQL files.
- Subflows: See Migrating subflows.
- Flows that use SSLv3: See Migrating a flow that uses SSLv3.
- Flows that contain JMS nodes: See Migrating a flow that contains JMS nodes.
- Flows that contain File nodes: See Migrating a flow that contains File nodes.
- Flows that contain ?wsdl queries: See Migrating a flow that supports ?wsdl queries.
- Custom integration applications: See Migrating custom integration (CMP) applications.
- Applications that contain SAP adapter projects: See Migrating an application that contains an SAP adapter connection project
| To continue developing in IBM Integration Bus Version 10.0 | Resource created in Version 7.0 | Resource created in Version 8.0 | Resource created in Version 9.0 |
|---|---|---|---|
| Message sets | You must enable the menus for message set development. | You must enable the menus for message set development. | You must enable the menus for message set development. |
| Message maps | You must complete the migration of message maps to graphical data maps. | You must complete the migration of message maps to graphical data maps for those legacy message maps that you did not convert when you migrated to Version 8.0. New maps created in Version 8.0 are graphical data maps. | You must complete the migration of message maps to graphical data maps for those legacy message maps that you did not convert when you migrated to Version 9.0. New maps created in Version 9.0 are graphical data maps. |
| ESQL files | You must complete the migration tasks. | You must complete the migration tasks. | You must complete the migration tasks. |
| Subflows | You must complete the migration of subflows created as .msgflow files into .subflow files. | You must complete the migration of the legacy subflows that you did not convert when you migrated to Version 8.0. New subflows created in Version 8.0 are created as .subflow files. | You must complete the migration of the legacy subflows that you did not convert when you migrated to Version 9.0. New subflows created in Version 9.0 are created as .subflow files. |
Migrating message sets
About this task
In WebSphere Message Broker Version 8.0 and later, message model schema files contained in applications, integration services, and libraries are the preferred way to model messages for most data formats. Message sets are required if you use the MRM or IDOC domains. For more information about message modeling, see Message modeling concepts.
You can import message flows containing message sets from previous versions into IBM Integration Bus Version 10.0. Your existing message sets can be viewed, modified, and deployed in the usual way. However, by default, the menu options for creating new message sets or message definition files are hidden. To perform these tasks, you must first enable message set development in the IBM Integration Toolkit Preferences.
For more information, see Enabling message set development.
Migrating message maps
About this task
IBM Integration Bus Version 10.0 includes a graphical data mapping capability, which is used when you add a Mapping node to a message flow.
- DataDelete
- DataInsert
- DataUpdate
- Extract
- Mapping
- Warehouse
The message mapping (.msgmap) on these Version 7.0 nodes can be viewed, compiled into a BAR file, and deployed to run the same transformation logic that was used in Version 7.0. However, the Version 7.0 message mapping operations are accessible only in read-only mode and cannot be modified. If you want to modify the transformation logic of an imported message flow that used Version 7.0 message mapping operations, you must replace the node with a new Mapping node and build a new graphical data map file (.map).
For information about converting Version 7.0 message maps (.msgmap) to Version 10.0 graphical data maps (.map), see Converting a message map from a .msgmap file to a .map file.
Migrating ESQL files
About this task
The required character set encoding for ESQL files that
are used in IBM Integration Bus Version 10.0 is UTF-8.
When a message flow project is migrated to an integration
project, any ESQL files that the
message flow project contains are read by using the character set
encoding that was used in the previous version of WebSphere Message Broker, and are rewritten in UTF-8.
When importing your message flow projects, note that the file encoding
of the workspace and host operating system must match the file encoding
with which the message flow projects were created.
Migrating subflows
About this task
Since WebSphere Message Broker Version 8, you create subflows as .subflow files.
Subflows from earlier versions of the product were created as .msgflow files. You must convert them into .subflow files if you want to continue developing them in IBM Integration Bus Version 10.0. You convert these subflows by using the function Convert to subflow.
For more information on how to convert a legacy subflow into a .subflow file, see Converting between message flows and subflows.