After completing this unit, you’ll be able to:
- Describe SOAP Message Structure
- Easily create soap template message type
It is important for web applications to be able to communicate over the Internet. The best way to communicate between applications is over HTTP, because HTTP is supported by all Internet browsers and servers. SOAP was created to accomplish this. A SOAP message is an XML format containing the some specific elements I,e Envelope, Header and Body.
What is the soap template message type?
To secure our data transmission system need specific formatted data. In Skyvva we have specific soap template message type contains URL, header body. We have different template for request and response. . As we have three element in Request: ,
1. URL Param
2. Header and
As we have two element in Response
1. Header and
So , when we get response and we will get both header and body so based on mapping we will perform DML operation for the data we got in response.
soap template message type
A SOAP request message is an XML format containing the some specific elements as:
SOAP URL Parameter :
The Simple Object Access Protocol (SOAP) endpoint is a URL. It identifies the location on the built-in HTTP service where the web services listener listens for incoming request. There are two URL parameter:
- Path parameter:
- Query parameter:
But we support only Query parameter:
Here we can see the Question mark in above URL, So before ? mark we have path parameter and after question mark we have query parameter and parameter name exactly same as we inserted in messageType.
SOAP Header :
The optional SOAP Header element contains application-specific information (like authentication, payment, account id etc) about the SOAP message.If the Header element is present, it must be the first child element of the Envelope element. It Contains any optional attributes of the message used in processing the message, either at an intermediary point or at the ultimate end-point. It can be hierarchical.
SOAP Body :
The SOAP body is a mandatory element that contains the application-defined XML data being exchanged in the SOAP message. The body must be contained within the envelope and must follow any headers that might be defined for the message. The body is defined as a child element of the envelope, and the semantics for the body are defined in the associated SOAP schema.The body contains mandatory information intended for the ultimate receiver of the message. It can be hierarchical. We support hierarchical body and generate chained interface. For example − fields of account object:
Message type for soap adapter?
Step 1: We have to create metadata provider
Step 2: Create Istructure repository
Step3: Create message type.
Type of each element should be same as shown in screenshot.