connecting webservice to ecc

[Former Member]

Hi

want to connect webservice to R/3 .Here am getting input from Webservice like "Mat no" , so that If I choose SOAP to RFC synchronus ,then how would I get the input which is coming from webservice.

regards

srikant

[Former Member]

Hi Srikant,

While developing the SOAPtoRFC you will generate a WSDL right that can be used or consumed in any web applications like you can say you can consume that webservice in JavaWebDynpro or .Net application.

As a Developer for testing purpose you can use any XML tool kit like Altova xml spy or SAP Client tool ..etc.

If everything goes well then your webservice is correct .

/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i

/people/riyaz.sayyad/blog/2006/05/10/consuming-xi-web-services-using-web-dynpro-150-ui-design-part-iii

The above blogs will explain you how to consume a XI webservice in JavaWebDynpro.

Thanks,

Kalyan.

[dharamveer_gaur2]

hey

u can use SOAP request client, or altova to send request. as you mentioned that u r sending material no.

[Former Member]

Sender SOAP Adapter

Receiver RFC/IDOC/ABAP proxies.

IR

Step 1:

Create the Sender Datatypes for Request & Response

step2:

Create the MT for Req & Res

Step3 :

Create OB Message Interface ( Syncronous)

Step4 :

Import FM/BAPI

step5 :

Request Mapping : Sender Req MT--> FM Req

Response Mapping : FM Res----->Sender Res MT

Step6:

Interface Mapping

ID

Step1 :

Configure Sender Soap Adapter

Step2 :

Configure Receiver RFC Adapter

Step 3: Configure Sender Agreement, receiver determination,Interface determination,Receiver agreement

Step 4:

Create WSDL file.( ID->tools-Defien webservice)

save the file as .wsdl file

[Former Member]

. 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...

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

Web Services Testing: SAP Netweaver Platform

http://www.crosschecknet.com/web_services_testing_SAP.php

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-873...

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-f22...

have a look at this weblog:

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/d...

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

[Former Member]

If your scenario is SOAP to RFC, then you have to deploy the Sender side structure in XI and have to define the Webservice as mentioned in below blog,

Invoke Webservices using SAPXI

and you can send the request to SAP -RFC as below

Testing XI exposed Web-Services

soap to soap scenario