19.8 Best Practices for Replication

Here are some best practices to help you set up data replication.

The following points and the information in the sections should be taken into account when setting up data replication.

  • It is recommended that as many Policy Domain artifacts are created as possible before cloning. This will help the replication manager work efficiently during incremental updates.

  • The OAM server instance list will be used as the Well Known Addresses (WKA) to create a Coherence cluster so do not add other data center servers to the server instance list.

  • To allow for a WebGate profile to point to a remote data center in the secondary server list, use the Other option to provide OAP with the host and port details of the remote data center.

  • See Enabling Replication Logs

  • See Changing the User Identifier

19.8.1 Enabling Replication Logs

To get detailed logs on replication agreement and replication poll-related issues, enable the logger ‘oracle.oam.replication' by executing the WLST command.

setLogLevel(logger="oracle.oam.replication", level="TRACE:32", persist="0",

This enables logger only till next shutdown of AdminServer. To keep the logger state across restart, set the persist attribute to “1”.

19.8.2 Changing the User Identifier

While creating replication agreement if you have not specified any authorization header of the user to be used for replication if the user's password got changed at later point, you can edit the replication agreement with the latest user identity and password.

Run the following command:

curl -u <repluser> -H 'Content-Type: application/json' -X PUT
329353668' -d '{"replicaType":"CONSUMER","config":{"entry":
{"key":"authorization","value":"BASIC d2VibG9naWM6d2VsY29tZTE="}}}'