Web services messages overview

This topic describes how to work with the abstract data graph form of Web services messages.

The format of Web services messages

WebSphere® Application Server supports two formats for Web services messages: SOAP and enterprise beans. (These are similar to Java™ APIs for XML based RPC, or JAX-RPC).

To work with Web services messages, you need the following information:

Format types

The Web services message type is defined by a message format string within the message. The format string is prefixed with a domain identifier, which is either SOAP or Bean, followed by four comma-separated fields as shown below:
SOAP:<wsdlLocation>,<serviceNameSpace>,<serviceName>,<portName>
Bean:<wsdlLocation>,<serviceNameSpace>,<serviceName>,<portName>
The fields are described in the following table:
Field name Message format string Field description
WSDL location <wsdlLocation> The URI where the WSDL for this message is located. The WSDL is deployed to the SDO Repository using this location as the key.
Service namespace <serviceNamespace> Service namespace and Service name uniquely identify the Service definition within the WSDL.
Service name <serviceName> Service name and Service namespace uniquely identify the correct Service definition within the WSDL.
Port name <portName> Locates the Port definition within the Service, giving the PortType and Binding information that is required for message processing.



Subtopics
Mapping of SDO data graphs for Web services messages
Mapping XML schema definitions to the SDO type system
Web Services code example
Related reference
Transcoding between message formats
Reference topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 8:25:23 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=rjy1110
File name: rjy1110.html