8 Scaling Out the Oracle Fusion Common Domain

This chapter describes how to scale out the Oracle Fusion Common domain.

This chapter includes the following topics:

• Section 8.1, "Overview of the Oracle Fusion Common Domain"

• Section 8.2, "Prerequisites for Scaling Out the Oracle Fusion Common Domain"

• Section 8.3, "Adding a New Machine in the Oracle WebLogic Server Console"

• Section 8.4, "Scaling Out Oracle Universal Content Management"

• Section 8.5, "Packing and Unpacking the Managed Server Domain Home"

• Section 8.6, "Cloning Managed Servers and Assigning Them to CRMHOST2"

• Section 8.7, "Oracle HTTP Server Configuration"

• Section 8.8, "Validating the System"

8.1 Overview of the Oracle Fusion Common Domain

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.

Figure 8-1 Reference Topology for Oracle Fusion Common Domain

8.2 Prerequisites for Scaling Out the Oracle Fusion Common Domain

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

• The /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 CRMHOST1

• The directory structure /u01/oracle is mounted to same shared file system as CRMHOST1

• The directory structure /u02/local/oracle/config on CRMHOST2 has been created

• The initial Oracle Fusion Customer Relationship Management deployment on CRMHOST1 has already been done and verified by provisioning

8.3 Adding a New Machine in the Oracle WebLogic Server Console

To add a new machine:

1. Log in to the Administration Server: http://commoninternal.mycompany.com:7777/console.

2. Navigate to CommonDomain > Environment > Machines.

   LocalMachine is located in the right-hand pane.

3. In the left-hand pane, click Lock & Edit.

4. In the right-hand pane, first click New to add the remote machine, and then specify the following:

   • Name - enter CRMHOST2

   • Machine operating system - Unix

5. Click Next.

6. In the window that opens, set the following attributes:

   • Type - SSL

   • Listen Address - <CRMHOST2>

     Note:

     The "localhost" default value here is wrong.

   • Listen port - 5556

7. 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.

8.4 Scaling Out Oracle Universal Content Management

Scaling out Oracle UCM involves two tasks:

• Creating a Common Location for the Oracle UCM Managed Servers

• Scaling Out the Oracle UCM Inbound Refinery Server

8.4.1 Creating a Common Location for the Oracle UCM Managed Servers

Do the following prior to performing the steps in Section 8.5, "Packing and Unpacking the Managed Server Domain Home":

1. Move the CRMHOST1 /u02/local/oracle/config/domains/CRMHOST1/CommonDomain/ucm/cs directory from the local to the shared location: ORACLE_BASE/config/domains/CRMHOST1/CommonDomain/ucm/cs.

2. In the ORACLE_BASE/config/domains/CRMHOST1/CommonDomain/ucm/cs/bin/intradoc.cfg file, create the variables intradocDir, vaultDir, and weblayoutDir so that they point to the shared location, ORACLE_BASE/config/domains/CRMHOST1/CommonDomain/ucm/cs.

8.4.2 Scaling Out the Oracle UCM Inbound Refinery Server

You also must scale out the Oracle UCM Inbound Refinery server.

Note:

/u02/local/oracle/config/domains/CRMHOST1/CommonDomain/ucm/ibr on CRMHOST1 must 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":

1. Edit the /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.)

   • InstanceMenuLabel=CRMHOST1usoraclecom7012

   • SocketHostAddressSecurityFilter=127.0.0.1|cluster node's addresses|CRMHOST1 IP ADDRESS|CRMHOST2 IP ADDRESS|0.0.0.0.0.0.0.1 (Include the cluster node's addresses.)

   • HttpServerAddress=CRMHOST1:7012 (CRMHOST1's server address instead of load balancer, as it is a singleton node.)

2. Start UCM_server2.

3. Navigate to http://CRMHOST2:7012/ibr (CRMHOST2's ibr) and log in when prompted.

   The post-installation configuration page displays, as it is not a clustered node.

4. On the post-installation configuration page:

   1. Set the intradoc server port to 7035.

   2. Ensure the port has both a unique IDC_Name and unique local paths on CRMHOST2.

   3. 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 
      

   4. Click Submit.

5. Navigate to http://CRMHOST1:7012/cs and select Administration > providers.

   ibrprovider is already defined in this list.

6. Add a new outgoing provider:

   1. Click Add.

   2. Set the values to match the values of ibrprovider.

   3. Set the HTTP host name to be second host address's CRMHOST2 IP address.

7. Restart UCM_server1 and UCM_server2.

8. Navigate to Inbound Refinery on second node: http://CRMHOST2:7012/ibr.

9. Select Conversion Settings and update the primary web rendition.

10. Navigate to the third-party application's Settings > General OutsideIn Filter Options > Options, and set the following path to the fonts: /usr/share/X11/fonts/TTF.

    Note:

    The font location can be specific to the operating system.

11. Restart UCM_server2.

12. Create a COMMONUCMVH1 TCP VIP on the load-balancing router (LBR) with CRMHOST1:7012 and CRMHOST2:7012 as its members.

After scaling out the Oracle WebCenter managed server, do the following:

1. Log in to: http://commoninternal.mycompany.com:7777/em.

2. Navigate to WebCenter > WebCenter_managedserver > WebCenter (top left of right pane ) > Content repository > Oracle Content Server > Edit > RIDC Socket type (in Connection details).

3. Select Socket and enter COMMONUCMVH1 as the host.

4. Restart the Oracle WebCenter managed servers.

8.5 Packing and Unpacking the Managed Server Domain Home

Since the CRMHOST1 domain directory file system is also available from CRMHOST2, both pack and unpack commands can be executed from CRMHOST2.

1. Do the following:

   1. Change directory to ORACLE_BASE/products/fusionapps/oracle_common/common/bin.

   2. Run the pack command:

      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" 
      

2. Ensure that /u02/local/oracle/config/domains/CRMHOST2/CommonDomain is empty, and then run the unpack command:

   CRMHOST2> ./unpack.sh -domain=/u02/local/oracle/config/domains/CRMHOST2/
   CommonDomain -template=ORACLE_BASE/user_templates/CommonDomain_managed.jar
   

   Here, ORACLE_BASE is shared, and /u02/local is local to CRMHOST2.

8.6 Cloning Managed Servers and Assigning Them to CRMHOST2

To add a managed server and assign it to CRMHOST2:

1. Log in to the Administration Server: http://commoninternal.mycompany.com:7777/console.

2. Navigate to CommonDomain > Environment > Servers.

3. Switch to Lock & Edit mode.

4. Select the Managed_Servers checkbox (for example, HomePageServer_1) and then click Clone.

5. Specify the following Server Identity attributes:

   • Server Name - HomePageServer_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 - <CRMHOST2>

   • Server Listen Port - leave "as is"

6. Click OK.

   You now should see the newly cloned sales server, HomePageServer_2.

7. Click HomePageServer_2 and change the following attributes:

   • Machine - <CRMHOST2>

   • Cluster Name - Default, HomePageCluster

8. Click Save and then Activate Changes.

9. From the Name column, click the HomepageServer_2 scaled-out server link.

10. Click Lock & Edit, and then choose the Keystores tab.

11. Ensure that the keystores value is Custom Identity and Custom Trust.

12. Do the following:

    1. Change the Custom Identity Keystore path to point to the ORACLE_BASE/products/fusionapps/wlserver_10.3/server/lib/CRMHOST2_fusion_identity.jks file.

    2. Leave the Custom Identity Keystore type blank.

    3. 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."

    4. Re-enter the Confirm Custom Identity Keystore Passphrase.

    5. Ensure that the Confirm Custom Trust Keystore path is pointing to the ORACLE_BASE/products/fusionapps/wlserver_10.3/server/lib/fusion_trust.jks file.

    6. Leave the Custom Trust Keystore type blank.

    7. 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."

    8. Re-enter the Custom Trust Keystore Passphrase.

    9. Click Save.

13. Choose the SSL tab.

    1. Make sure that Identity and Trust Locations is set to Keystores.

    2. Change the Private Key Alias to CRMHOST2_fusion.

    3. 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."

    4. Re-enter the keypassword from Step c for the Confirm Private Key Passphrase.

    5. Click Save.

14. Click Activate Changes.

15. Repeat Steps 2 to 14 for all the managed servers on this domain.

16. Set the following environment variable:

    WLST_PROPERTIES="-Dweblogic.security.SSL.trustedCAKeyStore=ORACLE_BASE/
    products/fusionapps/wlserver_10.3/server/lib/fusion_trust.jks"
    

17. Stop the domain's Administration Server:

    CRMHOST1> ORACLE_BASE/config/domains/CRMHOST1/CommonDomain/bin/stopWebLogic.sh
    

18. 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 nmConnect are 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".

19. For the wlcs_sipstate2 scaled-out server only, do the following:

    1. Change directory to:

       ORACLE_BASE/config/domains/CRMHOST1/CommonDomain/config/custom
       

    2. In the datatier.xml file, after the following line:

       <server-name>wlcs_sipstate1</server-name>
       

       add

       <server-name>wlcs_sipstate2<server-name>
       

20. Run the newly created managed server:

    1. Navigate to CommonDomain > Environment > Servers > Control.

    2. Select the newly created managed server and click Start.

    3. Navigate to CommonDomain > Environment > Servers and check the State to verify that the newly created managed servers are running.

21. Log in to the Administration Server once again (http://commoninternal.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 /u02/local/oracle/config/domains/HOSTNAME/DomainName/servers/ManagedServer/data/nodemanager/startup.properties file to the following:

    Arguments=-DJDBCProgramName\=DS/CommonDomain/HomePageServer_2
    -Dserver.group\=HomePageCluster
    

Note:

For all the scaled-up and scaled-out managed servers, do the following:

1. Access the Oracle WebLogic Server Administration Console for the CommonDomain:

   http://commoninternal.mycompany.com:7777/console

2. Navigate to Environment > Servers and click the "Managed Server" link.

3. First select the Logging tab and then the HTTP tab.

4. 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

5. Click Save.

6. 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)
   

7. Click Save and Activate Changes.

8. Restart the Managed Server for the changes to take affect.

8.7 Oracle HTTP Server Configuration

To configure Oracle HTTP Server:

1. On WEBHOST1:

   1. Change directory to ORACLE_BASE/config/CommonDomain_webtier/config/OHS/ohs1/moduleconf.

   2. Copy FusionVirtualHost_fs.conf to FusionVirtualHost_fs.conf.org.

2. Edit the 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.

   Example 8-1 Sample "HomePageServer" Code

   <Location /HomePage>
           SetHandler weblogic-handler
           WebLogicCluster <CRMHOST1:port>,<CRMHOST2:port>
       </Location>
   

3. Repeat Step 2 for all applications.

4. Restart Oracle HTTP Server: cd to ORACLE_BASE/config/CommonDomain_webtier/bin and enter the following:

   WEBHOST1> ./opmnctl stopall
   WEBHOST1> ./opmnctl startall
   

5. Repeat Steps 1 through 4 on WEBHOST2.

8.8 Validating the System

You should verify URLs to ensure that the appropriate routing and failover are working.

To verify the URLs:

1. 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.

2. Access the following URLs to verify that routing and failover are functioning properly. (Ensure the log in prompt is visible.)

   • https://commonexternal.mycompany.com/helpPortal/faces/AtkHelpPortalMain

   • https://commonexternal.mycompany.com/homePage/faces/AtkHomePageWelcome

3. Log in to the CommonDomain Oracle WebLogic Server Administration Console and stop all the managed servers on CRMHOST2.

4. Start the managed servers on CRMHOST1.

5. Repeat Step 2. (Ensure the log in prompt is visible.)

6. Start all the managed servers on CRMHOST2 and verify that they are running on CRMHOST1.