Sie sind auf Seite 1von 4

Configuring the Sender SOAP Adapter

PDF download from SAP Help Portal:


http://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/3555240bea31c3e10000000a42189d/frameset.htm
Created on August 19, 2016

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.

Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 4

Table of content
1 Configuring the Sender SOAP Adapter

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 4

1 Configuring the Sender SOAP Adapter


Use
Configure the sender SOAP adapter to send content from remote clients or Web service servers to the Integration Server/Advanced Adapter Engine Extended
(AEX).

Prerequisites
If you want to handle acknowledgments, you must create a HTTP destination in the SAP NetWeaver Administrator (NWA)
For more information, see Maintaining HTTP Destinations

Procedure
1. Select the Transport Protocol as HTTP .
2. If you want to send information from a remote client or a Web service server to the Integration Server/AEX, then select the Message Protocol as SOAP
1.1 . If you want to send an XI message from a legacy system or AAE through the SOAP Adapter, then select the Message Protocol as XI 3.0 .
3. Select the Adapter Engine on the Integration Server, or select a non-centrally installed Adapter Engine.
1. Define Inbound Security Checks
From the HTTP Security level drop-down, select the security level for the inbound message.
For more information, see the SAP NetWeaver Process Integration Security Guide.

Note
You can only define inbound security checks for the SOAP 1.1 message protocol.
2. Define Security Parameters
1. If you want to make additional settings for security in the relevant sender agreement on the Integration Server or in the AEX, select Select Security
Profile .
For more information, see SAP NetWeaver Library under
Function-Oriented View
Process Integration
Integration Directory
Defining Sender
Agreements
Security Settings for the Sender SOAP Adapter .

Note
If you select Security Profile , there must be exactly one sender agreement for the defined communication channel.
2. Under Security Profile select:
Web Services Security
S/MIME

Note
For XI 3.0 message protocol, you can use only web services security as the security profile.
3. Specify the Persist Duration for messages in days, hours, minutes, and seconds.
3. Define Conversion Parameters
1. If the adapter is to expect a message without a SOAP envelope, select Use No SOAP Envelope .
In addition specify nosoap=true in the URL.
2.
3.
4.
5.

The adapter puts the whole message in the XI payload.


To include the header of the Web service message in the XI message, select Keep Headers .
To include attachments of the Web service message in the XI message, select Keep Attachments .
If the XI header information is to be included in the encoded string, select Use Encoded Headers .
If the XI header information is to be included in a query string, select Use Query String .

Note
Conversion Parameters are available only if you select the Message Protocol as SOAP 1.1 .
4. Define Processing Parameters
Under Quality of Service , specify how the message is to be processed by the Integration Engine/AEX.
For Exactly Once In Order Quality of Service enter the Queue Name .
For more information, see Quality of Service and
Ensuring Exactly Once in the Sender Adapter
5. Define Adapter-Specific Message Properties
1. Select the Advanced tab page.
2. To save adapter-specific attributes in the message header of the XI message, select Set Adapter-Specific Message Properties .
The following attributes are added to the XI message header if the sender makes them available, and if you select Variable Transport Binding .
Remote User : (technical name: SRemoteUser )
Remote Host : (technical name: SRemoteHost )
SOAP Action (technical name: SHeaderSOAPACTION )
To transfer further header fields, set the relevant indicator. You can then store the following attributes and their values in the XI message header:

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 4

Variable Header : (technical name: XHeaderName1 )


Variable Header : (technical name: XHeaderName2 )
Variable Header : (technical name: XHeaderName3 )
The names of the fields and parameters must correspond to the names of the fields and parameters that also go through the HTTP request.
The attribute namespace for the adapter is http://sap.com/xi/XI/System/SOAP .
6. Define the Adapter Status
Set the adapter to Active to enable messages to be exchanged.

Note
Adapter Status is available only if you select the Message Protocol as SOAP 1.1 .
7. Define Acknowledgement Destinations

Note
You can define acknowledgement destinations for external entities that communicate with AAE using SOAP XI adapter. Some of the examples of such
entities are ABAP proxy applications or Integration Servers.
1. From the Message Protocol dropdown listbox, choose XI 3.0 .
2. Choose the Acknowledgement Handling tab.
3. In the HTTP destination (from NWA) field, specify the HTTP destination that you have created in the SAP NetWeaver Administrator.
Note of Message Protocol XI 3.0
The sender channel splits all multi-message into individual message and then processed.
A system acknowledgement for the multi-message is received after all the individual messages in the multi-message are processed.

Result
You have configured the SOAP sender adapter. You can trigger a call to the sender SOAP adapter using either of the following URLs. However, SAP
recommends you to use the second option.
http:// <host name> : <port name> /XISOAPAdapter/MessageServlet?channel= <party name> : <service name> :
<channel name> . If you have not created a party, enter channel=: <service name> : <channel name>
http:// <host name> : <port name> /XISOAPAdapter/MessageServlet?senderParty= <name of the sender party>
&senderService= <name of the sender service> &interface= <name of the interface> &receiverParty= <name of
the receiver party> &receiverService= <name of the receiver service> &interfaceNamespace= <name of the
interface namespace>

Note
You must specify the parameters in the URL even if some of them do not have values.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 4 of 4

Das könnte Ihnen auch gefallen