cancel
Showing results for 
Search instead for 
Did you mean: 

SOAMANAGER webservice URL

fralarsen
Participant
0 Kudos

Hi,

we have some proxy webservices developed in ECC 6.0 NW ABAP 7.4. when these transports are imported in ECC 6.0 NW ABAP 7.0 system, the generated URL differs from that on the original system. The message type and binding names are not part of URL. We are facing an issue here as an external system always expects a URL format which differs in this case.

I would like to know whether this is case with only 7.0 or other versions like 7.1, 7.2 and 7.3 aswell. Basically, how to know the changes related to SOAMANAGER service url generation process ?

Accepted Solutions (1)

Accepted Solutions (1)

former_member198833
Active Participant
0 Kudos

Hi Naresh,

This is the normal behavior. In newer releases, the syntax of the WSDL URLs changed so the URL doesn't require a randomly generated ID, it uses the service access path to identify the service. You can find more information in KBA 2225859 - WSDL URL changed for ABAP Web Services with SOAMANAGER's new Single Configuration UI

I would advise you to contact the external system admin and let them know the URLs are now changed.

Cheers,
Felipe

fralarsen
Participant
0 Kudos

Hi Felipe,

Thanks for your response. Its Spot ON !!

Just one clarification. I'm little confused with the Environment and Product∏ versions listed in the Note. Is the new syntax applicable from SAP enhancement package 2 for SAP NetWeaver 7.0 and above(as mentioned in Product & ProductVersion) or SAP Netweaver 7.02 SP15 and above (as mentioned under Environment) ?

Regards,

Naresh

former_member198833
Active Participant
0 Kudos

Hi Naresh,

The correct details are in the Environment section, that is SAP Netweaver 7.02 SP15 and above. This is because the Product Version section does not offer to specify by SP, only by major versions, so we complemented the information in the text of the Environment.

Cheers,
Felipe

Answers (0)