Click Protocol, and select HTTP. Click Activate Changes in the Change Center window to enable editing.

12-38 Oracle Fusion Middleware High Availability Guide Invalidation User Name: Enter the user name for Portal invalidations. Invalidation Password: Enter the password for this account.

i. Click Apply to start the rewire.

j. When the rewire is complete, click the Portal menu option again, and ensure

that the Portal URL is now the following: https:cfcvip.mycompany.com:WCHTTPPortportalplsportal 8. Change Host Assertion in Oracle WebLogic Server. Because the Oracle HTTP Server acts as a proxy for WebLogic, by default certain CGI environment variables, including the host and port, are not passed through to WebLogic. TO ensure that Web Logic is ware that it is using a virtual site name and port so that it can generate internal URLs appropriately: a. Log in to the WebLogic Server Administration Console using the following URL: http:cfcvip.mycompany.com:7001console

b. Select WLS_PORTAL from the home page or select Environment, and then

Clusters from the Domain Structure menu.

c. In the Change Center, click Lock Edit.

d. Click Protocol, and select HTTP.

e. Enter the following values: Frontend Host: Cfcvip.mycompany.com Frontend HTTP Port: WCHTTPPort 8090 Frontend HTTPS Port: WCHTTPSPort 8094 This ensures that any HTTPS URLs created from within WebLogic are directed to port 443 on the load balancer.

f. Click Activate Changes in the Change Center window to enable editing.

g. Restart the WLS_PORTAL managed server

12.2.3.10.5 Transforming Oracle Business Activity Management BAM Oracle BAM is made

up of Java EE components deployed to a managed server. Since these are Java EE components, the Cold Failover Cluster transformation procedure involves configuring the managed server to which they are deployed to listen on the virtual IP. See Section 12.2.2.4, Transforming Oracle WebLogic Managed Servers for information on transforming managed servers WLS_BAM. When using Oracle HTTP Server as the front end, the mod WebLogic configuration for the applications deployed to WLS_BAM should provide the VIP cfcvip.mycompany.com as the address of these managed server. To do this, change the WebLogic host configuration in the webserver proxy plugin configuration files for the mount points used by SOA components. For example, use a text editor to make the following edits in the mod_wl_ohs.conf file: BAM Web Application Location OracleBAM SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-39

12.2.3.10.6 Transforming a Custom ADF Deployment For a deployment that uses a custom

ADF application, Cold Failover Cluster can be used in the same way as any of the Fusions Middleware deployment. The domain is created in this case using the installation from Oracle Application Developer DVD. Since this is primarily a Java EE components. the Cold Failover Cluster transformation procedure involves configuring the managed server to which they are deployed to listen on the virtual IP. See Section 12.2.2.4, Transforming Oracle WebLogic Managed Servers for information on transforming managed servers. When using Oracle HTTP Server as the front end, the mod WebLogic configuration for the applications deployed to WLS_ADF the name of the managed server for the customer app should provide the VIP cfcvip.mycompany.com as the address of these managed server. To do this, change the WebLogic host configuration in the webserver proxy plugin configuration files for the mount points used by SOA components. For example, use a text editor to make the following edits in the mod_wl_ohs.conf file: BAM Web Application Location ADFApplicationMountPoint SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location

12.2.3.11 Transforming an Oracle Enterprise Content Management Suite

The Oracle Enterprise Content Management Suite ECM Suite has products such as Oracle Imaging and Process Management Oracle IPM, Oracle Universal Content Management Oracle UCM, Oracle Universal Records Management URM, and Oracle Inbound Refineries Oracle IBR. These managed servers typically included when the ECM Suite is installed: ■ Oracle IPM WLS_IPM ■ Oracle UCM WLS_UCM ■ Oracle URM WLS_URM ■ Oracle IBR WLS_IBR For Cold Failover deployments, the recommendation is to set up the Application tier and the Web tier as recommended for CFC deployments in previous sections of this chapter, and to follow the procedure for Cold Failover Cluster transformation for these managed servers. See Section 12.2.2.4, Transforming Oracle WebLogic Managed Servers for information on transforming Oracle IPM, UCM or URM, and IBR managed servers. Additional things to consider in Cold Failover Cluster deployments of ECM Suite include: ■ In many Cold Failover Cluster deployments of ECM Suite, the likely deployment topologies include: – Both IPM and UCM deployed together on the same node of a hardware cluster. – A deployment with IPM on one node of a hardware cluster and UCM on the other node of a hardware cluster and configured for mutual failover. ■ All IPM related files that need to be available when the IPM server fails over should also be on the shared disk. This includes files such as the input files and the images. These should always be on the shared disk so they are accessible from all 12-40 Oracle Fusion Middleware High Availability Guide nodes of a CFC configuration. It is recommended that there is a separate volume for the input files and the image files. ■ All persistence stores such as one used by JMS and TLogs should also be on the shared disk. ■ All restrictions related to Inbound Refinery continue to apply in a CFC configuration. For information on configuring Inbound Refinery instances, refer to Oracle Fusion Middleware Administrators Guide for Conversion. ■ All content related folders for UCM should be on a shared disk as well, which will fail over as a unit along with the UCM server configuration. This includes folders such as: – Content server instance folder – Native File repository location – Web Layout folder ■ When configuring UCM or URM using http:cfcvip.mycompany.com:portcs, the Webserver HTTP Address is the hostname and port of the location of the HTTP server front-ending the ECM managed servers. Depending on the high availability configuration of the HTTP server this can be a load balancer address, physical host or a virtual host. In the case where Oracle HTTP Server is also in a CFC deployment, the above value should be set to the virtual IP of the Oracle HTTP Server. When Oracle HTTP Server is collocated on the same hardware cluster as the ECM servers, this is likely to be cfcvip.mycompany.com. ■ In cases where UCM is configured to be in a Cold Failover Cluster including the example above, when IPM is wired to UCM, the recommendation is to use the virtual IP address of UCM. When doing this configuration using http:cfcvip.mycompany.com:portimaging:

1. In the left-hand pane, click Manage Connections, and then Create Content

Server Connection .

2. Enter a name and description for the new connection, and then click Next.

3. In the Connection Settings screen, enter the following: – Content Server Version: CS 11g – Primary: cfcvip.mycompany.com:4444 Click Next. 4. In the connection security screen, leave the default selections for the WebLogic user, and then click Next.

5. Review the connection details and click Submit.

■ In addition, when Oracle HTTP Server is used as the front end for ECM Suite applications, the mod_weblogic configuration should use the VIP cfcvip.mycompany.com as the address of the managed servers. To do this, change the WebLogic host configuration in the webserver proxy plugin configuration files for the mount points used by ECM components. For example, use a text editor to make the following edits in the mod_wl_ohs.conf file: LoadModule weblogic_module {ORACLE_HOME}ohsmodulesmod_wl_ohs.so Content Server Location cs SetHandler weblogic-handler Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-41 WebLogicHost cfcvip.mycompany.com WebLogic port WLCookieName IDCCS_SESSIONID Location URM Location urm SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port WLCookieName IDCURM_SESSIONID Location IBR Location ibr SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port WLCookieName IDCIBR_SESSIONID Location IPM Location imaging SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location

12.2.3.12 Transforming Oracle Business Intelligence

Oracle Business Intelligence is an integrated business intelligence BI solution that provides the business user with a complete picture across the entire organization. Oracle Business Intelligence is designed to quickly and easily integrate diverse data sources, find information from the database, share the database information, and exploit the data to learn more about the business and its customers. This section describes active-passive high availability for Oracle Business Intelligence Enterprise Edition, Oracle Business Intelligence Publisher and Oracle Real-Time Decisions.

12.2.3.12.1 Transforming Oracle Business Intelligence Enterprise Edition and its Clients This

section describes how to transform Oracle Business Intelligence Enterprise Edition Oracle BI EE to work in a Cold Failover Cluster environment. Transforming Oracle Business Intelligence Enterprise Edition The following section describes how to transform Oracle BI EE to work in a Cold Failover Cluster environment. Transform Managed Server Oracle BI Enterprise Edition is deployed to a managed server for example, BI_ SERVER1 and the procedure for Cold Failover Cluster transformation is to configure this managed server after install to listen on the virtual IP cfcvip.mycompany.com. Follow the steps in Section 12.2.2.4, Transforming Oracle WebLogic Managed Servers to configure the BI_SERVER1 managed server to listen on the cfcvip.mycompany.com virtual IP. After these steps, restart the managed server using the WebLogic Server Administration Console or the WLST command line. 12-42 Oracle Fusion Middleware High Availability Guide All requirements for placing the Middleware Home and other related domain artifacts on shared storage that can be failed over apply as Section 12.2.1, General Requirements for Cold Failover Cluster describes. The specific requirement for Cold Failover Cluster deployments of the Oracle BI Enterprise Edition is to ensure that the following artifacts are also on the shared disk and available on the same mount points on both nodes of the failover cluster. When configured in the default install, this happens implicitly: ■ BIEE Presentation Catalog ■ BIEE Repository Publishing Directory RPD To transform an Oracle BI EE component managed server: 1. Edit the biee-domain.xml file to replace the hostname with cfcvip.mycompany.com. The biee-domain.xml file is located in this directory: MW_HOME user_projectsdomainsbifoundation_domainconfigfmwconfig 2. Set the front-end host for the BI_SERVER managed server to cfcvip.mycompany.com. a. Log into Oracle WebLogic Server Administration Console.

b. In the Environment section, select Servers.