See information about the latest product version
Migrating deployable resources
You can continue to use legacy resources in WebSphere® Message Broker Version 8. However, if you want to continue developing resources created in WebSphere Message Broker Version 6 and Version 7, you must migrate them.
- Read the concept information about applications and libraries: Applications and libraries.
- Read the concept information about subflows: Subflows.
- You can migrate message flow projects by following the instructions in Importing resources from previous versions.
- Message sets: For more information, see Migrating message sets.
- Maps: For more information, see Migrating message maps.
- ESQL files: For more information, see Migrating ESQL files.
- Subflows: For more information, see Migrating subflows.
To continue developing in WebSphere Message Broker Version 8.0 | Resource created in Version 6 | Resource created in Version 7 |
---|---|---|
Message sets | 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. |
ESQL files | 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 subflows created as .msgflow files into .subflow files. |
Migrating message sets
In WebSphere Message Broker Version 8.0 and later, message model schema files contained in applications 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 WebSphere Message Broker Version 7.0 into WebSphere Message Broker Version 8.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 WebSphere Message Broker Toolkit Preferences.
For more information, see Enabling message set development.
Migrating message maps
WebSphere Message Broker Version 8.0 provides a new 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 8.0 graphical data maps (.map), see Converting a message map from a .msgmap file to a .map file.
Migrating ESQL files
The required character set encoding for ESQL files that are used in WebSphere Message Broker Version 8.0 is UTF-8. When a message flow project is migrated to a Message Broker 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
In WebSphere Message Broker Version 8, you create subflows as .subflow files.
When you import subflows created in earlier versions of the product into WebSphere Message Broker, that is, subflows created as .msgflow files, you must convert them into .subflow files if you want to continue developing them. 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.