external https web service

[Madjid_Khanevadegi]

Hello all abap developers

i want access to external web service with https

i add a new service consumer and register web service certificate

but in "soamanager" t-code for web service configuration . enconter with this error "No Service found in WSDL" . and can not make a new port that used it in abap code . Maybe guide me

thank you so much

[UweFetzer_se38]

Are you able to manually download and inspect the WSDL? Maybe there's really no service defined in it...

[Madjid_Khanevadegi]

hello Uwe Fetzer

yes , when i direct access to these service , i have XML of that

for the more , i can used this web service from C#.net and test it successfully

thanks

[UweFetzer_se38]

Can you upload the previously downloaded WSDL to SOA-Manager? (On the same screen as above, just don't select "HTTP Access" but "WSDL from Upload"). Do you get the same error message?

[Madjid_Khanevadegi]

before upload WSDL file , Analyze it in "WSDL Analyzer" of soa-manager and show this error "unsupported fragment"

[attila_mikulan]

Hello Madijed,

Without checking the entire WSDL it's difficult to figure out what might be missing. Based on the SOAMANAGER error (No service found) my assumption is that the <wsdl:service ... > element is not correct, or entirely missing.

A few things to check:

- service must come after the wsdl:binding part, the order of the WSDL elements are not flexible in many R/3 releases

- the namespace of the service element

- it refers to the binding part properly

Regarding the unsupported elements: it's not enough information for me to tell if that could be the cause, but I doubt that.

As an alternative, you can simply create a logical port manually, without using the WSDL file. You can find the steps in the SAP Help portal here.

Hope this helps. If not and the WSDL can be shared publicly, please upload it and then we can check it better.

Cheers,
Attila

[Madjid_Khanevadegi]

thank you Attila

i scan XML file and find that two tag is that make this error

<sp:EndorsingSupportingTokens xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">

and

<sp:SecureConversationToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">

[attila_mikulan]

I don't have experience with these elements, but I'm not sure if these are the problem. I would expect different error message during LP creation if it was caused by unsupported elements. Did you check manual logical port if that is feasible solution for you?