Restoring the Flow Service Pipeline while Debugging

Cloud Application Integration (On-Premises) : Service Development : Debugging Flow Services : Saving and Restoring the Flow Service Pipeline while Debugging : Restoring the Flow Service Pipeline while Debugging

Loading a Saved Pipeline while Debugging

Restoring a pipeline is useful when you simply want to inspect the values in a particular pipeline file (perhaps one that contains the pipeline from a failed service). Additionally, it is useful in many debugging situations. For example, you can use it to replace the existing pipeline with a different set of values when stepping though a flow service with the debugging tools.

There are three ways to restore the contents of the pipeline:

Manually load the saved pipeline into the Variables view while debugging in Designer.

Automatically load the saved pipeline at run time by using the Pipeline debug property.

Programmatically load a saved pipeline at run time by invoking pub.flow:restorePipelineFromFile at the point where you want to modify the pipeline. For more information about using this service, see the webMethods Integration Server Built-In Services Reference.

Note:

When using MTOM streaming for SOAP attachments, messageContext variables and/or XOPObject fields will not be available in the saved pipeline. A messageContext variable is used by many pub.soap services to hold the SOAP message on which the service acts. XOPObject fields are Objects that use the com.wm.util.XOPObject Java wrapper type. For more information about MTOM Streaming, see the Web Services Developer’s Guide.

Contact Support | Community | Feedback