| Oracle® Fusion Applications Enterprise Deployment Guide for Financials 11g Release 6 (11.1.6) Part Number E27364-09 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Enterprise Deployment Guide for Financials 11g Release 6 (11.1.6) Part Number E27364-09 |
|
|
PDF · Mobi · ePub |
This chapter describes how to configure and validate the Oracle WebLogic Server Administration Server for high availability.
This chapter includes the following topics:
Section 17.1, "Enabling Administration Server High Availability"
Section 17.4, "Manually Failing Over the Administration Server to FINHOST2"
Section 17.5, "Failing the Administration Server Back to FINHOST1"
The Administration Server is a singleton application, so it cannot be deployed in an active-active configuration. By default, the Administration Server is only available on the first installed node. If this node becomes unavailable, then the Administration Console and Fusion Middleware Control also become unavailable. To avoid this scenario, the Administration Server and the applications deployed to it must be enabled for failover. The enterprise deployment architecture in this guide calls for the deploying the Administration Server on a disk shared between the primary node and the secondary node.
The following domains are deployed as part of the Oracle Fusion Financials enterprise deployment implementation:
Oracle Fusion Customer Relationship Management Domain
Oracle Fusion Common Domain
Oracle Fusion Financials Domain
Oracle Fusion Human Capital Management Domain
Oracle Fusion Supply Chain Management Domain
Oracle Fusion Projects Domain
Oracle Fusion Procurement Domain
Oracle Business Intelligence Domain
The process described in this guide initially deploys each domain-specific Administration Server in shared storage (/u01/oracle) mounted on FINHOST1, and Managed Servers in the local disk (/u02/local/oracle).
This section contains the following topics:
Section 17.1.1, "Enabling Administrative Virtual Host on FINHOST1"
Section 17.1.2, "Adding a New Machine in the Oracle WebLogic Server Console"
Section 17.1.3, "Enabling the Administration Server to Listen on the Virtual IP Address"
Note:
FINADMINVH is used as a generic name in this chapter. For domain-specific administrative virtual host names, see Table 3-1 in Section 3.6, "IPs and Virtual IPs."
The Administration Server must be configured to listen on a virtual IP Address to enable it to seamlessly failover from one host to another. In case of a failure, the Administration Server, along with the virtual IP Address, can be migrated from one host to another.
However, before the Administration Server can be configured to listen on a virtual IP Address, one of the network interface cards on the host running the Administration Server must be configured to listen on this virtual IP Address. The steps to enable a virtual IP Address are completely dependent on the operating system.
To enable a virtual IP Address on FINHOST1:
Note:
In a UNIX environment, the command must be run as the root user.
On FINHOST1, run the ifconfig command to get the value of the netmask. In a UNIX environment, run this command as the root user. For example:
[root@FINHOST1 ~] # /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:43:D7:5B:06
inet addr:139.185.140.51 Bcast:139.185.140.255 Mask:255.255.255.0
inet6 addr: fe80::211:43ff:fed7:5b06/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10626133 errors:0 dropped:0 overruns:0 frame:0
TX packets:10951629 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4036851474 (3.7 GiB) TX bytes:2770209798 (2.5 GiB)
Base address:0xecc0 Memory:dfae0000-dfb00000
On FINHOST1, bind the virtual IP Address to the network interface card using ifconfig. In a UNIX environment, run this command as the root user. Use a netmask value that was obtained in Step 1.
The syntax and usage for the ifconfig command is as follows:
/sbin/ifconfig networkCardInterface Virtual_IP_Address netmask netMask
For example:
/sbin/ifconfig eth0:1 100.200.140.206 netmask 255.255.255.0
Update the routing table using arping. In a UNIX environment, run this command as the root user.
/sbin/arping -q -U -c 3 -I networkCardInterface Virtual_IP_Address
For example:
/sbin/arping -q -U -c 3 -I eth0 100.200.140.206
Validate that the address is available by pinging it from another node. For example:
/bin/ping 100.200.140.206
Create a new machine and assign the Administration Server to the new machine using the Administration Console:
Log in to the Administration Console.
In the Change Center, click Lock & Edit.
In the Environment section of the Home page, click Machines.
On the Summary of Machines page, select the machine that is associated with the Administration Server from under the Machines table and click Clone. For example: FINHOST1.MYCOMPANY.COM.
On the Clone a Machine page, enter the name of the machine under the Machine Identity section and click OK. For example, enter ADMINHOST as the machine name.
On the Summary of Machines page, click the newly created machine link.
On the Settings page for the ADMINHOST machine, select the Servers tab.
Click Add under the Servers table.
On the Add a Server to Machine page, select Select an existing server, and associate it with this machine option.
Choose the AdminServer from the dropdown list.
Click Finish to associate the Administration Server with the machine.
In the Change Center, click Activate Changes.
Ensure that you have performed the steps described in Section 17.1.1, "Enabling Administrative Virtual Host on FINHOST1"before setting the Administration Server listen address.
To set the Administration Server listen address:
Log in to the Administration Console.
In the Change Center, click Lock & Edit.
Expand the Environment node in the Domain Structure window.
Click Servers. The Summary of Servers page is displayed.
Select AdminServer(admin) in the table. The Settings page for AdminServer(admin) is displayed.
Set the Listen Address to FINADMINVH (domain-specific administrative virtual host).
Click Save.
Click Activate Changes.
The changes will not take effect until the Administration Server is restarted. Follow these steps to restart the Administration Server:
In the Summary of Servers page, select the Control tab.
Select AdminServer(admin) in the table and then click Shutdown.
Set the following environment variable:
WLST_PROPERTIES="-Dweblogic.security.SSL.trustedCAKeyStore=ORACLE_ BASE/config/keystores/fusion_trust.jks"
Start the Administration Server again from the command line. Use the nmconnect username and password you specified in the Installation Location Screen in Chapter 5.
FINHOST1> ORACLE_BASE/products/fusionapps/wlserver_10.3/common/bin/wlst.sh FINHOST1> nmConnect(username='username', password='password', domainName='domain_name', host='FINADMINVH',port='5556', nmType='ssl', domainDir='ORACLE_BASE/config/domains/FINHOST1/domain_name') FINHOST1> nmStart('AdminServer')
To configure Oracle HTTP Server:
On WEBHOST1:
cd ORACLE_BASE/config/CommonDomain_webtier/config/OHS/ohs1/moduleconf.
Edit the domain-specific virtual host config file. For example:
cp FusionVirtualHost_fin.conf FusionVirtualHost_fin.conf.org
Edit the FusionVirtualHost_fin.conf file, adding the Administrative virtual host and port. Example 17-1 shows sample code.
Note:
Replace FINADMINVH and port with domain-specific Administrative virtual host and port number.
Example 17-1 Add AdministrativeVirtual Host and Port
## Context roots for application em
<Location /em>
SetHandler weblogic-handler
WebLogicCluster FINADMINVH:port
</Location>
## Context roots for application console
<Location /console >
SetHandler weblogic-handler
WebLogicCluster FINADMINVH:port
</Location>
Restart Oracle HTTP Server: cd to ORACLE_BASE/config/CommonDomain_webtier/bin and enter the following:
WEBHOST1> ./opmnctl stopall WEBHOST1> ./opmnctl startall
Perform these steps to ensure that the Administration Server and Oracle Enterprise Manager Fusion Middleware Control are properly configured:
Ensure that you can access the domain-specific Oracle WebLogic Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control. For example, for the Oracle Fusion Financials domain:
http://fininternal.mycompany.com:7777/console
http://fininternal.mycompany.com:7777/em
After completing the steps in Section 17.1 and Section 17.2 for other domains, repeat Step 1 for other domains by replacing the domain-specific URL.
Do the following:
Log into Oracle Fusion Functional Setup Manager as a super user. The user should have the Oracle WebLogic Server Administrator role, for example, "FAadmin". Functional Setup Manager is located here:
https://commonexternal.mycompany.com/setup/faces/TaskListManagerTop
Select Register Domains in the left-hand task pane.
On the Register Domains page, select the domain to be updated and click Edit.
Do the following:
– Replace ADMIN_HOST (the default value) with FINADMINVH wherever it appears.
– Update the value of Enterprise Manager Protocol to https.
– Ensure the value of Enterprise Manager Port is 5556.
Click Save and Close.
Replace the value of TAXONOMY_URL in the fusion_env.properties, fusion_prov.properties, and atgpf_env.properties files located in ORACLE_BASE/config/fapatch with FINADMINVH if the Administration Server's listen address is updated with the virtual IP (VIP) for CommonDomain.
Do the following:
Connect to the Oracle Fusion Applications database as the user fusion.
Run the following commands for each domain for which the Administration Server's listen address is configured with a VIP:
update ASK_DEPLOYED_DOMAINS set NODE_MANAGER_PROTOCOL='ssl' where DEPLOYED_DOMAIN_NAME='domain_name';
The changes will not take effect until the Administration Server is restarted. Follow these steps to restart the Administration Server:
In the Summary of Servers page, select the Control tab.
Select AdminServer(admin) in the table and then click Shutdown.
Set the following environment variable:
WLST_PROPERTIES="-Dweblogic.security.SSL.trustedCAKeyStore=ORACLE_ BASE/config/keystores/fusion_trust.jks"
Start the Administration Server again from the command line. Use the nmconnect username and password you specified in the Installation Location Screen in Chapter 5.
FINHOST1> ORACLE_BASE/products/fusionapps/wlserver_10.3/common/bin/wlst.sh FINHOST1> nmConnect(username='username', password='password', domainName='domain_name', host='FINADMINVH',port='5556', nmType='ssl', domainDir='ORACLE_BASE/config/domains/FINHOST1/domain_name') FINHOST1> nmStart('AdminServer')
Restart the Managed Servers:
Log in to the Oracle WebLogic Server Administration Console (http://crminternal.mycompany.com:7777/console).
Navigate to CRMDomain > Environment > Servers > Control.
Select all the Managed Servers and click Stop.
After all the servers have shut down, select all the servers in the table and then click Start.
In case a node fails, you can fail over the Administration Server to another node. This section describes how to fail over the Administration Server from FINHOST1 to FINHOST2.
Ensure the following:
The Administration Server is configured to listen on a domain-specific administrative virtual host, and not on any address
When failover happens, the Administration Server is failed over from FINHOST1 to FINHOST2 and the two nodes have the following IPs:
FINHOST1 to : 100.200.140.165
FINHOST2: 100.200.140.205
FINADMINVH: 100.200.140.206. This is the VIP where the domain-specific Administration Server is running, assigned to ethX:Y, available in FINHOST1 to and FINHOST2.
The domain directory where the Administration Server is running on FINHOST1 to is on shared storage and is mounted from FINHOST2
The following procedure explains how to fail over the Administration Server to a different node (FINHOST2) with the Administration Server still using the same Oracle WebLogic Server machine. (This machine is a logical machine, not a physical one.)
To fail over the Administration Server:
Stop the Administration Server.
Migrate the IP to the second node:
Run the following command as root on FINHOST1 to (where X:Y is the current interface used by FINADMINVH):
FINHOST1> /sbin/ifconfig ethX:Y down
Run the following command as root on FINHOST2:
FINHOST2> /sbin/ifconfig interface:index IP_Address netmask netmask
For example:
/sbin/ifconfig eth0:1 100.200.140.206 netmask 255.255.255.0
Note:
Ensure that the netmask and interface to be used to match the available network configuration in FINHOST2.
Update the routing tables with arping. For example, run the following command as root:
FINHOST2> /sbin/arping -q -U -c 3 -I eth0 100.200.140.206
Validate that the address is available by pinging it from another node. For example:
/bin/ping 100.200.140.206
Start the Administration Server on FINHOST2 using the procedure in Section 17.1.3.
Test access to the Administration Server on FINHOST2:
Ensure that you can access the domain-specific Oracle WebLogic Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control. For example, for the Oracle Fusion Financials domain, use these URLs:
http://fininternal.mycompany.com:7777/console
http://fininternal.mycompany.com:7777/em
Repeat Step a for other domain by replacing the domain-specific URL.
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 FINHOST1, and not the failover machine, FINHOST2. 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 ignore it.
You also must ensure that you can fail back the Oracle WebLogic Server Administration Server, that is, stop it on FINHOST2 and run it on FINHOST1. To do this, migrate FINADMINVH back to FINHOST1 node.
To migrate FINADMINVH:
Stop the Administration Server on FINHOST2.
Run the following command as root from FINHOST2 to shut down the network stack virtual interface:
FINHOST2> /sbin/ifconfig ethX:Y down
Run the following command as root from FINHOST1 to restart the virtual interface:
FINHOST1> /sbin/ifconfig ethX:Y 100.200.140.206 netmask 255.255.255.0
Note:
Ensure that the netmask and interface to be used match the available network configuration in FINHOST1.
Run the following command from FINHOST1 to update the routing tables through arping:
FINHOST1> /sbin/arping -q -U -c 3 -I eth0 100.200.140.206
Validate that the address is available by pinging it from another node. For example:
/bin/ping 100.200.140.206
Start the Administration Server again on FINHOST1 using the procedure in Step 3 in Section 17.1.3.
Test access to the Administration Server on FINHOST1:
Ensure that you can access the domain-specific Oracle WebLogic Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control. For example, for the Oracle Fusion Financials domain, use these URLs:
http:/fininternal.mycompany.com:7777/console
http:/fininternal.mycompany.com:7777/em
Repeat Step a for other domain by replacing the domain-specific URL.
|
 Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|