Topic
  • 6 replies
  • Latest Post - ‏2012-12-20T16:02:50Z by SystemAdmin
Jaango
Jaango
267 Posts

Pinned topic Wsdl enpoint soap address

‏2012-05-15T10:26:15Z |
Consider the attached wsdl. If we upload the same wsdl to a datapower webserviceproxy and access through "http://frontsidehandlerip:port/uri?wsdl", in the browser, the soap address of wsdl changes from "http://localhost:8088/external-services-0.0.1-SNAPSHOT/webservices/HotelPriceService" to "http://frontsidehandlerip:port/uri", which is fine.

However if our client access this in their browser, they will be able to see the frontsidehandlerip, which we do not want. How can we prevent this? We have a Loadbalancer name, which we can expose to the client. Is there a way that we can have the client view like "http://loadbalancername:port/uri", within the soap address?

Performed some research and we found that we can uncheck "Use Local" option just beneath the wsdl and give a url, which will be loaded while giving in the browser. We dont want that option as with that option we lose the ability to retain info (http/https - we can have https and http handler) from originating request.
Updated on 2012-12-20T16:02:50Z at 2012-12-20T16:02:50Z by SystemAdmin
  • Daviiid
    Daviiid
    344 Posts

    Re: Wsdl enpoint soap address

    ‏2012-05-15T12:09:48Z  
    Hello

    You can force the adress expose by datapower if you uncheck "Published Use Local".

    After you can indicate your adress.
  • Jaango
    Jaango
    267 Posts

    Re: Wsdl enpoint soap address

    ‏2012-05-15T12:16:44Z  
    • Daviiid
    • ‏2012-05-15T12:09:48Z
    Hello

    You can force the adress expose by datapower if you uncheck "Published Use Local".

    After you can indicate your adress.
    Thanks Daviid. We do not want to use that option, as with that option we cannot retain whether it is http or https is present from the originating request.
  • Daviiid
    Daviiid
    344 Posts

    Re: Wsdl enpoint soap address

    ‏2012-05-15T13:23:40Z  
    • Jaango
    • ‏2012-05-15T12:16:44Z
    Thanks Daviid. We do not want to use that option, as with that option we cannot retain whether it is http or https is present from the originating request.
    sorry

    I have no idea
  • SystemAdmin
    SystemAdmin
    6772 Posts

    Re: Wsdl enpoint soap address

    ‏2012-05-15T22:00:46Z  
    If you want to achieve this, probably you may need to create an MPG frontending ws-proxy and create a processing response rule with match rule as *.wsdl, and add a transform action with xslt to change the endpoint dynamically depends on your request. The flow will be client -> Load balancer -> MPG -> WS-proxy.
  • Jaango
    Jaango
    267 Posts

    Re: Wsdl enpoint soap address

    ‏2012-05-16T11:49:38Z  
    If you want to achieve this, probably you may need to create an MPG frontending ws-proxy and create a processing response rule with match rule as *.wsdl, and add a transform action with xslt to change the endpoint dynamically depends on your request. The flow will be client -> Load balancer -> MPG -> WS-proxy.
    Thanks. It worked.
  • SystemAdmin
    SystemAdmin
    6772 Posts

    Re: Wsdl enpoint soap address

    ‏2012-12-20T16:02:50Z  
    • Jaango
    • ‏2012-05-16T11:49:38Z
    Thanks. It worked.
    Hello, I am having a similar problem. Jaango could you please post the XSLT you created?

    Thanks in advance