OAM Policy And Configuration Changes Not Propagated To All Nodes In OAM Cluster

(Doc ID 1615674.1)

Last updated on AUGUST 08, 2017

Applies to:

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


Changes made to a WebGate profile is not getting propagated from the Admin Server to the Managed Server nodes.
This can be verified by checking the oam-config.xml version on the Managed Servers. The downstream effect of this is WebGates continuing to "bounce" between the old and new configuration profile, depending on which Managed Server instance they connect to.

Additionally, you might see cases where changes to OAM policy are not correctly propagated to Managed Server instances.

In both cases, a full restart of all managed servers seems to be the only thing that solves the issue/


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms