{"id":7409,"date":"2014-03-20T19:56:13","date_gmt":"2014-03-20T23:56:13","guid":{"rendered":"http:\/\/onlineappsdba.com\/?p=7409"},"modified":"2016-05-04T08:17:31","modified_gmt":"2016-05-04T12:17:31","slug":"addpartnerformultidatacentre-is-not-updating-mdc-partners-in-oam-config-xml-in-oam-11g-r2-ps2","status":"publish","type":"post","link":"https:\/\/onlineappsdba.com\/index.php\/2014\/03\/20\/addpartnerformultidatacentre-is-not-updating-mdc-partners-in-oam-config-xml-in-oam-11g-r2-ps2\/","title":{"rendered":"addPartnerForMultiDataCentre is not updating MDC partners in oam-config.xml in OAM 11g R2 PS2"},"content":{"rendered":"

In OAM 11g R2 PS2, I was working on Multi Data Center setup by following the documentation<\/a>. I had to run the WLST command addPartnerForMultiDataCentre<\/strong> by giving partnerInfo.properties file as input.<\/p>\n

What does this command do?<\/p>\n

In MDC, when the failover happens from DC1 to DC2, all the webgate requests will be routed to DC2 to serve. The user session would have cookies\/session pertaining to DC1. When the DC2 OAM servers serve the user request, then DC2 specific cookies\/session has to be present. Before that, DC2 OAM servers will talk to DC1 OAM servers through back channel using Access Gate.<\/p>\n

partnerInfo.properties<\/strong> contains the below details:<\/p>\n

remoteDataCentreClusterId=DC2_CLUSTER
\noamMdcAgentId=ACCESS_GATE_NAME
\nPrimaryHostPort=DC2_OAM_SERVER_NAME:port
\nSecondaryHostPort=
\nAccessClientPasswd=ACCESS_GATE_PASSWORD
\noamMdcSecurityMode=open
\nagentVersion=11g
\ntrustStorePath=
\nkeyStorePath=
\nglobalPassPhrase=
\nkeystorePassword=<\/p>\n

Let me explain every parameter:<\/p>\n

remoteDataCentreClusterId<\/strong>: This is the secondary Data center Cluster Name.<\/p>\n

oamMdcAgentId<\/strong>: Access Gate name which is making back channel call to DC1 for validating\/requesting user session details. By default in OAM 11g R2 PS2, accessgate-oic is created. I have used this in my case. Also, ensure that Allow Management operations flag is enabled in this AG profile. For quick test, you can verify the regular webgate profiles and see that this flag is disabled by default.<\/p>\n

PrimaryHostPort & SecondaryHostPort<\/strong>: Secondary DC OAM server host name and port eg., oam2.oracle.com:5575 and oam2.oracle.com:5576 respectively.<\/p>\n

oamMdcSecurityMode<\/strong>: Mode in which AG is running.<\/p>\n

agentVersion:<\/strong> AG version defined in profile.<\/p>\n

trustStorePath, keyStorePath, globalPassPhrase, keystorePassword<\/strong>: If AG is set in simple\/cert mode, provide the keystore and relevant details.<\/p>\n

Steps to run the command<\/strong><\/span>:<\/p>\n