PCP configuration in 12.2

 

Step 1: Using Oracle Applications Manager, edit the applications context file, and set the variable APPLDCP's value to ON.

For both Nodes (ebs-app1  and  ebs-app2), set the value of s appldcp to ON in the RUN  and PATCH file system context files.

On Run File System, ebs-app1 and ebs-app2

[appldev ~]$ grep APPLDCP $CONTEXT_FILE

<APPLDCP oa_var="s_appldcp">ON</APPLDCP>

On Patch File System, ebs-app1 and ebs-app2

<APPLDCP oa_var="s_appldcp">ON</APPLDCP>

Step 2: Run the following command on all concurrent processing nodes to carry out AutoConfig.

ssh ebs-app2

[appldev@ebs-app2 ~]$ echo $FILE_EDITION

Run

[appldev@ebs-app2 ~]$ adautocfg.sh

ssh ebs-app1

[appldev@ebs-app1 ~]$ echo $FILE_EDITION

Run

[appldev@ebs-app1 ~]$ adautocfg.sh

Step3: Examine the listener.ora and tnsnames.ora configuration files, which are located in the $INST TOP/ora/10.1.2/network/admin directory. Verify that all other concurrent nodes have the necessary FNDSM and FNDFS entries.

Edit the tnsnames.ora file on both ebs-app1 & ebs-app2 Application nodes.

[appldev~]$ cd $TNS_ADMIN

[appldev~]$ vi tnsnames.ora

[appldev~]$ vi listener.ora”

Step4: Restart the Applications listener processes on BOTH application tier node.

[appldev~]$ cd $ADMIN_SCRIPTS_HOME

[appldev~]$ adalnctl.sh stop

[appldev~]$ adalnctl.sh start

Step5: Use the SYSADMIN account to log into Oracle E-Business Suite Version 12 and select the System Administrator Responsibility. Make sure that each node in the cluster is registered by going to the Install > Nodes screen. There should be a total of 5 entries.

Step 6: Confirm that the Internal Monitor is correctly defined for each node, including the principal node specification and work shift information. Internal Monitor: For instance, host1 must be the primary node. Furthermore, make sure the Internal Monitor manager is enabled you can accomplish this by going to Concurrent > Manager > Administrator.

Step 7: Set the $APPLCSF environment variable on all the Concurrent Processing nodes to point to a log directory on a shared file system.

[appldev~]$ echo $APPLCSF

Step 8: Set the $APPLPTMP environment variable on all the CP nodes to the value of the shared directory path on the database node.

Step 9: On both application tier nodes, run AUTOCONFIG on the RUN file system (first on node 2 and then on node 1).

[appldev~]$

$ echo $FILE_EDITION

run

[appldev~]$

$ adautocfg.sh

Step 10: If database instance-sensitive failover is not necessary, set the profile option "Concurrent: PCP Instance Check" to OFF. A concurrent manager will switch to a backup Application layer node if the database instance to which it is attached goes down by setting it to "ON".

Step 11: Set Up Transaction Managers

1.Shut down the application services (servers) on all nodes

2.Shut down the database instance, using the command: 

[oradev@oraebs01]$ sqlplus / as sysdba;

sql> shut immediate.

 

Add following parameter as below (oraebs01)

_lm_global_posts=TRUE 

_immediate_commit_propagation=TRUE

[oradev@oraebs01]$  cd $ORACLE_HOME/dbs/

[oradev@oraebs01]$  vi vision1_oraebs01_ifile.ora

4.Start the instances on all database nodes, one by one.

[oradev@oraebs01]$ sqlplus / as sysdba;

sql> startup;

 

5. Start up the application services (servers) on all nodes.

6. Log on to Oracle E-Business Suite Release 12 using the SYSADMIN account, and choose the System Administrator responsibility. Navigate to Profile > System, change the profile option ‘Concurrent: TM Transport Type' to ‘QUEUE', and verify that the transaction manager works.

7. Navigate to Concurrent > Manager > Define screen, and set up the primary and secondary node names for transaction managers.

8. Restart the concurrent managers. (both Tier)

9. If any of the transaction managers are in deactivated status, activate them from Concurrent > Manager > Administrator. 

Step 12: Set Up Load Balancing on Concurrent Processing Nodes:

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

2. Execute AutoConfig by running $INST_TOP/admin/scripts/adautocfg.sh on all concurrent nodes.