Considerations When Coding the Target Service to Receive the XML Document
BecauseIntegration 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 you want the target service to return output to the client:
Configure the email port to return results from requests that it receives.
By default, the email port does not return results. For information about configuring the email port to return results, see webMethods Integration Server Administrator’s Guide.
If your email port is configured to return results, Integration Server emails the output from target service back to the sender of the original message, in an attachment file called xml.out.
Define how you want the target service to return its output.
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.)
Related Topics
