Considerations When Coding the Target Service to Receive the XML Document
Because Integration Server passes the parsed XML document in the node variable, the target service that receives the XML document must take a node variable as input.
The target service can then manipulate the data in the XML node. The target service can pass the node to another service that takes node as input, for example:
pub.xml:queryXMLNode to query the node
pub.xml:xmlNodeToDocument to convert the node to an IData object
For more information about the pub.xml:queryXMLNode and pub.xml:xmlNodeToDocument services, see webMethods Integration Server Built-In Services Reference.
If the target service returns output, the format of the returned output depends on whether you assign an output template to the target service:
If the service does not have an output template assigned to it, the results from the service (that is, the contents of the pipeline) are XML-encoded and returned as an XML document.
If the service has an XML output template assigned to it, that template is applied to the results. (If the template is not an XML-based template, it is not applied.)
Integration Server writes the output to the same virtual directory where the XML document was initially sent via FTP. The results are in a file named filename.out, where filename is the name of the XML file originally sent to the target service via FTP.
Related Topics