Oracle® Fusion Applications Enterprise Deployment Guide 11g Release 1 (11.1.2) Part Number E16684-04 |
|
|
PDF · Mobi · ePub |
This chapter describes how to scale out the Oracle Fusion Supply Chain Management domain.
This chapter includes the following topics:
Section 10.1, "Overview of the Oracle Fusion Supply Chain Management Domain"
Section 10.2, "Prerequisites for Scaling Out the Oracle Fusion Supply Chain Management Domain"
Section 10.3, "Adding a New Machine in the Oracle WebLogic Server Console"
Section 10.4, "Packing and Unpacking the Managed Server Domain Home"
Section 10.5, "Cloning Managed Servers and Assigning Them to CRMHOST2"
Oracle Fusion Customer Relationship Management uses Oracle Fusion Supply Chain Management for products and product groups. The Oracle Fusion Supply Chain Management domain provides the flows to import any existing customer product and product catalog into Oracle Fusion Customer Relationship Management.
Figure 10-1 shows the Oracle Fusion Supply Chain Management 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
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
To add a new machine:
Log in to the Administration Server: http://
scminternal
.mycompany.com:7777/console
.
Navigate to SCMDomain > Environment > Machines.
Local Machine 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 CRMHOST2
Machine operating system - Unix
Click Next.
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
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.
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 a nd unpack the Managed Server domain home:
Change directory to ORACLE_BASE
/products/fusionapps/oracle_common/common/bin
.
Run the pack
command:
CRMHOST2> ./pack.sh -managed=true -domain=ORACLE_BASE/config/domains/ CRMHOST1/SCMDomain -template=ORACLE_BASE/user_templates/ SCMDomain_managed.jar -template_name="SCM_Managed_Server_Domain"
Ensure that /u02/local/oracle/config/domains/
CRMHOST2
/SCMDomain
is empty, and then run the unpack
command:
CRMHOST2> ./unpack.sh -domain=/u02/local/oracle/config/domains/CRMHOST2/ SCMDomain -template=ORACLE_BASE/user_templates/SCMDomain_managed.jar
Here, ORACLE_BASE
is shared, and /u02/local
is local to CRMHOST2
.
To add a managed server and assign it to CRMHOST2
:
Log in to the Administration Server: http://
scminternal
.mycompany.com:7777/console
.
Navigate to SCMDomain > Environment > Servers.
Switch to Lock & Edit mode.
Select the Managed_Server checkbox (for example, ProductManagementServer_1) and then click Clone.
Specify the following Server Identity attributes:
Server Name - ProductManagementServer_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"
Click OK.
You now should see the newly cloned sales server, ProductManagementServer_2
.
Click ProductManagementServer_2 and change the following attributes:
Machine - <CRMHOST2
>
Cluster Name - accept the default, ProductManagementCluster
Note:
Ensure that this cluster name is the same as the cluster name of the original managed server.
Click Save and then Activate Changes.
From the Name column, click the ProductManagementServer_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
/products/fusionapps/wlserver_10.3/server/lib/
CRMHOST2
_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 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 ORACLE_BASE
/products/fusionapps/wlserver_10.3/server/lib/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 6.2, "Creating the Identity Keystore on CRMHOST2."
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 CRMHOST2
_fusion
.
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 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/SCMDomain/ProductManagementServer_2 -Dserver.group\=ProductManagementCluster
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 17 for all the managed servers on this domain.
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"
Stop the domain's Administration Server:
CRMHOST1> ORACLE_BASE/config/domains/CRMHOST1/SCMDomain/bin/stopWebLogic.sh
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='SCMDomain', host='CRMHOST1',port='5556', nmType='ssl', domainDir='ORACLE_BASE/config/domains/CRMHOST1/SCMDomain') 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".
Run the newly created managed server:
Log in to the Administration Server: http://
scminternal
.mycompany.com:7777/console
.
Navigate to SCMDomain > Environment > Servers > Control.
Select the newly created managed server and click Start.
Navigate to SCMDomain > Environment > Servers and check the State to verify that the newly created managed servers are running.
To configure Oracle HTTP Server:
On WEBHOST1
:
Change directory to ORACLE_BASE
/config/CommonDomain_webtier/config/OHS/ohs1/moduleconf
.
Copy FusionVirtualHost_scm.conf
to FusionVirtualHost_scm.conf.org
.
Edit the FusionVirtualHost_scm.conf
file, adding the scaled-out host and port to all the WebLogic Application Clusters. Example 10-1 shows sample code for ProductManagementServer.
Repeat Step 2 for all applications.
Restart Oracle HTTP Server: cd
to ORACLE_BASE
/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 SCMDomain
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 URL to verify that routing and failover are functioning properly. (Ensure the log in prompt is visible.)
https://scmexternal.mycompany.com/productManagement/faces/ItemDashboard
Log in to the SCMDomain
Oracle WebLogic Server Administration Console and stop all the managed servers on CRMHOST2
.
Start the managed servers on CRMHOST1
.
Repeat Step 2. (Ensure the log in prompt is visible.)
Start all the managed servers on CRMHOST2
and verify that they are running on CRMHOST1
.