Adapter for SAP 10.1 | webMethods Adapter for SAP Documentation | webMethods Adapter for SAP Installation and User’s Guide Documentation | Routing Messages Through Adapter for SAP | Routing Notifications | Configuring a Routing Notification | XML Transport
 
XML Transport
Use this transport to post an SAP IDoc- or RFC-XML to a URL.
Set the transport parameters as follows:
Key
Value
url
URL to which you want to post the XML message.
xmlType
Select between the XML dialects SAP-XML, bXML, Values-XML, Arbitrary XML or SOAP XRFC (XRFC with SOAP envelope).
If you select SAP-XML the content type is set to application/x-sap.idoc(respectively.rfc). Therefore the receiving server has to understand this content type. (This can be overridden using the following flag.)
If Arbitrary XML is selected, the transport expects the XML document as string in the variable xmlData.
useTextXml
Flag that allows you to overwrite the content type of bXML, SAP-XML to text/xml, if set to true. The checkbox is disabled for other dialects.
useUTF8
Flag that allows you to force the renderers of bXML, SAP-XML to use the encoding utf-8, if set to true. The checkbox is disabled for other dialects.
useBAPI
Set this flag if you want to use the BAPI XML format. (This field is only active when using the bXML dialect.)
objectName
The name of the business object to which the call should be mapped. This value is case-sensitive. (Available only when using the bXML dialect and the BAPI format.)
bapiName
The name of the BAPI method, to which the call should be mapped. This value is case-sensitive. (Available only when using the bXML dialect and the BAPI format.)
httpUser
An optional parameter that allows you to specify a username for authentication on the remote Web system.
httoPassword
An optional parameter that allows you to specify a password for authentication on the remote Web system.
Tip:
When sending an IDoc between two adapters for SAP via XML transport, use http://<hostname>:<port>/invoke/pub.sap.transport.ALE/InboundProcess as URL.
When sending an RFC to a second Adapter for SAP over HTTP, use http://<hostname>:<port>/invoke/pub.sap.transport.RFC/InboundProcess as URL.
When the routing listener receives a message for which it cannot locate a routing notification, it logs the message in its transaction store and throws an Exception.