Professional Documents
Culture Documents
F1634119743 Estrada 74 (1) New
F1634119743 Estrada 74 (1) New
F1634119743 Estrada 74 (1) New
Introduction This paper describe step-by-step the required configuration changes Load Balancer, Parallel Concurrent Processing. Using Load-Balancers with Oracle E-Business Suite Release 12 [ID 380489.1]
Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 12 [ID 823587.1]
Enable Load Balancing This section describes required steps to configure hardware load balancer to work with Oracle E-Business R12 to balance load between the two web tiers. 1. Login into application as SYSADMIN and select System Administration responsibility
2.
3.
4.
5.
6.
7.
Select nodes (web1 and web2) from list of available nodes and click next
8.
Variable
Non-SSL Value
SSL Value
url constructed with http protocol and s_webport for both non-SSL and SSL url constructed with http protocol and s_webport url constructed with https protocol and s_webssl_port
9. Click Next
10. Make sure that all validations complete successful and click next
Configure Parallel Concurrent Processing This section describes required steps to enable Parallel Concurrent Processing (PCP) on Concurrent Manager Tiers (CM1 and CM2).
1.
Edit the applications context file via Oracle Applications Manager, and set the value of the variable APPLDCP to ON.
2.
Execute AutoConfig by running the following command on all concurrent processing nodes: $ $INST_TOP/admin/scripts/adautocfg.sh
3.
4.
Check the tnsnames.ora and listener.ora configuration files, located in $INST_TOP/ora/10.1.2/network/admin. Ensure that the required FNDSM and FNDFS entries are present for all other concurrent nodes.
5.
6.
Log on to Oracle E-Business Suite Release 12 using the SYSADMIN account, and choose the System Administrator Responsibility. Navigate to Install > Nodes screen, and ensure that each node in the cluster is registered.
7.
Verify that the Internal Monitor for each node is defined properly, with correct primary and secondary node specification, and work shift details. For example, Internal Monitor: Host2 must have primary node as host2 and secondary node as host3. Also ensure that the Internal Monitor manager is activated: this can be done from Concurrent > Manager > Administrator.
8.
Set the $APPLCSF environment variable on all the Concurrent Processing nodes to point to a log directory on a shared file system.
9.
Set the $APPLPTMP environment variable on all the CP nodes to the value of the UTL_FILE_DIR entry in init.ora on the database nodes. (This value should be pointing to a directory on a shared file system.)
10. Set profile option 'Concurrent: PCP Instance Check' to OFF if database instance-sensitive failover is not required. By setting it to 'ON', a concurrent manager will fail over to a secondary Application tier node if the database instance to which it is connected becomes unavailable for some reason.
11. Edit the applications context file through the Oracle Applications Manager interface, and set the value of Concurrent Manager TWO_TASK (s_cp_twotask) to the load balancing alias (<service_name>_balance>).
Note: Windows users must set the value of "Concurrent Manager TWO_TASK" (s_cp_twotask context