Query on Sender SOAP

Question

Hello,
Do we need to Configure Sender in case of Sender SOAP adapters...Normally in which cases we can skip configuring the sender SOAP adapter.
Because In on of our interfaces ,in production..I have  seen an interface with no sender SOAP Communication channel used in Sender Agreement ....Even then defined Sender SOAP communication channel in some business service...
What could be the reason...

Answer 1

1. When we use *Sender SOAP Adapter how the connectivity is happening with Remote Clients.
A:SOAP is an XML-based protocol for exchanging information in a decentralized, distributed environment.SOAP is a technology that allows XML to move easily over the Web. SOAP does this trough an XML envelope for delivering XML content and specifying a set of rules for services to follow when they receive a SOAP message.The fundamental change brought about by SOAP has been the ability to move data anywhere across the Web.
When ever XI needs to talk to a webservice you will go for SOAP adapter. If you need to enable some functionality as webservice using XI you can use SOAP Sender adapter. If you need to send request to a webservice you will go for SOAP Receiver
SOAP Message Structure :
SOAP Envelop: The outermost element of SOAP message. The envelope element is the root of the XML document that defines a SOAP message.
SOAP Header: An optional, yet key element in architecting a distributed system around XML. The header element provides a modular way of directing SOAP servers to do processing before passing the SOAP message on. For example, it is possible to add SOAP header information that instructs a server to add transaction or authentication information. Header are also important in building piped architectures where processing is done in stages and data is modified as it is passed from handler to handler.
SOAP Body: An element that must appear in a SOAP message. The Body element is where the transported XML is loaded. SOAP makes no assumptions about the kind of XML transport in the body of a SOAP message. XML or it may take the form of remote procedure call.
also these weblogs can give you a view where you can use SOAP adapters
EP-XI Integration using Web Services and Web Dynpro MVC
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1334 [original link is broken] [original link is broken] [original link is broken]
Looking for replacing SAP.NET connectors with SAP XI?
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken]
how the connectivity is happening with Remote Clients?
A:Configuring the Sender SOAP Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
2.How sender SOAP Adapter get those webservices from remote clients and when exactly Remote clients will send webservices to SOAP Adapter?
It purely depends on ur client & if ur client provides WSDL file then u no need to develop it in ID and use that WSDL.WSDL describes a particular web service. Using a wsdl, we are requesting the broker to point the exact system, application, message interface. Once it is found, the SOAP channel is opened between the provider and the consumer. So the WSDL is a must to access web services.
in XI, we have to define the Web service which we want to use for the Sender SOAP channel. It is done by choosing Define Web Service from the tool menu of Integration Directory.
There is no need to code any thing. Here, what you are doing is, just exposing the sender service,channel,Message Interface as a web service.
In XI, we need to map the incoming messages to the target message( to the actual web service from the provider) format and to maintain the technical and logical routing between the sender and receiver.
Check this blog to generate WDSL file...
Exposing BAPI as Web Services through SAP XI
Configuring a SOAP Sender Channel:
When we create a SOAP sender channel we have to define the namespace and the name of a message interface (values can be taken from Integration Repository).
Select the Quality of Service according to your interface type. If you are using a synchronous interface, select Best Effort. Otherwise, select Exactly Once or Exactly Once in Order.
Transport protocol : HTTP
Message protocol : SOAP 1.1
Adapter Engine: Integration Server
3. I need exactly how the webservices request is passing through sender SOAP Adapter.
After completion of ur scenario u can use XML spy for testing ur scenario.
Refer this Blog how to send SOAP message from XML Spy
Invoke Webservices using SAPXI
Web Services Testing: SAP Netweaver Platform
http://www.crosschecknet.com/web_services_testing_SAP.php
Using the SOAP inbound channel of the Integration Engine
XI: Propagation of meaningful error information to SOAP Client
An Overview of SOAP
Refer the following blogs for SOAP sender Configuration:
How to Use the XI 3.0 SOAP Adapter
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
How Tou2026Set Up a Web-Service-Related Scenario with SAP XI
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/befdeb90-0201-0010-059b-f222711d10c0
have a look at this weblog:
How to use Client Authentication with SOAP Adapter
SOAP Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/content.htm
Architecture of connector for SAP XI
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst14.htm
Configuring the Sender SOAP Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
Security Settings for the Sender SOAP Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/1f/7e2441509fa831e10000000a1550b0/content.htm