Do you have OAM, OMSM and Policy Manager servers in your environment? Are they all tied to same OAM WebLogic cluster or different clusters?
Well, the recommended approach is to tie respective weblogic server to respective cluster. Therefore, OAM servers should be associated with OAM Cluster, OMSM servers should be with OMSM cluster and so are Policy manager servers.
This post will explain about an issue that you may come across when WLS servers are associated in their respective cluster.
I will skip the steps for T2P commands on the Master DC as they are not relevant to this post. After running extraceMovePlan.sh script on Clone DC, it generates moveplan.xml which is the basis for pushing configurations into Clone DC and creating weblogic domain.
moveplan.xml contains server details and cluster details etc., for OAM servers, OMSM servers and Policy Manager servers.
The default xml template would look like as shown below.
Well, the recommended approach is to tie respective weblogic server to respective cluster. Therefore, OAM servers should be associated with OAM Cluster, OMSM servers should be with OMSM cluster and so are Policy manager servers.
This post will explain about an issue that you may come across when WLS servers are associated in their respective cluster.
I will skip the steps for T2P commands on the Master DC as they are not relevant to this post. After running extraceMovePlan.sh script on Clone DC, it generates moveplan.xml which is the basis for pushing configurations into Clone DC and creating weblogic domain.
moveplan.xml contains server details and cluster details etc., for OAM servers, OMSM servers and Policy Manager servers.
The default xml template would look like as shown below.
With this moveplan.xml, pasteConfig is failed.
After commenting out the omsm and policy manager server definitions in moveplan.xml, pasteConfig has worked.
Also, the weblogic domain was created for omsm and policy manager servers even though it was commented in moveplan.xml.
No comments:
Post a Comment