cancel
Showing results for 
Search instead for 
Did you mean: 

WSDL Generation / Publishing with external URLs in endpoints.

Former Member
0 Kudos

Hi All,

I was hoping someone could assist, I am using PI 73ehp1 and trying to publish / generate a WSDL for an integrated configuration, I am using the Publish to SR functionality in IB. I have web dispatcher configured on the box and I want the WSDL to have the URL / port of the web dispatcher not the url of the application server.

Reading the help it seems like the reverse proxy config of SOA Global Settings in NWA would do the trick, my understanding was that if I configure this correctly and mark as relevant for SR publishing, and then publish my service to the SR, I should see the external endpoints in the published WSDL. For example from help:  (http://help.sap.com/SAPhelp_nw73/helpdata/en/78/8fbce344ff418abc1870cd16838a91/frameset.htm)

"....The system uses this default value for the generation of the first part for

external endpoint/WSDL URLs published in Services Registry."

But I cannot get it to do this. When I configurre the WS HTTP Proxy to have the URL mapping i desire it does not affect the URLs in the published. The only result of this seems to be that the "internal" link to the SR http://<appserver>:<port>/sr now redirects using the values configured in the reverse proxy, which I don't really want! So I don't get the result I want but I get an annoying side effect.

I can acheive what I want by using the "options" button (while publishing from IB) and selecting "Overwrite URLs During Publication" but I don't want to manually do this every time, it is prone to error and is time consuming. I just want to set something up to say that all WSDLs published to the SR should contain the webdispatcher details in the URL not the "internal" app server and port.

Can anyone point me in the right direction? I am running out of things to try.

Thanks

Chris

Accepted Solutions (0)

Answers (1)

Answers (1)

pereira_nuno
Explorer

Hi Christopher,

I know that has been more than 1 year since your question and most probably you already solved this issue but, for the record, here goes a trick to influence the WSDL generation out of a integrated configuration or classic scenario.

You simply have to add “&endp_url=https://<wdisp_host>:<wdisp_port>” (filled with valid content)  to the WSDL generation URL and the Endpoint URL for the SOAP Sender will be changed within the generated WSDL.

Further info is available at https://<host>:<port>/dir/wsdl of you PI system.

Hope this can help, if not you, future ones.

BR,

NP