Query regarding wsdl

[Former Member]

Dear SCNers

We have a .net application to R/3 scneario. We have configured the scenario as Soap Sender to RFC Receiver. Scenario works fine and hase been tested like this:

a. in ID - Display Web service. The wsdl was downloaded and tested through Altova

b. In ID - Publish in SR from Sender Agreement. This was tested through WS Navigator. This generated a wsdl url and the wsdl url internally calls the soap adapter url as in channel=:party:service:channel

Now we need to provide the wsdl to the .net developers, which one should be provided and which url should be called by them.

Regards

Monika

[MichalKrawczyk · Accepted solution]

Hi,

>>>Now we need to provide the wsdl to the .net developers, which one should be provided and which url should be called by them.

they need to be able to change the URL in net app so provide them with one from dev

and just tell them that on QA and PRD it will be different

Regards,

Michal Krawczyk

[Former Member · Accepted solution]

Hi Michal

You mean http://hostname:8000/XISOAPAdapter/MessageServlet?channel=:Sender Component:Soap_Sender_CC.

This is the soap adapter url.

and the one which i have recieved after publishing in SR from Sender Agreement is

http://hostaname:8000/dir/wsdl?p=sa/b194e71438883c2a8fcb8fb37b776a16 (this wsdl internally calls the above soap url)

Regards

Monika

[Former Member · Accepted solution]

Any inputs?

[Former Member · Accepted solution]

HI Monika,

Can you try with the WSDL which WS administrator has , select your service and Open WSDL document for selected binding

just set the WSDL options and set WSDL format as standard.

Open the WSDL and save it as WSDL and import in soap UI tool, you may have to give the endpoint manualy,just copy paste the which appears in the WSnavigator(custome Endpoint).

If you are trying to test from WSDL created from the ID, then its a standard way which we used to follow, Please let me know what error you are getting.Try using SOAP UI instead of altova xml spy.

Regarsd,

Srinivas

[Former Member · Accepted solution]

Dear Srinivas\

Checking in th Altova with the standard way ID-Define services works..bt not with the wsdl of Sender Agreeent.

regards

Monika

[Former Member · Accepted solution]

Hi Monika,

Could you please cross check the if the sender agrement you are refering to generate the WSDL is the correct one.

Actually if we create from Tools -Display wsdl we will be enterning the details manually and throufh Sender agrement we dont need to . And to my knowledge that is the only difference and a point of error is maintaining the correct sender agrement details as you maintained while creating from Tools.

Regards,

Srinivas

[Former Member]

Hi Monika

in ID - Display Web service. The wsdl was downloaded and tested through Altova

You can give the one which is generated from ID,this is the way it has to be done till PI 7.1

Actually using SR is also a similar approach but many of us have not tried it as its a new feature in PI 7.1.

I suggest you to give it a try and see if .Net application can access the SR generated wsdl URL.

Testing through WS navigator is a internal testing in SR to check if posting is happening fine.I think the wsdl url which is generated in SR will also trigger the same interface as its the comes from the same WSDL document.

Please give it a try and let us know what is the difference in using the old and new approach.

Regards,

Srinivas

[Former Member]

Hi Srinivas

I am also trying to figure out the same Hence thought of sharinf with the SCN members. The wsdls appear similar.

I believe the one published in SR is a wrapper over the soap url.

For the one published in SR also, i am not sure which needs to be given to the .net team

http://hostname:8000/dir/wsdl?p=sa/b194e71438883c2a8fcb8fb37b776a16

http://hostname:8000/dir/wsdl?p=sa/b194e71438883c2a8fcb8fb37b776a16/binding

http://hostname:8000/dir/wsdl?p=sa/b194e71438883c2a8fcb8fb37b776a16/portType

Regards

Monika

[Former Member]

Hi Monika,

I don't understand what is your problem ? Because you are able to download the .wsdl and tested successfully using Altova.

You should able to provide the same thing to .net developer. They should read the wsdl because all the information is there.

Regards

Fernand

[Former Member]

Hi Fernand

the strange thing is the wsdl through wsnavigator is not getting successfully tested through altova. It works only from wsnavigator.

For Altova, the wsdl is getting downloaded from ID- Define wsdl and providing details like sender nterface, namespace ect.

Regards

Monika