A rule document created for the purpose of replicating can be modified as required.
The allowed transformation rules are represented by the XML document in the following example:
<mdc-transform-rule> <changes-to-include entity-path="/policy"/> <changes-to-include entity-path="/oauth"/> <changes-to-include entity-path="/IDM"/> <changes-to-include entity-path="/config/NGAMConfiguration/DeployedComponent/Agent/WebGate/Instance" /> <changes-to-include entity-path="/config/NGAMConfiguration/DeployedComponent/Server/NGAMServer/Profile/AuthenticationModules"/> <changes-to-include entity-path="/config/NGAMConfiguration/DeployedComponent/Server/NGAMServer/Profile/oamproxy"/> <changes-to-include entity-path="/config/NGAMConfiguration/DeployedComponent/Server/NGAMServer/Profile/Sme/SessionConfigurations"/> <changes-to-include entity-path="/config/NGAMConfiguration/DeployedComponent/Server/NGAMServer/Profile/OAMServerProfile"> <ignore attribute-match="/OAMSERVER/serverprotocol"/> <ignore attribute-match="/OAMSERVER/serverhost"/> <ignore attribute-match="/OAMSERVER/serverport"/> <ignore attribute-match="/OAMSERVER/serversslterminated"/> <ignore attribute-match="/HostAlias/oamserverHttps/serverprotocol"/> <ignore attribute-match="/HostAlias/oamserverHttps/serverhost"/> <ignore attribute-match="/HostAlias/oamserverHttps/serverport"/> </changes-to-include> <changes-to-include entity-path="/config/NGAMConfiguration/DeployedComponent/Server/NGAMServer/Profile/OAMServerProfile/OAMSERVER"> <ignore attribute-match="/serverprotocol"/> <ignore attribute-match="/serverhost"/> <ignore attribute-match="/serverport"/> <ignore attribute-match="/serversslterminated"/> </changes-to-include> <changes-to-include entity-path="/config/NGAMConfiguration/DataCenterConfiguration/Cluster"> <ignore attribute-match="/DataCenterType"/> <ignore attribute-match="/ClusterId"/> <ignore attribute-match="/WriteEnabledFlag"/> </changes-to-include> <changes-to-include entity-path="/config/NGAMConfiguration/DeployedComponent/Descriptors/OAMSEntityDescriptor" /> <changes-to-include entity-path="/config/NGAMConfiguration/DeployedComponent/Federation/IdentityProvider" /> <changes-to-include entity-path="/config/NGAMConfiguration/DeployedComponent/Federation/ServiceProvider" /> <changes-to-include entity-path="/config/NGAMConfiguration/DeployedComponent/Server/NGAMServer/Profile/STS/fedattributeprofiles" /> <changes-to-include entity-path="/config/NGAMConfiguration/DeployedComponent/Server/NGAMServer/Profile/STS/fedpartnerprofiles" /> <changes-to-include entity-path="/config/NGAMConfiguration/DeployedComponent/Server/NGAMServer/Profile/STS/fedserverconfig" /> </mdc-transform-rule>
The rule document will mention the XPath of system configuration artifacts to be replicated for a clone. If there is any transformation to be done during replication for the entry in XPath, it can be provided as replacement rule for that clone. To add a new XPath for replication to a clone, create a new transformation XML file, using the above XML document as a template. Add and remove XPaths as required. For example, adding the following XPath as the child of an <mdc-transformation-rule> node and saving the file to the clone's file system will modify Available Services.
<changes-to-include entity-path= "/config/NGAMConfiguration/DeployedComponent/Descriptors/ OAMSEntityDescriptor" />
Set the following VM property in the Clone's adminserver (setDomainEnv.sh) to use the newly created transformation rule document for replication instead of the OOTB one.
-Doracle.oam.MDCRuleFile=/path/to/rule/mdcrule.xml
For developer recommendations when using replication, see Best Practices for Replication.