8-16 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite
8.19 Validating Access Through Oracle HTTP Server
Verify URLs to ensure that appropriate routing and failover is working from the HTTP Server to the IPM_Cluster. Perform these steps to verify the URLs:
1.
While WLS_IPM2 is running, stop WLS_IPM1 using the Oracle WebLogic Server Administration Console.
2.
Access http:WEBHOST1:7777imaging to verify it is functioning properly. Please note that you will not be able to retrieve reports or data since the IPM
server is down.
3.
Start WLS_IPM1 from the Oracle WebLogic Server Administration Console.
4.
Stop WLS_IPM2 from the Oracle WebLogic Server Administration Console.
5.
Access http:WEBHOST1:7777imaging to verify it is functioning properly.
6.
Start WLS_IPM2 from the Oracle WebLogic Server Administration Console.
8.20 Configuring Node Manager for the WLS_IPM Managed Servers
It is assumed that the host names used by the WLS_IPM managed servers as listen address have already been configured for host name verification as explained in
Section 7.12, Configuring Node Manager for the WLS_UCM and WLS_IPM Managed Servers.
At this point, once the WLS servers have been added to the domain, the procedure in Section 9.3.5, Configuring Managed WLS Servers to Use the Custom Keystores
should be performed so that the servers are configured to use custom key stores.
8.21 Configuring Server Migration for the WLS_IPM Managed Servers
Server migration is required for proper failover of the Oracle IPM components in the event of failure in any of the ECMHOST1 and ECMHOST2 nodes. See
Chapter 10, Configuring Server Migration
for further details. For Oracle IPM, use the following values for the variables in that chapter:
Note: When HTTPS is enabled in the load balancer and the load
balancer terminates SSL the SOA servers receive only HTTP requests, not HTTPS, as suggested in this guide, the endpoint protocol for
webservices is set to http. Since the load balancer redirects HTTP to HTTPS, this causes the following exception when testing web services
functionality in Oracle Enterprise Manager Fusion Middleware Control:
javax.xml.soap.SOAPException: oracle.j2ee.ws.saaj.ContentTypeException
To resolve this exception, update the URL endpoint:
In the Enterprise Manager Test Page, check Edit Endpoint URL.
Within the endpoint URL page:
■
Change http to https.
■
Change the default port number say 80 to SSL port say 443.
Extending the Domain with Oracle IPM 8-17
■
Server names:
– WLS_SERVER1: WLS_IPM1
– WLS_SERVER2: WLS_IPM2
■
Host names:
– HOST1: ECMHOST1
– HOST2: ECMHOST2
■
Cluster name:
– CLUSTER: IPM_Cluster
8.22 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.
8-18 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite
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
9
Setting Up Node Manager 9-1
9
Setting Up Node Manager
This chapter describes how to configure Node Manager in accordance with the EDG recommendations. It contains the following sections:
■
Section 9.1, About Setting Up Node Manager
