|Oracle® Fusion Applications Enterprise Deployment Guide
11g Release 1 (220.127.116.11)
Part Number E16684-02
This chapter describes how to scale out the Oracle Fusion Common domain.
This chapter includes the following topics:
The Oracle Fusion Common domain is shared by all Oracle Fusion Applications product families. Oracle Fusion Customer Relationship Management implementation is dependent on the Oracle Fusion Common domain for the following components:
Oracle Fusion Functional Setup Manager, for all setup task flows
Help Portal, for centralized help
Home page application, which has the Oracle Fusion Customer Relationship Management home page and launch pad
Oracle Universal Content Management (Oracle UCM), to store all marketing collateral as well as all attachments. Import flow also uses Oracle UCM to stage the CSV files that theuser uploads
Oracle Secure Enterprise Search
Oracle WebCenter Community Space and forums
Oracle WebLogic Communication Services (OWLCS) and Oracle WebLogic SIP Server
Figure 8-1 shows the Oracle Fusion Common domain within the overall reference enterprise deployment topology for Oracle Fusion Applications.
Before you begin, ensure the following:
Node Manager has been started in the Secure Sockets Layer (SSL) mode by following the instructions in Chapter 6, "Configuring Node Manager"
You are starting with a clean machine if it is the first time it is being used for a scale out
/etc/hosts file has proper entries. To verify, ping this machine with the fully qualified name of the machine
The user created on
CRMHOST2 should the same as the user on
The directory structure
/u01/oracle is mounted to same shared file system as
The directory structure
CRMHOST2 has been created
The initial Oracle Fusion Customer Relationship Management deployment on
CRMHOST1 has already been done and verified by provisioning
To add a new machine:
Log in to the Administration Server:
Navigate to CommonDomain > 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
Machine operating system - Unix
In the window that opens, set the following attributes:
Type - SSL
Listen Address - <
Note:The "localhost" default value here is wrong.
Listen port - 5556
Click Finish and activate the changes.
Note:If you get an error when activating the changes, see Section 18.8.18, "Administration Console Redirects from Internal URL to Container URL after Activation" for the temporary solution.
Scaling out Oracle UCM involves two tasks:
Do the following prior to performing the steps in Section 8.5, "Packing and Unpacking the Managed Server Domain Home":
/CommonDomain/ucm/cs directory from the local to the shared location:
/config/domains/CRMHOST1/CommonDomain/ucm/cs/bin/intradoc.cfg file, create the variables
weblayoutDir so that they point to the shared location,
You also must scale out the Oracle UCM Inbound Refinery server.
CRMHOST1must already be on the local disk.
Do the following after performing the steps in Section 8.5, "Packing and Unpacking the Managed Server Domain Home" and Section 8.6, "Cloning Managed Servers and Assigning Them to CRMHOST2":
/u02/local/oracle/config/domains/CRMHOST1/CommonDomain/ucm/ibr/config/config.cfg file on
CRMHOST1 with the following:
IDC_Name=CRMHOST1usoraclecom7012 (In this instance,
CRMHOST1 is not the fully qualified name.)
SocketHostAddressSecurityFilter=127.0.0.1|cluster node's addresses|
IP ADDRESS|0.0.0.0.0.0.0.1 (Include the cluster node's addresses.)
CRMHOST1's server address instead of load balancer, as it is a singleton node.)
ibr) and log in when prompted.
The post-installation configuration page displays, as it is not a clustered node.
On the post-installation configuration page:
intradoc server port to 7035.
Ensure the port has both a unique IDC_Name and unique local paths on
Set the Incoming Socket Connection Address Security Filter:
SocketHostAddressSecurityFilter=127.0.0.1| cluster node's addresses|CRMHOST1 IP ADDRESS|CRMHOST2 IP ADDRESS|0.0.0.0.0.0.0.1
http://CRMHOST1:7012/cs and select Administration > providers.
ibrprovider is already defined in this list.
Add a new outgoing provider:
Set the values to match the values of ibrprovider.
Set the HTTP host name to be second host address's
CRMHOST2 IP address.
Navigate to Inbound Refinery on second node:
Select Conversion Settings and update the primary web rendition.
Navigate to the third-party application's Settings > General OutsideIn Filter Options > Options, and set the following path to the fonts:
Note:The font location can be specific to the operating system.
COMMONUCMVH1 TCP VIP on the load-balancing router (LBR) with
:7012 as its members.
After scaling out the Oracle WebCenter managed server, do the following:
Log in to:
Navigate to WebCenter > WebCenter_managedserver > WebCenter (top left of right pane ) > Content repository > Oracle Content Server > Edit > RIDC Socket type (in Connection details).
Select Socket and enter
COMMONUCMVH1 as the host.
Restart the Oracle WebCenter managed servers.
CRMHOST1 domain directory file system is also available from
unpack commands can be executed from
Do the following:
Change directory to
CRMHOST2> ./pack.sh -managed=true -domain=ORACLE_BASE/config/domains/ CRMHOST1/CommonDomain -template=ORACLE_BASE/user_templates/ CommonDomain_managed.jar -template_name="Common_Managed_Server_Domain"
/CommonDomain is empty, and then run the
CRMHOST2> ./unpack.sh -domain=/u02/local/oracle/config/domains/CRMHOST2/ CommonDomain -template=ORACLE_BASE/user_templates/CommonDomain_managed.jar
ORACLE_BASE is shared, and
/u02/local is local to
To add a managed server and assign it to
Log in to the Administration Server:
Navigate to CommonDomain > Environment > Servers.
Switch to Lock & Edit mode.
Select the Managed_Servers checkbox (for example, HomePageServer_1) and then click Clone.
Specify the following Server Identity attributes:
Server Name -
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 - <
Server Listen Port - leave "as is"
You now should see the newly cloned sales server,
Click HomePageServer_2 and change the following attributes:
Machine - <
Cluster Name - Default, HomePageCluster
Click Save and then Activate Changes.
From the Name column, click the HomepageServer_2 scaled-out server link.
Click Lock & Edit, and then choose the Keystores tab.
Ensure that the keystores value is Custom Identity and Custom Trust.
Do the following:
Change the Custom Identity Keystore path to point to the
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 6.2, "Creating the Identity Keystore on CRMHOST2."
Re-enter the Confirm Custom Identity Keystore Passphrase.
Ensure that the Confirm Custom Trust Keystore path is pointing to the
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 6.2, "Creating the Identity Keystore on CRMHOST2."
Re-enter the Custom Trust Keystore Passphrase.
Choose the SSL tab.
Make sure that Identity and Trust Locations is set to Keystores.
Change the Private Key Alias to
Change the Private Key Passphrase to the keypassword, as described in the second bullet in Step 4 in Section 6.2, "Creating the Identity Keystore on CRMHOST2."
Re-enter the keypassword from Step c for the Confirm Private Key Passphrase.
Click Activate Changes.
Set the following environment variable:
Stop the domain's Administration Server:
Restart the domain's Administration Server:
CRMHOST2> ORACLE_BASE/products/fusionapps/wlserver_10.3/common/bin/wlst.sh CRMHOST2> nmConnect(username='<username>', password='<password>', domainName='CommonDomain', host='CRMHOST1',port='5556', nmType='ssl', domainDir='ORACLE_BASE/config/domains/CRMHOST1/CommonDomain') CRMHOST2> nmStart('AdminServer')
Note:The username and password used in the
nmConnectare the Node Manager credentials (username and password) specified when creating the provisioning plan. This is shown in Figure 4-3 in "Using the Provisioning Process to Install Components for an Enterprise Deployment".
wlcs_sipstate2 scaled-out server only, do the following:
Change directory to:
datatier.xml file, after the following line:
Run the newly created managed server:
Navigate to CommonDomain > Environment > Servers > Control.
Select the newly created managed server and click Start.
Navigate to CommonDomain > Environment > Servers and check the State to verify that the newly created managed servers are running.
Log in to the Administration Server once again (
.mycompany.com:7777/console) and verify that all the managed servers, including scaled-out servers, are running.
Note:For all the scaled-up and scaled-out servers, change the Arguments in the
/data/nodemanager/startup.propertiesfile to the following:
Note:For all the scaled-up and scaled-out managed servers, do the following:
Access the Oracle WebLogic Server Administration Console for the CommonDomain:
Navigate to Environment > Servers and click the "Managed Server" link.
First select the Logging tab and then the HTTP tab.
Update the following parameters:
– Log file name: logs/access.log.%yyyyMMdd%
– Rotation Type: By Time
– Limit number of retained files: leave this option unchecked
– Rotate log file on startup: leave this option unchecked
Expand Advanced Node and set the following:
– Format: Extended
– Extended Logging Format Fields:
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 and Activate Changes.
Restart the Managed Server for the changes to take affect.
To configure Oracle HTTP Server:
Change directory to
FusionVirtualHost_fs.conf file, adding the scaled-out host and port to all the WebLogic Application Clusters. Example 8-1 shows sample code for HomePageServer.
Repeat Step 2 for all applications.
Restart Oracle HTTP Server:
/config/CommonDomain_webtier/bin and enter the following:
WEBHOST1> ./opmnctl stopall WEBHOST1> ./opmnctl startall
You should verify URLs to ensure that the appropriate routing and failover are working.
To verify the URLs:
Log in to the
CommonDomain Oracle WebLogic Server Administration Console and stop all the managed servers on the
CRMHOST1 while the managed servers on
CRMHOST2 are running.
Access the following URLs to verify that routing and failover are functioning properly. (Ensure the log in prompt is visible.)
Log in to the
CommonDomain Oracle WebLogic Server Administration Console and stop all the managed servers on
Start the managed servers on
Repeat Step 2. (Ensure the log in prompt is visible.)
Start all the managed servers on
CRMHOST2 and verify that they are running on