Generate .msgflow from running message flow pattern

This simple pattern causes a deployed message flow to be extracted from a running broker and converted into a corresponding source message flow file.

Diagram showing the conversion from a
        deployed message flow into a .MSGFLOW file

Solution

This pattern uses the Message Broker's CMP API interface to connect to a local or remote broker and discover a specific message flow and its properties. It uses this information to construct a new message flow that contains the same nodes, properties and connections of the source message flow.

When to use this pattern

There are several scenarios in which you might want to use this pattern. You might want to use this pattern to understand the high-level behaviour of message flows in situations where the source is not available, or if you want to ensure that the broker is running the message flow that was intended. Alternatively, you might want to use this pattern to kick-start the recreation of existing message flows where the source has been lost.

Restrictions

The pattern uses only public, published external interfaces to reconstitute message flows. However, this means that there are a number of restrictions on what this pattern can produce, based on limitations in the information that is available from the V7 or V8 broker through these interfaces. The most significant limitations include:

Support

This pattern is supplied "as-is" and has no formal support statement; use it at your own risk! Complete source for this pattern is included on the official download site for this pattern at MQSeries.net, so feel free to take a look there to find out how the pattern works (and improve it!). You can contact me with any questions or comments using the private message facility on the same site; my user name is mqmatt.