Configuring the SOAP Adapter 
Use
You need to configure the SOAP adapter so that you can exchange SOAP messages between the Integration Engine and remote clients or servers of Web Services.
The SOAP adapter provides a runtime environment that includes various SOAP components for the processing of SOAP messages. You can combine these SOAP components with separate components to satisfy your needs and requirements.
The SOAP adapter uses a helper class to instantiate and control SOAP components. If you want to use your own SOAP processing logic you must make your helper class known to the SOAP adapter.
To configure the SOAP adapter you must specify the following:
· The helper class that implements the following interface:
com.sap.aii.messaging.adapter.ModuleBubbleHelper
· The parameter values for the specified helper class
For example, you must specify the following parameters for the helper class ModuleBubbleHelperXMBWSImpl (instantiates a BubbleBag to integrate remote Web Services with the Integration Engine):
¡ Information about the Integration Engine destination (when the Integration Engine is acting as a service provider and therefore the SOAP adapter must be configured as an inbound adapter).
¡ Information about the Web Service provider destination (when the Integration Engine is acting as a service client and therefore the SOAP adapter must be configured as an outbound adapter).
¡ Various options for controlling the conversion of multi-part Integration Engine SOAP messages and Web Service SOAP messages.
Prerequisites
You have:
...
1. Installed the corresponding adapter.
2. Selected the adapter on the configuration screen.
3. Called the adapter configuration by choosing Configure.
Procedure
The configuration of the SOAP adapter comprises two functional subareas:
...
1. The Java class name for the SOAP adapter
Specify the class name as follows:
classname=com.sap.aii.messaging.adapter.ModuleBubble
This specification is mandatory.
2. The configuration parameters for the specified helper class
Therefore, you must specify the following parameters for the shipped helper class ModuleBubbleHelperXMBWSImpl, for example:
¡ Specifications for the Integration Engine as a service provider for queries from Web Service clients (inbound SOAP adapter).
¡ Specifications for the Web Service provider for queries from the Integration Engine as a Web Service client (SOAP outbound adapter).
You can configure an inbound adapter, or an outbound adapter, or both, if required.
Configuring the Helper Class for Inbound Processing
...
1. Enter the complete address (URL) of the Integration Engine that you want to send the message to:
XMB.TargetURL=http://IntegrationEngineHost:port/pipeline-arguments
This specification is mandatory when the Integration Engine is acting as a service provider.
The Integration Engine address can also be accessed dynamically from the SAP System Landscape Directory. The following entry is added to the configuration for this purpose:
XMB.SLDConfiguration=SLDaccessor
In this case, for the system specified with XMB.SenderBusinessSystem, the URL of the corresponding Server in the SLD is exported and the value specified under XMB.TargetURL is used instead. You also need to specify the following:
XMB.TargetURL=<fromSLD>
To be able to access the System Landscape Directory, the SLDaccessor service must be configured correspondingly and the respective entries must be maintained in the System Landscape Directory.
If an authentication was specified in the Integration Engine for the URL (HTTP service) entered, use the following address:
XMB.TargetURL=http://<user-name>:<password>@IntegrationEngineHost: port/pipeline-arguments
As an alternative, or if the URL is taken from the System Landscape Directory, you can also specify the logon parameters as follows:
¡ XMB.User=<user-name>
¡ XMB.Password=<password>
The specifications must match those that you made in transaction SICF in the Integration Engine. If you do not specify a user and password combination, or the combination is invalid, the system will terminate each attempt to access the Integration Engine with the message Transport Exception: http-Error 401 – Unauthorized.
The user must have the authorizations of group SAP_XI_APPL_SERV_USER on the Integration Server.
If you use a different client or language to the default setting in the Integration Engine when logging on, you can also set the following parameters:
¡ XMB.Client=<client-no>
¡ XMB.Language=<language-id>
The following address arguments are optional. If this information is not contained in the request message of a Web Service client, the specifications made here are used to identify the adapter configuration in routing and mapping in the Integration Engine pipeline. You can also find an explanation about each argument there.
¡ XMB.SenderBusinessSystem=<configuration name>
¡ XMB.SenderInterfaceNamespace=<namespace URI>
¡ XMB.SenderInterfaceName=<name>
¡ XMB.ReceiverBusinessSystem=<configuration name>
Use routing in the Integration Engine to change the receiver system.
The following arguments are also mandatory:
¡ XMB.QualityOfService=<QualityOfService>
Specifies how the Integration Engine should process a message. The following values are permitted:
XMB.QualityOfService=BE(Best Effort, means synchronous processing)
XMB.QualityOfService=EO(Exactly Once, means asynchronous processing)
XMB.QualityOfService=EOIO(Exactly Once in Order, means asynchronous processing using queues)
This specification is mandatory.
You must also define a queue name for EOIO:
¡ XMB.QueueId= <QueueName>
This queue name is used in the Integration Engine to process messages in the same sequence that they arrived in.
2. Specify the port number and the path for the adapter port for Web Service clients:
¡ XMBWS.WSPort=<port_no>
The port number (<port_no>) specifies the HTTP server port of the adapter that contains Web Service messages.
¡ XMBWS.WSPath=<path>
The path (<path>) describes the service part of the adapter URL that contains Web Service messages.
Configuring the Helper Class for Outbound Processing
...
1. Enter the complete address (URL) of the Web Service provider that you want to send the message to:
XMBWS.TargetURL=http://WebServiceHost:port/service-arguments
This specification is mandatory when the Web Service provider is acting as a service provider.
If an authentication was specified for the URL (HTTP service) entered in the Web Service provider, use the following address:
XMBWS.TargetURL=http://<user-name>:<password>@WebServiceHost:port/ service–arguments
Alternatively, you can also specify the logon parameters as follows:
¡ XMB.User=<user-name>
¡ XMB.Password=<password>
2. Specify the value for SOAPAction:
¡ XMBWS.DefaultSOAPAction=<default_soap_action>
<default_soap_action> specifies the default value for the SOAPAction in Web Service messages.
¡ XMBWS.UseSOAPAction=<use_soap_action_opt>
<use_soap_action_opt> specifies the method with which the SOAPAction value is identified, based on the message instance.
The only valid value is receiver.
3. Specify how the format of Web Service messages is to be controlled
¡ XMBWS.KeepHeaders=<boolean>
If you specify true here, all Integration Engine message headers are copied to Web Service messages. Otherwise, all headers are deleted.
Web Service message headers are always copied to Integration Engine messages.
¡ XMBWS.UseEncoded=<boolean>
If you specify true here, all Integration Engine message headers are encoded in the HTTP header X-XMB_WS_ENCODED.
4. Specify the port number and the path for the adapter port for the Integration Engine:
¡ XMBWS.XMBPort=<port_no>
The port number (<port_no>) specifies the HTTP server port of the adapter that contains messages from the Integration Engine.
¡ XMBWS.XMBPath=<path>
The path (<path>) describes the service part of the adapter URL that contains messages from the Integration Engine.
