After the map resources are imported, you can then convert the map to a graphical data
map.
About this task
The steps for converting the message
map for this scenario are taken from the steps that are described in Converting a message map from a .msgmap file to a .map
file. The steps have been tailored to the scenario, and so do not
include all possible options and methods available. Review the Information
Center topic for generic conversion steps.
If you import
your messaging solutions from WebSphere® Message Broker Version
6.1 or WebSphere Message Broker Version 7.0,
you can still compile and deploy message flows that use message map
(.msgmap) files, provided that the message flow
is built in a BAR file that has the option compile and
in-line resources set. However, in WebSphere Message
Broker Version 8.0 and
later, message map files are accessible in read-only mode and cannot
be modified by using the Toolkit.
In WebSphere Message Broker Version
8.0 and later, if you want to modify mapping operations that
are defined in a message map, you must first convert your message
map to a graphical data map (.map) file.
When
you convert a message map, message flows that reference the unconverted
message map cannot be deployed until you modify each message flow
to reference the new graphical data map instead.
To convert
the scenario message map to a deployable graphical data map by using
the Toolkit, complete the following steps:
Procedure
- In the Application Development view,
right-click MembersMFPFlow_Mapping.msgmap (or
a .msgmap that you want to convert), and click Convert
Message Map from .msgmap to .map.
Your
new graphical data map is created, and is displayed in the Application
Development view. Your message map is renamed MembersMFPFlow_Mapping.msgmap_backup,
and is displayed after your new graphical data map in the Application
Development view.
In the Application Development view,
you can see that the scenario message flow has a problem that is indicated
by a red box with a cross:
You must now modify
the message flow that referenced the previous message map so that
the message flow instead references your new graphical data map. In
this scenario, MembersMFPFlow.msgflow uses MembersMFPFlow_Mapping.map.
- In the Application Development view,
double-click MembersMFPFlow.msgflow. The message flow opens in the Message Flow editor.
- In the Message Flow editor, identify the Mapping node
from a previous version of WebSphere Message Broker. If you click an old Mapping node,
you get a warning message box, that informs you that the node cannot
find your previous message map.
You can also identify
a previous version of a Mapping node
by clicking it. In the Properties view, the node
title includes the type as Mapping (deprecated).
The Mapping node
must be replaced so that it can accept the new graphical data map.
Check the Basic tab in the Properties view
of the deprecated Mapping node.
The Mapping routine field contains the value MembersMFPFlow_Mapping.
This value is the name of the routine for the map, that is required
for the new Mapping node.
- In the Palette, expand the Transformation section,
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.
Note: If you do not change the default name now, you
can change it later by using the name field in the Description tab.
- Select your new Mapping node. The node properties are displayed in the Properties view.
- In the Properties view, the Mapping
routine property contains a default value, which must be
replaced. 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. There is no schema for the scenario,
and so {default} is shown.
For
the scenario, replace the MapName value with MembersMFPFlow_Mapping.
- Move the existing connections from your previous Mapping node
to your new Mapping node.
Drag the connectors by using the mouse. You can also use
the Terminal Selection dialog box to move the connections, but this
is not covered in this scenario; for more information, see Creating node connections with the Terminal Selection
dialog box.
- Select your previous Mapping node,
and press the delete key (del) to remove it from your message flow.
- You have replaced the Mapping node
and updated the message flow to reference the new graphical data map.
Save your changes.
Results
The message map is converted to a graphical data map that
can be modified by using the Graphical Data Mapping editor, and
MembersMFPFlow.msgflow accepts
the new map, as shown in the following image:
What to do next
After you convert a message map,
open and check the map for any warnings or errors on transforms. In
this scenario, you must configure the transforms to resolve errors
and warnings. Next, follow the tasks for Configuring the converted transforms