cancel
Showing results for 
Search instead for 
Did you mean: 

Implementing Webservices Doubt

Former Member
0 Kudos

Hi,

i have few queries in my mind

we have to integrate Third party webservices with our SAP R/3

1) Assume that in IDOC--- SOAP scenario( External Web Service) who has to generate the WSDL file????

2) In SOAP -


IDOC scenario( External web service) who has to generate the WSDL file.

Regards

Suman

Accepted Solutions (1)

Accepted Solutions (1)

prateek
Active Contributor
0 Kudos

1. Receiver side application has to generate the wsdl and give it to XI. XI will not generate wsdl in this case

2. XI will generate the wsdl and will give this wsdl to the soap client at sender

Regards,

Prateek

Former Member
0 Kudos

Hi ,

you said that

In case of SOAP is the sender means, XI has to genarate the WSDL File and has to give it to SOAP Client

In case of SOAP is the receiver means Third party has to generate the WSDL and has to give it to XI

Why this happenign what is the mechanism behind this process???

Q1) In IDOC-SOAP Scenario do we need to deply the WSDL file on XI Server to communicate and WHY???

Q2) In SOAP ---IDOC Scenario do we need to deploy any WSDL File on XI Server and Why???

Regards

Suman

Former Member
0 Kudos

hi suman,

if soap is a reciver then acording to third party requirement we making the structure for receiver side...

for using external message....

Incase of we using sender is SOAP they dont know our data structure sending the data for our structure..so that XI genrates WSDL and gave to third party...

Regards,

Prakasu

Former Member
0 Kudos

Hi Prakasu,

Not much clear your reply

Regards

Suman

Former Member
0 Kudos

Hi,

The basic thing behind the Webservice is to follow the wsdl structure.

On Sender side of SOAP we could create the WSDL file with defining the Webservice in ID and that can be deployed on Sender system to send the request message from web service.

On Receiver side normally the Webservice structure has to be define as per the receiver system so its preferrable to take the wsdl as per Receiver system and use it in XI as external defination.

In your IDOC-SOAP scenario, Web service is on receiver end and you have to develope the wsdl on receiver end as per the services provided by receiver system and the URL directs to receiver system.

Here you should not create the wsdl from XI as the url that you will be giving in XI will be pointing to XI Interface by giveing the service and communication details.

http://<Host>:<port>/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<communication channel>

In SOAP ---IDOC Scenario do we need to deploy any WSDL File on XI Server and Why???

Here SOAP will be sender and will be directing to XI server so we need to deploy it in XI.

I hope now its clear to you

Thanks

Swarup

Former Member
0 Kudos

Hi,

if SOAP is a Receiver then third party give the WSDL...

the WSDL have the structure and actions all those thinks..

if the WSDL have some

AA,

AB,

BB

fields. that time in mapping leavel we mapped Required mapping to that AA,AB,BB fields...

Here We Send the data to Third party...Acording do their requirement we mapped and send them to data...

If SOAP is sender then Third party wants to provide the data for us...

XI level we have structure like this..

XXX,

XYZ,

ZXX

that time they dont know our structure for providing the data ...

So that we Give the WSDL for them...

Regards,

Prakasu

Former Member
0 Kudos

Hi Prakasu,

Now I understood clearly,

I have one more doubt

In case of SOAP ---IDOC Scenario

After creating the Sender DT and all the things in IR, we will create the WSDL file??? OR do we have to create the WSDL File first and we shld use that wsdl file for SOAP Sender DT???Onoder to avoid the DT Creation for SOAP Sender Structure

Clear these

Regards

Suman

Former Member
0 Kudos

Hi,

As far as I know, you will have to cerate the sender data type and create the interface. from that you will have to create the WSDL and then export it and import it again as external definiton and use it.

Regards,

Merrilly

Former Member
0 Kudos

Hi,

You are saying that we have to create the DT and MT for SOAP Sender and create the WSDL File,

Then again you are saying that import that WSDL File in IR adn do the developement.

How far it will be fir ???

Regards

Suman

Former Member
0 Kudos

hi suman,

when ever you want to create a WSDL in Xi you need to give a message interface and namespace, software component and service or party names...

so Create WSDL file after creating IR and ID part ...

what is the behind is WSDL file will collect ur structure and sender interface along with party or service ...

i think now you will clear...

Regards,

Prakasu

Former Member
0 Kudos

Excellent Prakasu,

I have few more doubts

in case of SOAP is the sender means, you told that we need to create the WSDL File in ID and have to be deployed on XI.

Right????

How we will do this in XI , Where we will deploy,,using SDM??or in Visual Admin???

In case of SOAP is the receiver means where the third part systems will deploy the WSDL file which is generated by them???

Regards

Suman

Former Member
0 Kudos

Hi Suman,

Once you have created WSDL file for SOAP sender. No need to deploy it anywhere. Now this the source for creating your web service client and consuming it .

You can consume it through any other programming language using this URL

http://<host>:<j2ee-port>/XISOAPAdapter/

channel=:<service>:<channel>

If you are using SOAP receiver, it means you are calling some webservice through XI.

WebServices works with the HTTP protocol. You have to specify the url of the webservice.

Every WebService has a URL associated with it. This would be given by the provider of Web Service.

Regards,

Piyush

Please reward points if useful

Former Member
0 Kudos

Hi Piyush Gakhar

This means no need of any deployment of WSDL file in case of Either Sende or Receiver also??? Am i Right???

Regards

Suman

Former Member
0 Kudos

hi suman,

Just gone through the below blog...

[https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2684] [original link is broken] [original link is broken] [original link is broken];

Regards,

Prakasu

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

hi suman,

summing all previous post, in case the scenario is SOAP - IDoc,

you have to:

Define the DT,MT,MI, later, go to ID and create a Communication channel type soap sender.

complete the require fields, and save your changes.

later go to tool-->Define Web services. there, in the first step put this string

http://<server>:>java_port>/XISOAPAdapter/MessageServlet?channel=:<Businnes ystem>:<communication channel name>

for example:

http://serverPIDEV:50100/XISOAPAdapter/MessageServlet?channel=:APP_D:CC_app_soap_demo_sender

now,if the scenario is IDOC - SOAP,

you dont have to define any DT, MT, the receiver system team develope the WS. later they give you the URL where the ws is publicated. you link to the url and save the WSDL in your hard drive. later go to PI and import it as external definition, define the MI and thats all.

Thanks

Rodrigo

ps:Reward points if useful

Former Member
0 Kudos

Hi Suman,

No, there is not any need.

WSDL is generated when Web Services is deployed.

In XI case, it automatically deploy the Web Service and generate a WSDL file which you know. We have only to use that WSDL file to create Web Service client( exact message structure and param).

In Third Party case, they would deploy the web service and give WSDL file to you. So again no need to deploy the WSDL file.

You can use third party's WSDL file to create message structure(in IR) and technical parameters(URL mentioned in WSDL file) in SOAP receiver adapter.

Hope this helps.

Regards,

Piyush

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi buddy,

1) Assume that in IDOC--- SOAP scenario( External Web Service) who has to generate the WSDL file????

it is third party who ll generate and u ll consume

2) In SOAP -


IDOC scenario( External web service) who has to generate the WSDL file.

it is we who will generate using tool->define webservice in configuration.

Thanks & Regards,

Rama Krishna