Hi,
Transport Protocol : This parameter defines the transport protocol for processing the message.
Message Protocol : This parameter defines the message protocol for processing the message.
This is the main difference between these two
SOAP-:messaging protocol
HTTP: Transportprotocol
For more details on message protocol see below.
Message Protocol
The SAP Exchange Infrastructure message format is based on XML. Since a message in SAP XI can also have binary attachments, this documentation refers predominantly to messages in general and not specifically to XML messages.
XML Properties
XML (eXtensible Markup Language) enables you to describe data in a highly intelligible form. An XML schema definition specifies which elements can be used, which attributes these elements have, and how they are structured. More than one instance (a document that matches an XML schema definition) can exist for each schema. The following example of an instance illustrates that the elements in a schema are ordered hierarchically:
) are also known as tags in HTML.
You can describe the structure of a schema by using an XML schema. As well as the description of the structure of an XML document (elements, attributes, hierarchy), this language allows you to define simple and complex data types. Note the following difference:
· XML schema language provides a series of language constructs that you can use to describe an XML schema.
· XML schema definition describes exactly one XML schema and is defined using the XML schema language.
· More than one schema instance can exist for an XML schema. A schema instance is an XML document; its structure and values are defined using a corresponding XML schema definition. The process whereby the system checks whether an XML document matches a schema definition is called validation.
refer http://help.sap.com/saphelp_nw04/helpdata/en/b6/0b733cb7d61952e10000000a11405a/content.htm for more details.
You can say like while configuring adapters in Integration Directory, you can use like this
Configure Sender SOAP Adapter.
Scenario: WebServiceDemo,Service without Party
Business Service: WebServiceClient
Communication Channel:
SOAP_Client
Transport Protocol: HTTP / TCP-IP etc
Message Protocol: SOAP 1.1
Adapter Engine: Integration Server
Keep Headers: false
Keep Attachments: false
Use Encoded Headers: false
Use Query String: false
Edited by: Ashok Reddy Thatigutla on Feb 16, 2008 4:47 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.