Skip Headers
Oracle® Fusion Applications Financials Enterprise Deployment Guide
11g Release 5 (11.1.5)

Part Number E27364-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

13 Scaling Out the Oracle Fusion Projects Domain

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

This chapter includes the following topics:

13.1 Overview of the Oracle Fusion Projects Domain

The Oracle Fusion Projects domain supports the following products:

It integrates with the Oracle Essbase server in the Oracle Business Intelligence domain to support Project Performance Reporting functionality.

Figure 2-7 in Chapter 2, "Introduction to the Enterprise Deployment Reference Topologies," shows the topology for the Oracle Fusion Projects domain within the overall reference enterprise deployment topology.

13.2 Prerequisites for Scaling Out the Oracle Fusion Projects Domain

Before you begin, ensure the following:

13.3 Adding a New Machine in the Oracle WebLogic Server Console

To add a new machine:

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

  2. Navigate to ProjectsDomain > 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 FINHOST2

    • Machine operating system - Unix

  5. Click Next.

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

  7. Click Finish and activate the changes.

    Note:

    If you get an error when activating the changes, see Section 20.8.18, "Administration Console Redirects from Internal URL to Container URL after Activation" for the temporary solution.

13.4 Packing and Unpacking the Managed Server Domain Home

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:

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

  2. Run the pack command:

    FINHOST2> ./pack.sh -managed=true -domain=ORACLE_BASE/config/domains/
    FINHOST1/ProjectsDomain -template=ORACLE_BASE/user_templates/
    ProjectsDomain_managed.jar -template_name=
    "Projects_Managed_Server_Domain"
    
  3. Ensure that /u02/local/oracle/config/domains/FINHOST2/ProjectsDomain is empty, and then run the unpack command:

    FINHOST2> ./unpack.sh -domain=/u02/local/oracle/config/domains/FINHOST2/
    ProjectsDomain -template=ORACLE_BASE/user_templates/
    ProjectsDomain_managed.jar
    

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

13.5 Cloning Managed Servers and Assigning Them to FINHOST2

To add a Managed Server and assign it to FINHOST2:

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

  2. Navigate to ProjectsDomain > Environment > Servers.

  3. Switch to Lock & Edit mode.

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

  5. Specify the following Server Identity attributes:

    • Server Name - ProjectsFinancialsServer_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"

      Note:

      For Oracle SOA Suite server, add a port value that is different than the soa_server1 server value. This will help in server migration.

  6. Click OK.

    You now should see the newly cloned server, ProjectsFinancialsServer_2.

  7. Click ProjectsFinancialsServer_2 and change the following attributes:

    • Machine - <FINHOST2>

    • Cluster Name - accept the default, ProjectsFinancialsCluster

      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. Navigate to ProjectsDomain > Environment > Servers.

  10. From the Name column, click the ProjectsFinancialsServer_2 scaled-out server link.

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

  12. Select the Keystores tab, and ensure that the keystores value is Custom Identity and Custom Trust.

  13. Do the following:

    1. Change the Custom Identity Keystore path to point to the ORACLE_BASE/config/keystores/FINHOST2_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 7.2, "Creating the Identity Keystore on FINHOST2."

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

    5. Ensure that the Confirm Custom Trust Keystore path is pointing to the ORACLE_BASE/config/keystores/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 7.2, "Creating the Identity Keystore on FINHOST2."

    8. Re-enter the Custom Trust Keystore Passphrase.

    9. Click Save.

  14. Select the SSL tab.

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

    2. Change the Private Key Alias to FINHOST2_fusion.

    3. Change the Private Key Passphrase to the keypassword, as described in the second bullet in Step 4 in Section 7.2, "Creating the Identity Keystore on FINHOST2."

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

    5. Click Save.

  15. 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/ProjectsDomain/ProjectsFinancialsServer_2
    -Dserver.group=ProjectsFinancialsCluster
    
    
    

    Click Save.

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

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

  18. Click Activate Changes.

  19. Repeat Steps 2 to 18 for all the Managed Servers on this domain.

  20. Set the following environment variable on FINHOST2:

    WLST_PROPERTIES="-Dweblogic.security.SSL.trustedCAKeyStore=ORACLE_BASE/
    config/keystores/fusion_trust.jks"
    
  21. Stop the domain's Administration Server:

    FINHOST1> CRACLE_BASE/config/domains/FINHOST1/
    ProjectsDomain/bin/stopWebLogic.sh
    
  22. Restart the domain's Administration Server:

    FINHOST2> ORACLE_BASE/products/fusionapps/wlserver_10.3/common/bin/wlst.sh
    
    FINHOST2> nmConnect(username='<username>', password='<password>',
    domainName='ProjectsDomain', host='FINHOST1',port='5556', 
    nmType='ssl', domainDir='ORACLE_BASE/config/domains/FINHOST1/ProjectsDomain')
    
    FINHOST2> nmStart('AdminServer')
    

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

  23. Run the newly created Managed Servers:

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

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

    3. Select the newly created Managed Servers and click Start.

    4. Navigate to ProjectsDomain > Environment > Servers and check the State to verify that the newly created Managed Servers are running.

13.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_prj.conf to FusionVirtualHost_prj.conf.org.

  2. Edit the FusionVirtualHost_prj.conf file, 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_prj.conf file. Example 13-1 shows sample code for ProjectsFinancialsServer.

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

    Example 13-1 Sample "ProjectsFinancialsServer" Code

    <Location /projectsFinancials>
            SetHandler weblogic-handler
            WebLogicCluster <FINHOST1:port>,<FINHOST2: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.

13.7 Configuring Server Migration for the Managed Servers

Server migration is required for proper failover of Oracle Fusion Projects 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."

13.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 ProjectsDomain Oracle WebLogic Server Administration Console and stop all the Managed Servers on the FINHOST1 while the Managed Servers on FINHOST2 are running.

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

    • https://prjexternal.mycompany.com/projectsFinancials/faces/PRJProjectWorkarea

    • https://prjexternal.mycompany.com/projectsFinancials/faces/PrjCostWorkArea

  3. Log in to the ProjectsDomain Oracle WebLogic Server Administration Console and stop all the Managed Servers on FINHOST2.

  4. Start the Managed Servers on FINHOST1.

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

  6. Start all the Managed Servers on FINHOST2 and verify that they are running on FINHOST1 and FINHOST2.