My Oracle Support Banner

Local Optimization with OWSM Local Attached Policy is not Taking Effect (Doc ID 2982798.1)

Last updated on OCTOBER 24, 2023

Applies to:

Oracle Web Services Manager - Version and later
Information in this document applies to any platform.


After enabling local optimization on BPEL composites (composite B and composite A), and then enabling local optimization on custom binding_authorization_permitall_policy, it was observed that after attaching the OWSM policy to composite B and then invoking this composite from composite A, the invocation was not done locally which is not the expected behavior.

It was also observed that to make it work, the policy has to be disabled, and then the composite is run for the call to be run locally. After enabling the OWSM policy again, the call is also run locally. However, this is not a good workaround in a production environment especially, after redeployment or a restart of the server, the issue will occur until disabling and enabling the policy again.

The expected behavior should be that if an OWSM policy, having local optimization on, is attached to a composite that has local optimization enabled, then the call should be local.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.