Saving a message flow or subflow

The message flow or subflow is saved and the message flow validator validates the contents of the flow. The validator reports all errors that it finds in the Problems view. The flow remains open in the editor view. For example, if you save a message flow and have not set a mandatory property, an error message appears in the Problems view and the editor marks the node with the error icon . The message flow in the Application Development view is also marked with the error icon. This error can occur if you have not edited the properties of an MQInput node to define the queue from which the input node retrieves its input messages.

You might also get warnings when you save a message flow or subflow; warnings are also shown in the Problems view. Warnings indicate that, although the configuration of the message flow or subflow does not contain an explicit error, the configuration might result in unexpected results when the flow completes. For example, if you have included an input node in your message flow that you have not connected to another node, you get a warning.

To resolve this situation, right-click the subflow node in error and click Locate Subflow. The Locate Subflow dialog box is displayed, listing the available integration projects. Expand the list and explore the resources available to locate the required subflow. Select the correct subflow and click OK. All references in the current message flow or subflow are updated and the errors are removed from the Problems view.