Saving the Flow Service Pipeline while Debugging

Saving the Pipeline to a File while Debugging

You can save the pipeline to a file, which you can use to restore the pipeline to its current state at a later point in time. This is useful when you want to debug another service against the current set of pipeline values or if you want to restore the pipeline to this exact state later in the debugging process. There are three ways to save the contents of the pipeline:

Manually save the contents when you debug a service using Designer.

Automatically save the pipeline at run time using the Pipeline debug property. For more information about this property, see Automatically Saving or Restoring the Pipeline at Run Time.

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

When you save a pipeline, it is saved in a file in XML format. The file you create can be used to:

Manually load the pipeline into Variables view while debugging a service.

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

Load a default set of input values when creating a launch configuration.

Load a set of input values into the Input dialog box when debugging a service with Designer.

Dynamically load the pipeline at run time using the pub.flow:restorePipelineFromFile service.

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.