A legacy Mapping node
(created in WebSphere® Message Broker Version 7), cannot
reference a graphical data map (.map file). If
you want to reference a graphical data map in IBM® App Connect Enterprise, you must replace the legacy Mapping node with a new Mapping node, which is
supported in IBM App Connect Enterprise.
Before you begin
Before you replace a
Mapping node, you must
complete the following task:
You might also need to complete the following task:
About this task
If you import your integration solutions from WebSphere Message Broker Version 7, you must convert your
legacy message maps and Mapping nodes
before you can deploy the message
flows that
use them.
If you want to reference a graphical data map (.map file)
in a Mapping node,
you must use a Mapping node
that was created in WebSphere Message
Broker Version 8 (or
later) or in IBM App Connect Enterprise.
To
replace a legacy Mapping node
by using the IBM App Connect
Enterprise Toolkit, complete
the following steps:
Procedure
- In the Application
Development view,
double-click a message flow that
contains one or more legacy Mapping nodes.
The message flow opens
in the Message Flow editor.
- In the Message Flow editor, identify a legacy Mapping node that you want
to replace.
- In the Palette, expand the Transformation section,
and then drag a new Mapping node
from the Palette to the canvas of the Message Flow Editor.
A new Mapping node is added to
your message flow, and is assigned
a default name.
If you rename the node, the name that you choose
must be unique in the message flow.
If you do not change the default name at this time, you can change it later, as described in
Renaming a message flow
node.
- Select your new Mapping node.
The node properties are displayed in the Properties
view.
- In the Properties view, a default value is entered in the Mapping
routine property, and must be replaced by choosing one of
the following actions:
- To reference an existing graphical data map, click Browse... to
locate it, or specify your .map file in the format
{BrokerSchemaName}:MapName. {default} indicates
that no Broker schema is used by the graphical data map. For more information,
see Referencing an existing message map from a Mapping node.
- To create a new graphical data map, double-click the Mapping node, or right-click
the Mapping node and
click Open Map. For more information, see Creating a message map from a Mapping node.
-
Move the existing connections from your legacy Mapping node to your new Mapping node. For more information,
see Connecting message flow
nodes.
-
Select your legacy Mapping node and press the delete
key (del) to remove it from your message flow.
For more information, see Removing
a message flow node.
- Repeat steps 3 through 7 for each legacy Mapping node that you want
to replace in your message flow.
Results
You have removed your legacy Mapping nodes and replaced
them with new Mapping nodes.
What to do next
Deploy and test your message flow. For more information, see Deployment rules and
guidelines.