First, the services that you need to use are described in the Built-In Services Guide found in your wm_home\Developer\doc folder.
Assuming your XML is already in a string, you would use pub.xml:xmlStringToNode to convert it to a IS node. Nodes are objects representing parsed XML documents.
Map your string to the xmlstring parameter and be sure to set the isXML parameter to “true”.
If your service was invoked by posting an XML document to Integration Server, there will already be a node object in the pipeline created by the XML content handler.
The XML content handler processes the xml document before your service is invoked, checks for well-formedness and parses the XML into a node and inserts it into the pipeline.
To work with a node in IS, you need to use the pub.xml:xmlNodeToDocument service or the pub.xml:queryXMLNode service. The former is simpler, but lacks the ability to query a large XML document for the one section that you might need to process.
To use pub.xml:xmlNodeToDocument in its simplest form, just map your node to that service’s node input parameter.
You will now have a document (called “document”) in the pipeline and can use a map step to map it to another document type with the desired field names.
Use pub.xml:documentToXMLString to convert this target document to an xml string.
These steps represent transformation of a simple XML document like the example you gave. Documents with namespaces, repeating elements (arrays) or requiring you to operate on only a portion of the incoming document will make use of the other parameters for these xml handling services.
Spend some time with the services in the pub.xml folder and the sample code in the WmSamples package. If you plan on doing much integration with webMethods tools, you’ll need to become very, very proficient with the IS XML handling services.
Think of it as like learning algebra before you can move on to calculus.