skip to main content
Corticon Server: Deploying Web Services with Java : Consuming a Decision Service on Java server : Path 3: Using SOAP client to consume a Decision Service : Creating a SOAP request message for a Decision Service
 

Try Corticon Now
Creating a SOAP request message for a Decision Service
Once your SOAP development tool has imported the WSDL or XSD service contract, it should be able to generate an instance of a request message that complies with the service contract. It should also provide you with a way of entering sample data to be included in the request message when it is sent to the Decision Service.
Most commercial SOAP development tools accurately read service contracts generated by the Deployment Console, ensuring well-formed request messages are composed. 
One occasional problem, however, involves the Decision Service Name, which was entered in field 3 of the Deployment Console's Deployment Descriptor section. Even though all service contracts list decisionServiceName as a mandatory element, many SOAP tools do not automatically insert the Decision Service Name attribute into the request message's decisionServiceName element. Be sure to check this before sending the request message. If the request message is sent without a decisionServiceName, the Server will not know which Decision Service is being requested, and will return an error message.
Corticon Server also offers a mode of WSDL generation that's more compatible with Microsoft's Windows Communications Framework. See the Server Integration & Deployment Guide for more details.
Enter all required data into the request message. The tutorial_example.erf example produces its best results when you enter positive integer values such as:
*cargo.weight 200000
*cargo.volume 1000