pub.flow:savePipelineToFile

fileName

String Relative or absolute path to a file on the server file system in which Integration Server saves the contents of the pipeline.

When you specify a path for the fileName input parameter, Integration Server verifies whether it is specified in the allowedWritePaths parameter of the file access control configuration file (fileAccessControl.cnf). If the file path is not specified in the allowedWritePaths parameter, Integration Server issues an exception. Otherwise, Integration Server either creates the file if it does not yet exist or overwrites the existing file if one already exists.

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.

This service is helpful in the interactive development or debugging of an application. In some cases, however, using the Pipeline debug property for the debugging of an application is more efficient. For more information about the Pipeline debug property, see webMethods Service Development Help.

The following table shows the data types and classes that this service can write to the output file if they are included in the pipeline:

For...	pub.flow:savePipelineToFile supports...
Java data types	byte[] Date GregorianCalendar IData IData[] (IData list) String String[] (String list) String[][] (String table) Vector
Java wrapper classes	Boolean Byte Character Double Float Integer Long Short Single dimension arrays of any of the above
webMethods classes	MBoolean MByte MDouble MFloat MInteger MLong MShort Single dimension arrays of any of the above
Object arrays	Any non-array item listed in this table.