A schematic diagram like the one below depending on component (e.g IDM, SOA, Service Bus, BI etc.) will have best practices and guidelines on how to install and configure Oracle products.
Following these guides is very much recommended, but keep in mind that there may still be caveats.
Before you decide on how to implement and deploy, please do keep in mind that any duplication of IP-addresses in a network (and yes it sounds basic) even if those are private may not be a good idea. The same goes for other shortcuts and host file manipulation. Please go through the documents carefully and think about the overall deployment architecture on an Enterprise level using DNS servers and DNS aliasing.
Most organizations do not have a updated, tested and verified plan on how to migrate their production environment to a disaster/recovery site (DR-Site). You should actually test and verfiy these migrations and plan your architecture accordingly. To help you Enterprise Manager has built-in functionality called Oracle Site Guard.
Oracle Site Guard is a part of Oracle Enterprise Manager Cloud Control, and basically a framework used to automate site failover/switchover. It will stop and start your Database, WebLogic servers, Web servers, storage mount points etc. Custom scripts are also supported.
To make it work properly you need a Load Balancer, and a DNS server with dns-aliasing features, and follow the direct approach of the MAA guides described above. A short video demo shows how it works (older version) and what you need to configure.
Just imagine all the error-prone and manual steps that you will avoid doing when your platform is burning around you with this controlled approach!
No comments:
Post a Comment