In my organization, we are very big on DR site being available . In the event of any outage in the datacenter, the failover and failback processes are required to be nearly seamless. From the end user perspective, It is important for them to launch the same link for Smartview and be able to connect to Essbase, Reports, Planning.
In order to achieve this, we need the following:
Automatic DNS redirection
Any redirection tool of your choice can be implemented in your organization. In my case, both my production and DR VIPs are pointed to a separate dns url which gets the heartbeat information and redirects traffic to the primary or secondary site based on the response it gets from the status file. To make this happen, one can simply rename the file and that will make sure the traffic is redirected to the site that is active.
Oracle Wallet should contain the certificate information
This step is pretty standard and the same approach that needs to be adopted to implement SSL in the first place. In short, copy the cer file over to the destination environment. In Oracle Wallet, Open and import the certificate and save it. Also, if you have a load balanced setup we can simply copy the cwallet.sso and the ewallet.p12 file to Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component\keystores\default
Update the ssl.conf,mod_wl_ohs.conf and httpd.conf files
In a nutshell, make the entries match the production server setup.
On httpd.conf
include "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/admin.conf"
include "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/mod_wl_ohs.conf"
include "moduleconf/*.conf"
include "conf/ssl.conf"
Include "conf/epm_online_help.conf"
Include "conf/epm_rewrite_rules.conf"
Include "conf/epm.conf"
Include "conf/epm_online_help.conf"
Include "conf/epm_rewrite_rules.conf"
Include "conf/epm.conf"
On ssl.conf
NameVirtualHost *:443
ServerName example.hyperion.com
RewriteEngine On
Restart OHS with these changes populated. The redirection must happen now.
In order to achieve this, we need the following:
Automatic DNS redirection
Any redirection tool of your choice can be implemented in your organization. In my case, both my production and DR VIPs are pointed to a separate dns url which gets the heartbeat information and redirects traffic to the primary or secondary site based on the response it gets from the status file. To make this happen, one can simply rename the file and that will make sure the traffic is redirected to the site that is active.
Oracle Wallet should contain the certificate information
This step is pretty standard and the same approach that needs to be adopted to implement SSL in the first place. In short, copy the cer file over to the destination environment. In Oracle Wallet, Open and import the certificate and save it. Also, if you have a load balanced setup we can simply copy the cwallet.sso and the ewallet.p12 file to Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component\keystores\default
Update the ssl.conf,mod_wl_ohs.conf and httpd.conf files
In a nutshell, make the entries match the production server setup.
On httpd.conf
include "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/admin.conf"
include "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/mod_wl_ohs.conf"
include "moduleconf/*.conf"
include "conf/ssl.conf"
Include "conf/epm_online_help.conf"
Include "conf/epm_rewrite_rules.conf"
Include "conf/epm.conf"
Include "conf/epm_online_help.conf"
Include "conf/epm_rewrite_rules.conf"
Include "conf/epm.conf"
On ssl.conf
NameVirtualHost *:443
ServerName example.hyperion.com
RewriteEngine On
Restart OHS with these changes populated. The redirection must happen now.
No comments:
Post a Comment