You can continue to use legacy resources in IBM® App Connect Enterprise. However, if you want to continue developing resources created in previous versions, you must migrate them.
To continue developing in Version 11.0 | Resource created in Version 9.0 | Resource created in Version 10.0 |
---|---|---|
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 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. | 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 10.0. New maps created in Version 10.0 are graphical data maps. |
ESQL files | You must complete the migration tasks. | No action required. |
Message flows | Rework your message flows if they include message flow nodes that are no longer available. | Rework your message flows if they include message flow nodes that are no longer available. |
Subflows | 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. | You must complete the migration of the legacy subflows that you did not convert when you migrated to Version 10.0. New subflows created in Version 10.0 are created as .subflow files. |
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 App Connect Enterprise Version 11.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 App Connect Enterprise Toolkit Preferences.
For more information, see Enabling message set development.
IBM App Connect Enterprise Version 11.0 includes a graphical data mapping capability, which is used when you add a Mapping node to a message flow.
The message mapping (.msgmap) on these Version 7.0 nodes can be viewed but they cannot be deployed to the runtime because they are not available in IBM App Connect Enterprise Version 11.0. 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 11.0 graphical data maps (.map), see Converting a message map from a .msgmap file to a .map file.
The required character set encoding for ESQL files that are used in IBM App Connect Enterprise Version 11.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.
The set of message flow nodes that are available at IBM App Connect Enterprise Version 11.0 might be different to the set of message flow nodes that are available at the version from which you are migrating. If your message flows contain message flow nodes that are no longer available, you must rework them to use only those message flow nodes that are available at IBM App Connect Enterprise Version 11.0.
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 App Connect Enterprise Version 11.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.