Oracle® Fusion Applications Enterprise Deployment Guide for Financials 11g Release 7 (11.1.7) Part Number E27364-10 |
|
|
PDF · Mobi · ePub |
This chapter describes how to scale out the Oracle Fusion Projects domain.
This chapter includes the following topics:
Section 14.1, "Overview of the Oracle Fusion Procurement Domain"
Section 14.2, "Prerequisites for Scaling Out the Oracle Fusion Procurement Domain"
Section 14.3, "Adding a New Machine in the Oracle WebLogic Server Console"
Section 14.4, "Packing and Unpacking the Managed Server Domain Home"
Section 14.5, "Cloning Managed Servers and Assigning Them to FINHOST2"
Section 14.7, "Configuring Server Migration for the Managed Servers"
The Oracle Fusion Procurement domain supports the following products:
Oracle Fusion Procurement Contracts
Oracle Fusion Purchasing
Oracle Fusion Self Service Procurement
Oracle Fusion Sourcing
Oracle Fusion Supplier Model
Oracle Fusion Supplier Portal
Oracle Fusion Procurement integrates with the Oracle Business Intelligence domain for both embedded and PDF reports used by the Procurement and Supplier Portal applications.
Figure 2-8 in Chapter 2, "Introduction to the Enterprise Deployment Reference Topologies," shows the topology for the Oracle Fusion Procurement domain within the overall reference enterprise deployment topology.
Before you begin, ensure that Node Manager has been started in the Secure Sockets Layer (SSL) mode by following the instructions in Chapter 7, "Setting Up Node Manager for an Enterprise Deployment."
To add a new machine:
Log in to the Administration Server: http://
prcinternal
.mycompany.com:7777/console
.
Navigate to ProcurementDomain > Environment > Machines.
LocalMachine is located in the right-hand pane.
In the left-hand pane, click Lock & Edit.
In the right-hand pane, first click New to add the remote machine, and then specify the following:
Name - enter FINHOST2
Machine operating system - Unix
Click Next.
In the window that opens, set the following attributes:
Type - SSL
Listen Address - <FINHOST2
>
Note:
The "localhost" default value here is wrong.
Listen port - 5556
Click Finish and activate the changes.
Since the FINHOST1
domain directory file system is also available from FINHOST2
, both the pack
and unpack
commands can be executed from the FINHOST2
.
To pack and unpack the Managed Server domain home:
Change directory to ORACLE_BASE
/products/fusionapps/oracle_common/common/bin
.
Run the pack
command:
FINHOST2> ./pack.sh -managed=true -domain=ORACLE_BASE/config/domains/ FINHOST1/ProcurementDomain -template=ORACLE_BASE/user_templates/ ProcurementDomain_managed.jar -template_name= "Procurement_Managed_Server_Domain"
Ensure that /u02/local/oracle/config/domains/
FINHOST2
/ProcurementDomain
is empty, and then run the unpack
command:
FINHOST2> ./unpack.sh -domain=/u02/local/oracle/config/domains/FINHOST2/ ProcurementDomain -template=ORACLE_BASE/user_templates/ ProcurementDomain_managed.jar
Here, ORACLE_BASE
is shared, and /u02/local
is local to FINHOST2
.
To add a Managed Server and assign it to FINHOST2
:
Log in to the Administration Server: http://
prcinternal
.mycompany.com:7777/console
.
Navigate to ProcurementDomain > Environment > Servers.
Switch to Lock & Edit mode.
Select the Managed_Servers checkbox (for example, ProcurementServer_1) and then click Clone.
Specify the following Server Identity attributes:
Server Name - ProcurementServer_2
Note:
To ensure consistency in naming, copy the name of the server shown in Server Identity and paste it into the Server Name field. Then change the number to "_2".
Server Listen Address - <FINHOST2
>
Server Listen Port - leave "as is"
Click OK.
You now should see the newly cloned server, ProcurementServer_2
.
Click ProcurementServer_2 and change the following attributes:
Machine - <FINHOST2
>
Cluster Name - accept the default, ProcurementCluster
Note:
Ensure that this cluster name is the same as the cluster name of the original Managed Server.
Click Save and then Activate Changes.
Navigate to ProcurementDomain > Environment > Servers.
From the Name column, click the ProcurementServer_2 scaled-out server link.
Click Lock & Edit, and then select the Configuration tab.
Select the Keystores tab, and ensure that the keystores value is Custom Identity and Custom Trust.
Do the following:
Change the Custom Identity Keystore path to point to the ORACLE_BASE
/config/keystores/
FINHOST2
_fusion_identity.jks
file.
Leave the Custom Identity Keystore type blank.
Change the Custom Identity Keystore Passphrase entry. This should be the same as the keystorepassword field described in the first bullet in Step 4 in Section 7.3, "Creating the Identity Keystore on FINHOST2."
Re-enter the Confirm Custom Identity Keystore Passphrase.
Ensure that the Confirm Custom Trust Keystore path is pointing to the ORACLE_BASE
/config/keystores/fusion_trust.jks
file.
Leave the Custom Trust Keystore type blank.
Change the Custom Trust Keystore Passphrase entry. This should be the same as the keystorepassword field described in the first bullet in Step 4 in Section 7.3, "Creating the Identity Keystore on FINHOST2."
Re-enter the Custom Trust Keystore Passphrase.
Click Save.
Select the SSL tab.
Make sure that Identity and Trust Locations is set to Keystores.
Change the Private Key Alias to FINHOST2
_fusion
.
Change the Private Key Passphrase to the keypassword, as described in the second bullet in Step 4 in Section 7.3, "Creating the Identity Keystore on FINHOST2."
Re-enter the keypassword from Step c for the Confirm Private Key Passphrase.
Click Save.
Select the Server Start tab.
Change the Arguments to reflect the name of your cloned Managed Server and make sure the server group is the correct cluster name. For example, you should see the following:
-DJDBCProgramName=DS/ProcurementDomain/ProcurementServer_2 -Dserver.group=ProcurementCluster
Click Save.
Select the Logging tab, and then select the HTTP tab.
Do the following:
Change the Log file name to logs/access.log.%yyyyMMdd%
.
Change the rotation type to By Time.
Leave the Limit number of retained files option unchecked.
Leave the Rotate log file on startup option unchecked.
Click Save.
Expand Advanced.
Change the format to Extended.
Change the extended logging format fields to the following:
date time time-taken cs-method cs-uri sc-status sc(X-ORACLE-DMS-ECID) cs(ECID-Context) cs(Proxy-Remote-User) cs(Proxy-Client-IP)
Click Save.
Click Activate Changes.
Repeat Steps 2 to 18 for all the Managed Servers on this domain.
Stop the domain's Administration Server:
FINHOST1> ORACLE_BASE/config/domains/FINHOST1/ ProcurementDomain/bin/stopWebLogic.sh
Set the following environment variable on FINHOST2
:
export WLST_PROPERTIES="-Dweblogic.security.SSL.trustedCAKeyStore=ORACLE_BASE/
config/keystores/fusion_trust.jks"
Start the domain's Administration Server:
FINHOST2> ORACLE_BASE/products/fusionapps/wlserver_10.3/common/bin/wlst.sh FINHOST2> nmConnect(username='<username>', password='<password>', domainName='ProcurementDomain', host='FINHOST1',port='5556', nmType='ssl', domainDir='ORACLE_BASE/config/domains/FINHOST1/ProcurementDomain') FINHOST2> nmStart('AdminServer') FINHOST2> exit ()
Note:
The username and password used in the nmConnect
are the Node Manager credentials (username and password) specified when creating the provisioning response file. This is shown in Figure 5-3 in "Using the Provisioning Process to Install Components for an Enterprise Deployment".
Run the newly created Managed Servers:
Log in to the Administration Server: http://
prcinternal
.mycompany.com:7777/console
.
Navigate to ProcurementDomain > Environment > Servers > Control.
Select the newly created Managed Servers and click Start.
Navigate to ProcurementDomain > Environment > Servers and check the State to verify that the newly created Managed Servers are running.
To configure Oracle HTTP Server:
Do the following: :
On WEBHOST1
, change directory to ORACLE_BASE
/config/CommonDomain_webtier/config/OHS/ohs1/moduleconf
On WEBHOST2
, change directory to ORACLE_BASE
/config/CommonDomain_webtier1/config/OHS/ohs2/moduleconf
Copy FusionVirtualHost_prc.conf
to FusionVirtualHost_prc.conf.org
.
Edit the FusionVirtualHost_prc.conf
and FusionVirtualHost_prc.supplierportal.conf
files, adding the scaled-out host and port to all the WebLogic Application Clusters. Add this to both the Internal and External part of the FusionVirtualHost_prc.conf
file. Example 14-1 shows sample code for ProcurementServer.
Notes:
Do not add these values for Oracle Enterprise Manager, Oracle WebLogic Server Administration Console, or Oracle Authorization Policy Manager.
If the Managed Servers are running on VIPs, replace FINHOST1
and FINHOST2
with the VIP addresses in Example 14-1.
Repeat Step 3 for all applications.
Do the following to restart Oracle HTTP Server:
On WEBHOST1
:
Change directory to ORACLE_BASE
/config/CommonDomain_webtier/bin
Enter the following:
WEBHOST1> ./opmnctl stopall WEBHOST1> ./opmnctl startall
On WEBHOST2
:
Change directory to ORACLE_BASE
/config/CommonDomain_webtier1/bin
Enter the following:
WEBHOST2> ./opmnctl stopall WEBHOST2> ./opmnctl startall
Server migration is required for proper failover of Oracle Fusion Procurement components in the event of failure in any of the FINHOST1
and FINHOST2
nodes. For more information, see Chapter 18, "Setting Up Server Migration for an Enterprise Deployment."
You should verify URLs to ensure that the appropriate routing and failover are working.
To verify the URLs:
Log in to the ProcurementDomain
Oracle WebLogic Server Administration Console and stop all the Managed Servers on the FINHOST1
while the Managed Servers on FINHOST2
are running.
Access the following URLs to verify that routing and failover are functioning properly. (Ensure the log in prompt is visible.)
https://prcexternal.mycompany.com/procurement/faces/PrcPoPurchasingWorkarea
https://prcexternal.mycompany.com/supplierPortal/faces/PrcPosSupplierPortalWorkarea
Log in to the ProcurementDomain
Oracle WebLogic Server Administration Console and stop all the Managed Servers on FINHOST2
.
Start the Managed Servers on FINHOST1
.
Repeat Step 2. (Ensure the log in prompt is visible.)
Start all the Managed Servers on FINHOST2
and verify that they are running on FINHOST1
and FINHOST2
.