Does model._setHTTPDestinationName() work?

[Former Member]

I'm trying to use HTTP Destinations, as per this <a href="http://help.sap.com/saphelp_nw04/helpdata/en/59/e8e95d1eba48dfa86ae91ad8816f5d/frameset.htm">documentation</a> but they don't seem to work: if I specify a destination that doesn't work, the correct web service (defined in the original data model) is still invoked. Likewise, if I try to set the destination name to a destination that exists, yet points at an invalid URL, it still invokes the correct service. As a result, I can only assume that the original hard-coded URL is still used over the configured destination name.

Is anyone else using HTTP Destinations for Web Services in a Web Dynpro model?

If you're developing your own web service to be consumed in a Web Dynpro model, HTTP Destinations will let you transport your code between different environments with no code modifications - you only have to tweak the server config, and only once to create the destination.

[Former Member]

Ken,

If what you'd described works this way, then this is really cool!

I plan to use this feature to left authentication settings for HTTP destination, and use one destination for multiple endpoints. Did you check WS with authentication? Did destination settings propagated?

Regarding your original question. Why not to set endpoint URL directly on WS? I guess endpoints are stable and did not depend in any way on location of your __client__ WD model.

VS

[Former Member]

No, no authentication on the web service - yet. If I was to set the authentication, I would certainly use Logon Tickets, since most of the services would be invoked on behalf of the user...

The issue is that we're developing on both ends: both ABAP code (which may be accessible via web services), and on the Web Dynpro end. The destination URL will of course change as you move from dev to test to prod, so using an HTTP Destination seemed to be a nice solution to this problem.

So, in short, the endpoints aren't stable

[Former Member]

Ken,

Then (if destinations don't work and enpoints aren't stable) you may try IWDConfiguration instead, where each entry has format <LOGICAL_NAME>=<ENDPOINT_URL>. WD configurations could be edited in VisualAdministrator as well.

VS

[Former Member]

Hi Valery.

Can you please elaborate on how to work with IWDConfiguration? I want to change the logical name thru visual admin

Thanks

Som