Skip to Content
author's profile photo Former Member
Former Member

Difference between Porttype WSDL Doc and WSDL doc for selcted binding

Hi all,

We have an SAP ERP system in our office which runs on ABAP Stack

our ECC environment is as follows ERP 2005, RELEASE 6.0, KERNEL 7, ECC 6.0 NON -UNICODE SYSTEM,BASIS & ABAP SP 14

We have a CRM system which runs on Java Stack. We configured the SOAMANAGER in CRM system and with some BASIS settings both on CRM and ECC system...we are now able to use the SOAMANAGER in CRM system to manage the Web Services from our ECC System too.

Now I am trying to understand a few basic things. When I create a Web Service for a RFC enable function module and see the Web service in SOAMANAGER,...in the Overview Tab of the Web Service ..I find two WSDL's file named as

1) Open porttype WSDL document

2) Open WSDL document for selected binding

I gave both WSDL''d to the JAVA team in our office and they are able to consume both of the WSDL's and able to enable communication between ECC and .JAVA.

But when i observe the two WSDL'd files, I find the Port type WSDL doesnt give information about the Binding, Service name and SOAP Address Location.

I am wondering and trying to understand what is the difference between these two WSDL''s and what is thje best practice to use.

By the way we are not using PI, but using ABAP Web services to enable communication btw SAP and JAVA

Some one please help me understand the architectural break down of these two WSDL' file and why to use which file.

Regards,

Jessica Sam

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on May 21, 2009 at 07:27 AM

    Hi

    I observed the same thing. Did you solve the question?

    cheers

    gabriele

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 21, 2009 at 04:28 PM

    The port type WSDL only has the details of the operation and the message. the binding WSDL has details about the actual end point where it is implemented. You have to use the binding WSDL to be consumed. In SOAMANAGER, open the binding WSDL and give it to external parties. We dont need the Java server for getting the binding WSDL (it is needed only for testing the service). The help http://help.sap.com/saphelp_nw70/helpdata/EN/47/3431de6c720aa7e10000000a114a6b/frameset.htm is pretty good on this topic.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.