4-22 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter
3.
Update routing tables through arping, for example:
SOAHOST2 sbinarping -b -A -c 3 -I eth0 10.0.0.1 4.
Start the Administration Server on SOAHOST2 using the procedure in Section 4.7,
Starting the Administration Server on SOAHOST1. .
5.
Test that you can access the Administration Server on SOAHOST2 as follows:
a.
Ensure that you can access the Oracle WebLogic Server Administration Console at http:ADMINVHN:7001console.
b.
Check that you can access and verify the status of components in the Oracle Enterprise Manager at http:ADMINVHN:7001em.
4.23 Validating Access to SOAHOST2 Through Oracle HTTP Server
Perform the same steps as in Section 4.21, Validating Access Through Oracle HTTP
Server . This is to check that you can access the Administration Server when it is
running on SOAHOST2.
4.24 Failing the Administration Server Back to SOAHOST1
This step checks that you can fail back the Administration Server, that is, stop it on SOAHOST2 and run it on SOAHOST1. To do this, migrate ADMINVHN back to
SOAHOST1 node as follows:
1.
Stop the Administration Server.
2.
Run the following command on SOAHOST2.
SOAHOST2 sbinifconfig ethZ:N down 3.
Run the following command on SOAHOST1:
SOAHOST1 sbinifconfig ethX:Y 100.200.140.206 netmask 255.255.255.0
4.
Update routing tables through arping. Run the following command from SOAHOST1.
SOAHOST1 sbinarping -b -A -c 3 -I ethZ 100.200.140.206 5.
Start the Administration Server again on SOAHOST1 using the procedure in Section 4.7, Starting the Administration Server on SOAHOST1.
.
SOAHOST1 cd ORACLE_BASEadmindomain_nameaserverdomain_namebin Note:
The Administration Server does not use Node Manager for failing over. After a manual failover, the machine name that appears in
the Current Machine field in the Administration Console for the server is SOAHOST1, and not the failover machine, SOAHOST2. Since
Node Manager does not monitor the Administration Server, the machine name that appears in the Current Machine field, is not
relevant and you can ignored it.
Note: Ensure that the netmask and interface to be used match the
available network configuration in SOAHOST1
Creating a Domain 4-23
SOAHOST1 .startWebLogic.sh 6.
Test that you can access the Oracle WebLogic Server Administration Console at http:ADMINVHN:7001console.
7.
Check that you can access and verify the status of components in the Oracle Enterprise Manager at http:ADMINVHN:7001em.
4.25 Backing Up the Installation
Perform a backup to save your domain configuration make sure that you stop the server first. The configuration files all exist under the ORACLE_
BASEadmindomain_name directory.
SOAHOST1 tar -cvpf edgdomainback.tar ORACLE_BASEadmindomain_name Back up the Instance Home on the web tier using the following command:
tar -cvpf BACKUP_LOCATIONweb_instance_name.tar ORACLE_INSTANCE
4-24 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter
5
Extending the Domain for SOA Components 5-1
5
Extending the Domain for SOA Components
This chapter describes how to use the Configuration Wizard to extend the domain to include SOA components. You created in the domain in
Chapter 4, Creating a Domain.
This chapter contains the following sections:
■
Section 5.1, Installing Oracle Fusion Middleware for SOA Home
■
Section 5.2, Enabling VIP2 on SOAHOST1 and VIP3 on SOAHOST2
■
Section 5.3, Extending the Domain for SOA Components
■
Section 5.4, Restarting the Administration Server
■
Section 5.5, Configuring Oracle Coherence for Deploying Composites
■
Section 5.6, Setting Connection Destination Identifiers for B2B Queues
■
Section 5.7, Disabling Host Name Verification for the WLS_SOAn Managed Server
■
Section 5.8, Restarting the Node Manager on SOAHOST1
■
Section 5.9, Propagating the Domain Changes to the Managed Server Domain Directory
■
Section 5.10, Starting the WLS_SOA1 Managed Server on SOAHOST1
■
Section 5.11, Validating the WLS_SOA1 Managed Server
■
Section 5.12, Propagating the Domain Configuration to SOAHOST2 Using the unpack Utility
■
Section 5.13, Restarting Node Manager on SOAHOST2
■
Section 5.14, Starting and Validating the WLS_SOA2 Managed Server
Important: Oracle strongly recommends that you read the release
notes for any additional installation and deployment considerations prior to starting the setup process.
Note: Follow the steps in this chapter only if you want to run SOA
components on SOAHOST1 and SOAHOST2. If you do not want to run SOA components in your WebCenter topology, you can skip this
chapter.
5-2 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter
■
Section 5.15, Configuring Oracle HTTP Server for the WLS_SOAn Managed Servers
■
Section 5.16, Validating Access Through Oracle HTTP Server
■
Section 5.17, Setting the Frontend HTTP Host and Port
■
Section 5.18, Setting the WLS Cluster address for Direct BindingRMI invocations to composites
■
Section 5.19, Configuring a Shared JMS Persistence Store
■
Section 5.20, Configuring a Default Persistence Store for Transaction Recovery
■
Section 5.21, Enabling High Availability for Oracle File and FTP Adapters
■
Section 5.22, Scaling the Oracle Database Adapter
■
Section 5.23, Backing Up the Installation
5.1 Installing Oracle Fusion Middleware for SOA Home
