You can convert a subflow created as a .msgflow file
to a .subflow file by using the Convert
to subflow function in WebSphere® Message
Broker. If the subflow includes other legacy resources, you must convert
them before you can convert your subflow.
Procedure
You must complete the following steps to convert the MembersMFPFlow.msgflow subflow
sample into a subflow created as a .subflow file:
- In the Broker Development view,
identify the Message Broker project located under the Independent
resources folder that contains the subflow that you want
to convert. Select the subflow, in our example, MembersMFPFlow.msgflow.
- Right-click the subflow and select Convert to
subflow.
- An error window opens that tells you that you cannot convert
the subflow. The subflow contains a legacy Mapping node that you must
convert before you can select Convert to subflow.
- In the Broker Development view,
identify the Message Broker project located under the Independent
resources folder that contains the subflow that you want
to convert. Identify the map that needs to be converted. In our example,
it is the MembersMFPFlow_Mapping.msgmap. Select Convert
Mesage Map from .msgmap to .map.
- The Message map conversion progress window
opens and details the results from converting your map. Click Close.
- After you click Close, the Convert
Mesage Map from .msgmap to .map function completes. You
can see your converted map in the Broker Development view,
in the Maps folder under your Message Broker
project. The converted map has a .map file extension.
- After you convert the map, you need to fix the following
errors:
- Errors related with transformation functions that require
manual conversion steps to finalize its conversion. For more information,
see Scenario: Converting a message map to a graphical data map.
- The error related to the Mapping node that had the legacy
map configured. The node is a legacy node, and needs to be replaced
by the WebSphere Message
Broker Version 8 Mapping node.
- To replaced the legacy Mapping node with the WebSphere Message Broker Version 8 Mapping
node, complete the following steps:
- Identify the new Mapping node in the Palette.
- Drag and drop the Mapping node onto the message flow canvas.
- Select the map that you want to associate to the Mapping node.
This is the map you just finished converting.
- Delete the old Mapping node.
- Connect the new Mapping node where you just removed the old
Mapping node.
- After you have converted your legacy map and replaced the
old Mapping node with the new one, select the MembersMFPFlow.msgflow subflow.
Right-click the subflow and select Convert to subflow.
- In the Convert message flow to subflow window,
select Update all files, and click Ok.
The conversion starts.
- Optional: If the Conversion Failure window
opens, click Ok.
Then, select .
What to do next
You must verify that the converted subflow is created
and available:
After the conversion completes, verify that the initial subflow
disappears from the Flows folder, and the converted
subflow appears under the Subflows folder.
Verify that the message flow includes the subflow as a node.