Skip to Content
avatar image
Former Member

URL redirection config in PI SOAP receiver communication channel

Hi,

I am working on a similar scenario where I my consuming an external web service using https protocol from PI.

I have configured a soap receiver channel to call the target url of this web service as https://portal.xyz.org.uk/webservice_alt.

I am getting an error HTTP 302 suggesting that PI is not able to follow the re-direction to the target URL as the service resides not on that URL but on https://portal1.xyz.org.uk/webservice_alt or https://portal2.xyz.org.uk/webservice_alt.

This is their server fail over handling mechanism which is very common. But PI 7.0 is not able to handle this.

So if I change the target URL on the SOAP receiver channel to https://portal1.xyz.org.uk/web service or https://portal2.xyz.org.uk/webservice_alt , PI works fine without errors . But this is not the right approach because, every time the web service provider takes one of these systems down for upgrade/patching etc, they inform us and then I manually go and change the target URL to the available server on my production PI system config. 😔

My problem is I want to resolve this redirection error in PI. I have tried raising a call with SAP itself and they pointed out to use Axis adapter which is still not working.

So I am here asking for help. any suggestions please from the experts?

Thanks

Jhansi.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Mar 10, 2011 at 01:56 PM

    Hi Jhansi,

    if you want to avoid changing a lot channels you can put as target host a dummy and link that to a IP in PI's host file. So in case the target address changes you have to change only the host file.

    If there are just one or two receiver channels it is of course easier to change them directly.

    Regards,

    Udo

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Baskar Gopalakrishnan

      Hi Baskar,

      Thanks for your time but I think the link you pointed out is config we could do using CE7.1 we are on Netweaver 2004s, PI 7.0

      so doesn't help besides the fact that I couldn't really understand what config to put in place to handle this even if we were at the versions as per the document link. 😔

      Thanks very much anyways.

      Kind Regards,

      Jhansi.

  • Mar 10, 2011 at 02:36 PM

    Hi Jhansi,

    The HTTP 302 - Found error suggests that "the requested resource resides temporarily under a different URL. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URL for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.

    The temporary URL SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URL(s).

    If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued."

    It's kind of theoretic but may helps!

    Regards,

    Caio Cagnani

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Caio Cagnani,

      I have read this before referred in general rules for HTTP codes.

      All said, I need help in understanding how to do this in PI.

      thanks for your time anyways.

      Kind Regards,

      Jhansi.