| Oracle® Fusion Applications Enterprise Deployment Guide for Financials 11g Release 7 (11.1.7) Part Number E27364-10 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Enterprise Deployment Guide for Financials 11g Release 7 (11.1.7) Part Number E27364-10 |
|
|
PDF · Mobi · ePub |
This chapter describes how to scale out the Oracle Fusion Common domain.
This chapter includes the following topics:
Section 10.2, "Prerequisites for Scaling Out the Oracle Fusion Common 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 FINHOST2"
Section 10.8, "Configuring Server Migration for the Managed Servers"
The Oracle Fusion Common domain is shared by all Oracle Fusion Applications product families. Oracle Fusion Financials 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 Financials home page and launch pad
Oracle WebCenter Content, to store all marketing collateral as well as all attachments. Import flow also uses WebCenter Content to stage the CSV files that the user uploads
Oracle WebCenter Content: Imaging, for end-to-end management of document images within enterprise business processes
Oracle Secure Enterprise Search
Oracle WebCenter Community Space and forums
Oracle WebLogic Communication Services (OWLCS) and Oracle WebLogic SIP Server
Figure 2-5 in Chapter 2, "Introduction to the Enterprise Deployment Reference Topologies," shows the topology for the Oracle Fusion Common domain within the overall reference enterprise deployment topology.
Before scaling out the Oracle Fusion Common domain, ensure that you do the following:
Start Node Manager in the Secure Sockets Layer (SSL) mode
Remove Oracle Coherence startup properties
Configure Oracle WebCenter Content Server
To start Node Manager in the Secure Sockets Layer (SSL) mode, follow the instructions in Chapter 7, "Setting Up Node Manager for an Enterprise Deployment."
You must remove Oracle Coherence startup properties from the wlcs_server1 Managed Server's Startup tab before scaling out the wlcs_server2 Manager Server.
Note:
Although the provisioning process adds Oracle Coherence startup properties to the wlcs_server1 Managed Server, Oracle Coherence is not configured and is not currently used in Oracle Fusion Applications on-premise deployments.
To remove the startup properties:
Log in to the Oracle WebLogic Server Administration Console (http://commoninternal.mycompany.com:7777/console).
In the Domain Structure window, expand the Environment node.
Click Servers.
The Summary of Servers page appears.
Select wlcs_server1 (represented as a hyperlink) from the column of the table.
The Settings page appears.
Click Lock & Edit.
Click the Server Start tab.
Remove the following Oracle Coherence properties from the Arguments field:
-DUCS.coherence.localhost=FINHOST1 -DUCS.coherence.localport=7061 -DUCS.coherence.wka1.port=7061 -DUCS.coherence.wka1=FINHOST1
Click Save and Activate Changes.
Navigate to CommonDomain > Environment > Servers and select the Control tab.
Select the wlcs_server1 Managed Server in the table, click Shutdown, and then select the Force Shutdown Now option from dropdown list.
Start the wlcs_server1 Managed Server.
To configure shared content folders for the UCM_server1 server, do the following:
Create a COMMONUCMLBRVH Transmission Control Protocol (TCP) VIP with port 6300 on the load-balancing router (LBR) with FINHOST1:7034 and FINHOST2:7034 as its members.
Note:
Because Oracle WebCenter Content failover works only with TCP connections, ensure that you use TCP, and not Hypertext Transfer Protocol (HTTP), in the LBR setup.
Shut down the UCM_server1 Managed Server:
Log in to the Oracle WebLogic Server Administration Console (http://commoninternal.mycompany.com:7777/console).
In the Domain Structure window, first navigate to Environment > Servers, and then click Control.
Select UCM_server1.
Click Shutdown and then Force Shutdown Now.
In the /u02/local/oracle/config/domains/FINHOST1/CommonDomain/ucm/cs/bin/intradoc.cfg file on FINHOST1, create the variables IntradocDir, vaultDir, and weblayoutDir if they do not already exist, and point them to the shared location: ORACLE_BASE/config/domains/FINHOST1/CommonDomain/ucm/cs.
Copy the FINHOST1/u02/local/oracle/config/domains/FINHOST1/CommonDomain/ucm/cs directory from the local to the shared location, ORACLE_BASE/config/domains/FINHOST1/CommonDomain/ucm/cs.
Do the following in the config file on FINHOST1 (ORACLE_BASE/config/domains/FINHOST1/CommonDomain/ucm/cs/config/config.cfg):
Edit two existing properties with the following:
• SocketHostAddressSecurityFilter=127.0.0.1|FINHOST1 IP Address|FINHOST2 IP Address|COMMONUCMLBRVH IP Address|0:0:0:0:0:0:0:1
• IdcCommandServerHost=127.0.0.1
Add a new property:
• AlwaysReverseLookupForHost=Yes
Start the UCM_server1 Managed Server.
Ensure that the UCM_server1 Managed Server is functioning properly. You should be able to access and log in to the following:
http://FINHOST1:7012/cs
To add a new machine:
Log in to the Administration Server: http://commoninternal.mycompany.com:7777/console.
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 FINHOST2
Machine operating system - Unix
Click Next.
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
Click Finish and activate the changes.
Since the FINHOST1 domain directory file system is also available from FINHOST2, both the pack and unpack commands can be executed from FINHOST2.
To pack and unpack the Managed Server domain home:
Change directory to ORACLE_BASE/products/fusionapps/oracle_common/common/bin.
Run the pack command:
FINHOST2> ./pack.sh -managed=true -domain=ORACLE_BASE/config/domains/ FINHOST1/CommonDomain -template=ORACLE_BASE/user_templates/ CommonDomain_managed.jar -template_name="Common_Managed_Server_Domain"
Ensure that /u02/local/oracle/config/domains/FINHOST2/CommonDomain is empty, and then run the unpack command:
FINHOST2> ./unpack.sh -domain=/u02/local/oracle/config/domains/FINHOST2/ CommonDomain -template=ORACLE_BASE/user_templates/CommonDomain_managed.jar
Here, ORACLE_BASE is shared, and /u02/local is local to FINHOST2.
To add a Managed Server and assign it to FINHOST2:
Log in to the Administration Server: http://commoninternal.mycompany.com:7777/console.
Navigate to CommonDomain > Environment > Servers.
Switch to Lock & Edit mode.
Select the Managed_Server checkbox (for example, HomePageServer_1) and then click Clone.
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 - <FINHOST2>
Server Listen Port - leave "as is"
Click OK.
You now should see the newly cloned sales server, HomePageServer_2.
Click HomePageServer_2 and change the following attributes:
Machine - <FINHOST2>
Cluster Name - accept the default, HomePageCluster
Note:
Ensure that this cluster name is the same as the cluster name of the original Managed Server.
Click Save and then Activate Changes.
Navigate to CommonDomain > Environment > Servers.
From the Name column, click the HomepageServer_2 scaled-out server link.
Click Lock & Edit, and then select the Configuration tab.
Select the Keystores tab, and then 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/config/keystores/FINHOST2_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 7.3, "Creating the Identity Keystore on FINHOST2."
Re-enter the Confirm Custom Identity Keystore Passphrase.
Ensure that the Confirm Custom Trust Keystore path is pointing to the ORACLE_BASE/config/keystores/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 7.3, "Creating the Identity Keystore on FINHOST2."
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 FINHOST2_fusion.
Change the Private Key Passphrase to the keypassword, as described in the second bullet in Step 4 in Section 7.3, "Creating the Identity Keystore on FINHOST2."
Re-enter the keypassword from Step c for the Confirm Private Key Passphrase.
Click Save.
Select the Server Start tab and do the following:
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/CommonDomain/HomePageServer_2 -Dserver.group=HomePageCluster
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 18 for all the Managed Servers on this domain.
Note:
The wlcs_server1 and wlcs_server2 Managed Servers are required only if click-to-dial functionality is enabled in the application. (This functionality is disabled by default.) If click-to-dial is disabled, you can shut down these two managed servers to save host-server memory.
Stop the domain's Administration Server:
FINHOST1> ORACLE_BASE/config/domains/FINHOST1/CommonDomain/bin/stopWebLogic.sh
Set the following environment variable on FINHOST2:
export WLST_PROPERTIES="-Dweblogic.security.SSL.trustedCAKeyStore=ORACLE_BASE/
config/keystores/fusion_trust.jks"
Start the domain's Administration Server:
FINHOST2> ORACLE_BASE/products/fusionapps/wlserver_10.3/common/bin/wlst.sh FINHOST2> nmConnect(username='<username>', password='<password>', domainName='CommonDomain', host='FINHOST1',port='5556', nmType='ssl', domainDir='ORACLE_BASE/config/domains/FINHOST1/CommonDomain') FINHOST2> nmStart('AdminServer') FINHOST2> exit ()
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".
For the wlcs_sipstate2 scaled-out server only, do the following:
Change directory to:
ORACLE_BASE/config/domains/FINHOST1/CommonDomain/config/custom
In the datatier.xml file, after the following line:
<server-name>wlcs_sipstate1</server-name>
add
<server-name>wlcs_sipstate2</server-name>
Run the newly created Managed Servers:
Log in to the Administration Server: http://commoninternal.mycompany.com:7777/console.
Navigate to CommonDomain > Environment > Servers > Control.
Select the newly created Managed Servers (except for the IPM_server2 server) and click Start.
Navigate to CommonDomain > Environment > Servers and check the State to verify that the newly created Managed Servers are running.
Do the following:
Shut down the UCM_server2 Managed Server.
If they do not already exist in the intradoc.cfg file on FINHOST2, create the variables IntradocDir, vaultDir, and weblayoutDir in /u02/local/oracle/config/domains/FINHOST2/CommonDomain/ucm/cs/bin and point them to the shared location, ORACLE_BASE/config/domains/FINHOST1/CommonDomain/ucm/cs.
Start the UCM_server2 Managed Server.
Ensure that the UCM_server2 Managed Server is functioning properly. You should be able to access and log in to the following:
http://FINHOST2:7012/cs
This section describes the additional steps you must perform to complete the Oracle WebCenter product suite scale out.
This section includes the following topics:
Section 10.6.1, "Configuring Persistence Stores for JMS Servers"
Section 10.6.2, "Configuring the Oracle WebCenter Portal wc_spaces and wc_spaces2 Servers"
Section 10.6.3, "Configuring a Default Persistence Store for Transaction Recovery"
Section 10.6.4, "Setting the Listen Address for IPM_server1 and IPM_server2"
Section 10.6.5, "Adding IPM_server1 and IPM_server2 VIP Addresses to the List of Allowed Hosts"
Section 10.6.6, "Adding UCM_server1 and UCM_server2 to the Connection Pool"
You must set the location for all persistence stores targeted to the IPM_server1 and IPM_server2 Managed Servers to a directory that is visible from both FINHOST1 and FINHOST2.
To configure the persistence stores:
Log in to the Oracle WebLogic Server Administration Console (http://commoninternal.mycompany.com:7777/console).
Click Lock & Edit.
In the Domain Structure window, expand the Services node and then click the Persistence Stores node.
The Summary of Persistent Stores page displays.
Click New, and then select the Create File Store option from dropdown list.
Enter the following directory information:
Name: For example, IPMJMSFileStore1
Target: IPM_server1
Directory: ORACLE_BASE/config/domains/FINHOST1/CommonDomain
Click OK.
Repeat Steps 3 through 6 to create the following persistence stores:
ViewerJMSFileStore1, targeting to IPM_server1
ViewerJMSFileStore2, targeting to IPM_server2
IPMJMSFileStore2 , targeting to IPM_server2
Click Activate Changes.
Click Lock & Edit.
In the Domain Structure window, expand the Services node and then click the Messaging > JMS Servers node.
The Summary of JMS Servers page displays.
Click the name of the server, IpmJmsServer1 .
From the Configuration > General tab, select IPMJMSFileStore1 from the Persistence Store dropdown list.
Click Save.
Repeat Steps 10 through 13 for the JMS server ViewerJmsServer1 using ViewerJMSFileStore1.
Click Activate Changes.
Click Lock & Edit.
In the Domain Structure window, expand the Services node and then click the Messaging > JMS Servers node.
The Summary of JMS Servers page displays.
Click New.
Enter a name (for example, IpmJmsServer2), then select IPMJMSFileStore2 from the Persistence Store dropdown list.
Click Next.
Select IPM_server2 as the target.
Click Finish.
Repeat Steps 17 through 22 to create the new JMS server ViewerJmsServer2 using ViewerJMSFileStore2 targeting theIPM_server2 Managed Server.
Click Activate Changes.
Restart the IPM_server1 and IPM_server2 Managed SServers.
After scaling out the Oracle WebCenter Portal Managed Server, do the following:
Log in to: http://commoninternal.mycompany.com:7777/em.
Navigate to Farm_CommonDomain > WebCenter > Portal > Spaces > WebCenter Portal ( 11.1.*) (WC_Spaces) > WebCenter Portal (top left or right pane) > Settings > Service configuration.
Click Content Repository.
Highlight FusionAppsContentRepository and click Edit.
Select Socket and enter COMMONUCMLBRVH as the host and the LBR port for the server.
If updating the first instance of wc_spaces did not automatically update the second instance, repeat Step 2 through Step 4 for wc_spaces2.
Restart the Oracle WebCenter Portal wc_spaces and wc_spaces2 Managed Servers.
When configuring Oracle WebCenter Content Server, the FusionAppsContentRepository content repository should move from the file system to the Fusion database. To verify the move of the repository to the database, upload the /etc/hosts file on FINHOST1 to WebCenter Content Server by running the following commands, in order:
$ export RIDC_JAR=/u01/oracle/products/fusionapps/ecm/ucm/Distribution/RIDC/
oracle.ucm.ridc-11.1.1.jar
$ export UCMSCRIPT_JAR=/u01/oracle/products/fusionapps/ecm/ucm/Distribution/
FAProv/ucmscript.jar
$ java -cp $UCMSCRIPT_JAR:$RIDC_JAR oracle.ucm.client.UploadTool
--url=idc://FINHOST1:7034 --username=sysadmin
--uploadFile=/etc/hosts --dSecurityGroup=public --dDocTitle=hosts --quiet
Notes:
In the java -cp command, the Intradoc protocol is being used in the URL option --url=idc://, and not http.
Get the IntradocServerPort number 7034 used in the URL above from the /u02/local/oracle/config/domains/FINHOST1/CommonDomain/ucm/cs/config/config.cfg file.
After the /etc/hosts file successfully uploads to the Fusion database, something similar to the following displays:
Upload successful. [dID=1 | dDocName=UCMFA000001]
You will use the dID number in the next sqlplus command.
$ sqlplus FUSION_OCSERVER11G/password@fusionDB SQL> select dID, dRenditionID, dFileSize, DLastModified, from FileStorage where dID=1; SQL>
The following is sample output from the SQL command:
DID DRENDITIONID DFILESIZE DLASTMODIFIED 1 primaryFile 702 21-MAY-13 12.16.03.524000 PM 1 webViewableFile 702 21-MAY-13 12.16.03.687000 PM
Each server has a transaction log which stores information about committed transactions that are coordinated by the server that may not have been completed. Oracle WebLogic Server uses this transaction log for recovery from system crashes or network failures. To leverage the migration capability of the Transaction Recovery Service for the servers within a cluster, store the transaction log in a location accessible to a server and its backup servers.
Note:
Preferably, this location should be a dual-ported SCSI disk or on a Storage Area Network (SAN).
To set the location for the default persistence store:
Log in to the Oracle WebLogic Server Administration Console (http://commoninternal.mycompany.com:7777/console).
In the Change Center, click Lock & Edit.
In the Domain Structure window, expand the Environment node and then click the Servers node.
The Summary of Servers page displays.
Click the name of the server (represented as a hyperlink) in the IPM_server1 table. The settings page for the selected server opens with the Configuration tab active.
Open the Services tab.
In the Default Store section of the page, enter the path to the folder where the default persistent stores will store its data files. For example, create a directory
FINHOST1> ORACLE_BASE/config/domains/FINHOST1/CommonDomain/tlogs
Click Save.
Repeat Steps 1 through 7 for the IPM_server2 Managed Server.
Click Activate Changes.
Restart the Managed Servers to activate the changes (ensure that Node Manager is up and running):
Log in to the Oracle WebLogic Server Administration Console (http://commoninternal.mycompany.com:7777/console).
In the Summary of Servers screen, select the Control tab.
Select IPM_server1 and IPM_server2 in the table and then click Shutdown.
After the servers have shut down, select IPM_server1 and IPM_server2 in the table and click Start.
Notes:
To enable migration of the Transaction Recovery service, specify a location on a persistent storage solution that is available to other servers in the cluster. Both IPM_server1 and IPM_server2 must be able to access this directory.
Ensure the following the path exists on your machine: /usr/share/X11/fonts/TTF.
Ensure that you have performed the steps described in Section 16.1, "Enabling Virtual IPs on FINHOST1 and FINHOST2" before setting the IPM_server1 and IPM_server2 listen addresses.
To set the listen address for the Managed Servers:
Log in to the Administration Console (http://commoninternal.mycompany.com:7777/console).
In the Change Center, click Lock & Edit.
Expand the Environment node in the Domain Structure window.
Click Servers.
The Summary of Servers page displays.
Select IPM_server1 in the table.
The Settings page for IPM_server1 Managed Server displays.
Set the listen address to COMMONIPMVH1 and click Save.
Navigate to the Summary of Servers page and select IPM_server2 in the table.
The Settings page for the IPM_server2 Managed Server displays.
Set the listen address to COMMONIPMVH2 and click Save.
Note:
Both COMMONIPMVH1 and COMMONIPMVH2 are pingable.
Click Activate Changes.
The changes will not take effect until the IPM_server1 and IPM_server2 Managed Servers are restarted. To restart the Managed Servers, do the following:
Ensure that Node Manager is up and running.
On the Summary of Servers page, select the Control tab.
Navigate to the Summary of Servers page, select IPM_server1 andIPM_server2 in the table, and then click Shutdown.
After the servers have shut down, select IPM_server1 and IPM_server2 in the table and click Start.
Perform these steps to add the IPM_server1 and IPM_server2 virtual-host IP addresses to the SocketAddressSecurityFilter parameter list:
Edit the config file on FINHOST1, ORACLE_BASE/config/domains/FINHOST1/CommonDomain/ucm/cs/config/config.cfg, with the following:
SocketHostAddressSecurityFilter=127.0.0.1|FINHOST1 IP Address|FINHOST2 IP Address|COMMONUCMLBRVH IP Address|COMMONIPMVH1 IP Address|COMMONIPMVH2 IP Address|0:0:0:0:0:0:0:1
AlwaysReverseLookupForHost=Yes
Restart the UCM_server1 and UCM_server2 Oracle WebCenter Content Management Servers for the changes to take effect.
To add UCM_server1 and UCM_server2 to the connection pool, do the following:
Log in to the Oracle WebCenter Content: Imaging application at: https://commonexternal.mycompany.com/imaging.
In the left-hand pane, expand Manage Connections.
Click the Fusion Applications UCM Connection link.
In the right-hand Fusion Applications UCM Connection: Connection Summary pane, click Modify.
In the Basic Information screen, click Next.
In the Connection Settings screen, add two servers to the Content Server pool:
FINHOST1: 7034
FINHOST2: 7034
Click Next.
In the Connection Security screen, leave all four default selections for the FUN_FINANCIAL_APPLICATION_ADMINISTRATOR_JOB WebLogic user, and then click Next.
In the Review Settings screen, review the connection details and click Submit.
To configure Oracle HTTP Server:
Do the following: :
On WEBHOST1, change directory to ORACLE_BASE/config/CommonDomain_webtier/config/OHS/ohs1/moduleconf
On WEBHOST2, change directory to ORACLE_BASE/config/CommonDomain_webtier1/config/OHS/ohs2/moduleconf
Copy FusionVirtualHost_fs.conf to FusionVirtualHost_fs.conf.org.
Edit the FusionVirtualHost_fs.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_fs.conf file. Example 10-1 shows sample code for HomePageServer.
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 10-1.
Repeat Step 3 for all applications.
Do the following to restart Oracle HTTP Server:
On WEBHOST1:
Change directory to ORACLE_BASE/config/CommonDomain_webtier/bin
Enter the following:
WEBHOST1> ./opmnctl stopall WEBHOST1> ./opmnctl startall
On WEBHOST2:
Change directory to ORACLE_BASE/config/CommonDomain_webtier1/bin
Enter the following:
WEBHOST2> ./opmnctl stopall WEBHOST2> ./opmnctl startall
Server migration is required for proper failover of Oracle Fusion Financials 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."
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 FINHOST1 while the Managed Servers on FINHOST2 are running.
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
Log in to the CommonDomain Oracle WebLogic Server Administration Console and stop all the Managed Servers on FINHOST2.
Start the Managed Servers on FINHOST1.
Repeat Step 2. (Ensure the log in prompt is visible.)
Start all the Managed Servers on FINHOST2 and verify that they are running on FINHOST1 and FINHOST2.
|
 Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|