You can compile and deploy legacy message maps and legacy message flow nodes in WebSphere® Message
Broker Version 8 and later versions. However, if you need to
modify any of these resources, you must convert them into message
maps that the new Mapping node consumes.
About this task
A legacy message map is a message map created as a .msgmap
file in earlier versions of WebSphere Message
Broker, for
example in WebSphere Message Broker Version 7.
Note: From WebSphere Message
Broker Version 8 onwards, legacy message maps are accessible in read-only
mode and cannot be modified by using the IBM® Integration Toolkit.
The functions provided by the following legacy
message flow nodes in
WebSphere Message Broker Version 7 are replaced with the new
Mapping node in
WebSphere Message
Broker Version 8 and later versions:
- DataDelete node
- DataInsert node
- DataUpdate node
- Extract node
- Mapping node
- Warehouse node
Procedure
Follow these guidelines when you use legacy message maps and legacy message flow nodes in your integration
solutions:
-
You can import message flows developed in
earlier versions of WebSphere Message
Broker that use
legacy message maps.
-
You can import a message flow that contains
legacy message flow nodes. You can continue to
view and deploy these nodes, but you cannot modify them.
-
You can compile and deploy message flows that
use legacy message maps and legacy message flow nodes.
If you use a legacy message map as part of your integration
solution, the BAR file that you use to deploy the solution must have the option Compile
and in-line resources set. This setting might be incompatible with some other functions,
such as deployable subflows that require deploy as source mode. For more information, see Adding resources to a BAR
file.
-
You must convert a legacy message map to a message map before you can modify any of its
mapping operations by using the Graphical
Data Mapping editor. For more information, see Converting a message map from a .msgmap file to a .map file.
You can convert your legacy message map created
as a .msgmap file to a message map created as a .map
file.
-
You must convert a legacy message flow node before you can modify any of its
transformation logic.
-
You must change the transformation logic in your integration solution when a
legacy message map is invoked from an ESQL
CALL statement. For more information, see Converting a legacy message map that is called from an ESQL statement in a Compute node.
A message map cannot be called from a ESQL CALL
statement.