11 Scaling Out the Oracle Fusion Financials Domain

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

This chapter includes the following topics:

• Section 11.1, "Overview of the Oracle Fusion Financials Domain"

• Section 11.2, "Prerequisites for Scaling Out the Oracle Fusion Financials Domain"

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

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

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

• Section 11.6, "Oracle HTTP Server Configuration"

• Section 11.7, "Validating the System"

11.1 Overview of the Oracle Fusion Financials Domain

The Oracle Financials domain provides Oracle Fusion Customer Relationship Management with Currency, Calendar, and other functionality. The Oracle Fusion Financials domain exposes setup portlets that the Oracle Fusion Customer Relationship Management implementation manager can use via Functional Setup Manager.

Figure 11-1 shows the Oracle Fusion Financials domain within the overall reference enterprise deployment topology for Oracle Fusion Applications.

Figure 11-1 Reference Topology for Oracle Fusion Financials Domain

11.2 Prerequisites for Scaling Out the Oracle Fusion Financials 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

11.3 Adding a New Machine in the Oracle WebLogic Server Console

To add a new machine:

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

2. Navigate to FinancialDomain > 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 19.8.18, "Administration Console Redirects from Internal URL to Container URL after Activation" for the temporary solution.

11.4 Packing and Unpacking the Managed Server Domain Home

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

To pack and unpack the Managed Server domain home:

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/FinancialDomain -template=ORACLE_BASE/user_templates/
   FinancialDomain_managed.jar -template_name=
   "Financial_Managed_Server_Domain"
   

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

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

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

11.5 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://fininternal.mycompany.com:7777/console.

2. Navigate to FinancialDomain > Environment > Servers.

3. Switch to Lock & Edit mode.

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

5. Specify the following Server Identity attributes:

   • Server Name - GeneralLedgerServer_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 server, GeneralLedgerServer_2.

7. Click GeneralLedgerServer_2 and change the following attributes:

   • Machine - <CRMHOST2>

   • Cluster Name - accept the default, GeneralLedgerCluster

     Note:

     Ensure that this cluster name is the same as the cluster name of the original managed server.

8. Click Save and then Activate Changes.

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

10. Click Lock & Edit, and then select the Configuration tab.

11. Select the Keystores tab, and 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. Select 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. 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/FinancialDomain/GeneralLedger_2
    -Dserver.group\=GeneralLedgerCluster
    

    Click Save.

15. Select the Logging tab, and then select the HTTP tab.

16. Do the following:

    1. Change the Log file name to logs/access.log.%yyyyMMdd%.

    2. Change the rotation type to By Time.

    3. Leave the Limit number of retained files option unchecked.

    4. Leave the Rotate log file on startup option unchecked.

    5. Click Save.

    6. Expand Advanced.

    7. Change the format to Extended.

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

    9. Click Save.

17. Click Activate Changes.

18. Repeat Steps 2 to 17 for all the managed servers on this domain.

19. Set the following environment variable on CRMHOST2:

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

20. Stop the domain's Administration Server:

    CRMHOST1> CRACLE_BASE/config/domains/CRMHOST1/FinancialDomain/bin/stopWebLogic.sh
    

21. 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='FinancialDomain', host='CRMHOST1',port='5556', 
    nmType='ssl', domainDir='ORACLE_BASE/config/domains/CRMHOST1/FinancialDomain')
    
    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".

22. Run the newly created managed server:

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

    2. Navigate to FinancialDomain > Environment > Servers > Control.

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

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

11.6 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_fin.conf to FusionVirtualHost_fin.conf.org.

2. Edit the FusionVirtualHost_fin.conf file, adding the scaled-out host and port to all the WebLogic Application Clusters. Example 11-1 shows sample code for GeneralLedgerServer.

   Example 11-1 Sample "GeneralLedgerServer" Code

   <Location /GeneralLedger>
           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.

11.7 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 FinancialDomain 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://finexternal.mycompany.com/ledger/faces/JournalEntryPage

   • https://finexternal.mycompany.com/ledger/faces/LedgerWorkArea

3. Log in to the FinancialDomain 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.