That link seems to imply that the consumer is posting an XML document to the service, which as Dinesh has already discovered, is not always the case.
One of the better ways for you to get familiar with how it works is to run some data through it. My favorite option is to use something like soapUI in conjunction with services like savePipeline/restorePipeline.
You can create a REST project in soapUI and provide it your endpoint URL, which in this case, it will be something like: http://localhost:5555/rest/DigitalRestServices.Program
Please note a couple of important things:
- The use of the REST directive instead of INVOKE
- The exclusion of the service name from the URL
From soapUI, play around with changing the HTTP method from GET to POST to whatever and notice different services being called. Also, play around with passing data to the service and changing the content-type around, such as text/xml, application/json, etc, etc.
Percio
#webMethods#Integration-Server-and-ESB