Local Optimization With OWSM Policies
(Doc ID 2489934.1)
Last updated on AUGUST 19, 2022
Applies to:Oracle Web Services Manager - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Planning to apply oracle/wss_http_token_service_policy to all composites which are exposed outside of SOA environments,
a question arises about the use of local optimization at the owsm policy.
As the Oracle documentation mentions, "Local optimization enables you to bypass the HTTP stack and SOAP/normalized message conversions during run time".
When the oracle/wss_http_token_service_policy is disabled, the call goes through, a local invocation is made.
However, with this policy enabled, the call does not go through and an "unable to reach" Remote fault is thrown.
It is expected that composite-to-composite invocations should bypass OWSM policy for all internal calls. Is this the correct behavior?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document