This content has been marked as final. Show 4 replies
I have observed one thing:
The endpoint for service (without OWSM) is: B2B/Gateway
The endpoint for service (with OWSM) is: B2B/Gateway/Legacy
So when I change the endpoint of service (with OWSM) to B2B/Legacy (removed Gateway), then it is not causing any problem.
Can anybody pls explain this?
Looks like a bug to me. Raise a SR with support and if they confirm it as a bug then you will get a fix for it.
when I click the WSDL of the disabled proxy in browser it is automatically being redirected to the wsdl of other proxy service which doesn't have OWSM policy attached to itNot sure if I understand the problem properly, but how did you observe this? Did the URL change or just the content? Are you sure that's not a browser's cache issue?
The URL is same, but the content from the wsdl of Proxy service which doesn't have OWSM policy attached to it. Ideally it should display 404 error when the proxy is disabled, but on the contrary it is displaying the content of other Proxy service which has endpoint similar to this.
The only difference in the endpoints between the two services is:
Proxy with OWSM: B2B/Gateway/Legacy
Proxy without OWSM: B2B/Gateway
I've cleared the cache memory in IE. Even asked other's to open it in their systems.