7-12 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite
Location _ocsh WebLogicCluster ECMHOST1:16200,ECMHOST2:16200
SetHandler weblogic-handler WLCookieName JSESSIONID
WLProxySSL ON WLProxySSLPassThrough ON
Location
2.
Restart Oracle HTTP Server on both WEBHOST1 and WEBHOST2. WEBHOST1 ORACLE_BASEadmininstance_namebinopmnctl restartproc
ias-component=ohs1 WEBHOST2 ORACLE_BASEadmininstance_namebinopmnctl restartproc
ias-component=ohs2
7.11 Validating Access Through Oracle HTTP Server
You should verify URLs to ensure that appropriate routing and failover is working from Oracle HTTP Server to UCM_Cluster. Perform these steps to verify the URLs:
1.
While WLS_UCM2 is running, stop WLS_UCM1 using the Oracle WebLogic Server Administration Console.
2.
Access http:WEBHOST1:7777cs to verify it is functioning properly.
3.
Start WLS_UCM1 from the Oracle WebLogic Server Administration Console.
4.
Stop WLS_UCM2 from the Oracle WebLogic Server Administration Console.
5.
Access http:WEBHOST1:7777cs to verify it is functioning properly.
7.12 Configuring Node Manager for the WLS_UCM and WLS_IPM Managed Servers
Oracle recommends using host name verification for the communication between Node Manager and the servers in the domain. This requires the use of certificates for
the different addresses communicating with the Administration Server and other servers. See
Chapter 9, Setting Up Node Manager for further details. The procedures
in that chapter must be performed twice using the following information:
Optional; required only for WLS-managed Oracle IPM servers WLS_IPM.
Please note the following:
■
Even though the WLS_IPM managed servers are not yet configured at this point see
Chapter 8, Extending the Domain with Oracle IPM and are not mandatory
for a UCM-only Oracle ECM installation, the virtual host names used by Oracle I PM are configured here in order to provide a one-step configuration process that
includes both types of servers.
Run Host Name HOST
Virtual IP VIP Server Name WLS_SERVER
Run 1: ECMHOST1
ECMHOST1VHN1 WLS_UCM1
Run 2: ECMHOST2
ECMHOST2VHN1 WLS_UCM2
Extending the Domain with Oracle UCM 7-13
■
Perform all steps in Chapter 9, Setting Up Node Manager
except for Section 9.3.5, Configuring Managed WLS Servers to Use the Custom Keystores
for the WLS_IPM servers. This step can be done after the WLS_IPM servers are added to the domain.
7.13 Backing Up the Installation
After you have verified that the extended domain is working, back up the installation. This is a quick backup for the express purpose of immediate restore in case of
problems in the further steps. The backup destination is the local disk. This backup can be discarded once the enterprise deployment setup is complete. At that point, the
regular deployment-specific backup and recovery process can be initiated. The Oracle Fusion Middleware Administrators Guide provides further details. For information on
describing the Oracle HTTP Server data that must be backed up and restored, refer to the Backup and Recovery Recommendations for Oracle HTTP Server section in that
guide. For information on how to recover components, see the Recovery of Components and Recovery After Loss of Component sections in the guide. For
recommendations specific to recovering from the loss of a host, see the Recovering Oracle HTTP Server to a Different Host section in the guide. Also refer to the Oracle
Database Backup and Recovery Guide for information on database backup.
Perform these steps to back up the installation at this point:
1.
Back up the web tier:
a.
Shut down the instance using opmnctl. WEBHOST1 ORACLE_BASEadmininstance_namebinopmnctl stopall
b.
Back up the Middleware Home on the web tier using the following command as root:
WEBHOST1 tar -cvpf BACKUP_LOCATIONweb.tar MW_HOME
c.
Back up the Oracle Instance Home on the web tier using the following command:
WEBHOST1 tar -cvpf BACKUP_LOCATIONweb_instance_name.tar ORACLE_INSTANCE
d.
Start the instance using opmnctl: WEBHOST1 cd ORACLE_BASEadmininstance_namebin
WEBHOST1 opmnctl startall
2.
Back up the database. This is a full database backup either hot or cold using Oracle Recovery Manager recommended or operating system tools such as tar
for cold backups if possible.
3.
Back up the Administration Server and managed server domain directory to save your domain configuration. The configuration files all exist in the ORACLE_
BASEadmindomain_name directory. Run the following command to create the backup:
SOAHOST1 tar -cvpf edgdomainback.tar ORACLE_BASEadmindomain_name
7-14 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite
8
Extending the Domain with Oracle IPM 8-1
8
Extending the Domain with Oracle IPM
This chapter describes how to extend a domain with Oracle Imaging and Processing Management Oracle IPM using the Oracle Fusion Middleware Configuration
Wizard. It contains the following sections:
■
Section 8.1, About Adding Oracle IPM to a Domain
■
Section 8.2, Enabling VIP4 and VIP5 in ECMHOST1and ECMHOST2
■
Section 8.3, Extending the Domain to Include Oracle IPM
■
Section 8.4, Propagating the Domain Configuration to ECMHOST1 and ECMHOST2 Using the unpack Utility
■
Section 8.5, Starting Node Manager on ECMHOST1 and ECMHOST2
■
Section 8.6, Restarting the Administration Server
■
Section 8.7, Configuring a JMS Persistence Store for Oracle IPM JMS
■
Section 8.8, Configuring a Default Persistence Store for Transaction Recovery
■
Section 8.9, Disabling Host Name Verification for the WLS_IPM Managed Servers
■
Section 8.10, Starting the Oracle IPM System
■
Section 8.11, Configuring System MBeans for Oracle IPM
■
Section 8.12, Enabling Oracle IPM in Oracle UCM
■
Section 8.13, Adding the Oracle IPM Server Listen Addresses to the List of Allowed Hosts in Oracle UCM
■
Section 8.14, Creating a Connection to UCM System
■
Section 8.15, Configuring BPEL CSF Credentials
■
Section 8.16, Configuring a Workflow Connection
■
Section 8.17, Configuring Oracle HTTP Server for the WLS_IPM Managed Servers
■
Section 8.18, Setting the Frontend HTTP Host and Port
■
Section 8.19, Validating Access Through Oracle HTTP Server
■
Section 8.20, Configuring Node Manager for the WLS_IPM Managed Servers
■
Section 8.21, Configuring Server Migration for the WLS_IPM Managed Servers
■
Section 8.22, Backing Up the Installation
8-2 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite
8.1 About Adding Oracle IPM to a Domain
