How to Configure : Configure Parallel Concurrent Processing

Configure Parallel Concurrent Processing

Check prerequisites for setting up Parallel Concurrent Processing
Parallel Concurrent Processing (PCP) spans two or more nodes. If you need to add nodes, follow the relevant instructions in My Oracle Support Knowledge Document 1383621.1, Cloning Oracle Applications Release 12 with Rapid Clone.

Note:  If you are planning to implement a shared Application tier file system, refer to My Oracle Support Knowledge Document 1375769.1.1, Sharing the Application Tier File System in Oracle E-Business Suite Release 12, for configuration steps. If you are adding a new Concurrent Processing node to the application tier, you will need to set up load balancing on the new application by repeating steps in Section 4.7.2.
Set Up PCP
Edit the applications context file via Oracle Applications Manager, and set the value of the variable APPLDCP to ON.

Source the Applications environment.

Execute AutoConfig by running the following command on all concurrent processing nodes:
$
      $INST_TOP/admin/scripts/adautocfg.sh
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.

Restart the Applications listener processes on each application tier node.

Log on to Oracle E-Business Suite Release 12 using the SYSADMIN account, and choose the System Administrator Responsibility. Navigate to the Install > Nodes screen, and ensure that each node in the cluster is registered.

Verify that the Internal Monitor for each node is defined properly, with correct primary node specification, and work shift details. For example, Internal Monitor: Host1 must have primary node as host1. Also ensure that the Internal Monitor manager is activated: this can be done from Concurrent > Manager > Administrator.

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

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

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.
Set Up Transaction Managers
Shut down the application services (servers) on all nodes

Shut down all the database instances cleanly in the Oracle RAC environment, using the command:
SQL>shutdown immediate;
Edit $ORACLE_HOME/dbs/_ifile.ora. Add the following parameters:
_lm_global_posts=TRUE
_immediate_commit_propagation=TRUE
Start the instances on all database nodes, one by one.

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

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 across the Oracle RAC instance.

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

Restart the concurrent managers.

If any of the transaction managers are in deactivated status, activate them from Concurrent > Manager > Administrator.
Set Up Load Balancing on Concurrent Processing Nodes
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 (_balance>).

Note:  Windows users must set the value of "Concurrent Manager TWO_TASK" (s_cp_twotask context variable) to the instance alias.

Execute AutoConfig by running $INST_TOP/admin/scripts/adautocfg.sh on all concurrent nodes.
Note: For further details on Concurrent Processing, refer to the Product Information Center (PIC) (Doc ID 1304305.1).

mailer

set linesize 100
col Component format a40
SELECT component_name as Component, component_status as Status FROM fnd_svc_components WHERE component_type = 'WF_MAILER';


set linesize 150
set pagesize 9999
col COMPONENT_NAME format a50
col COMPONENT_STATUS format a50
select SC.COMPONENT_TYPE, SC.COMPONENT_NAME, FND_SVC_COMPONENT.Get_Component_Status(SC.COMPONENT_NAME) COMPONENT_STATUS from FND_SVC_COMPONENTS SC order by 1, 2;

workflow status

select fcq.USER_CONCURRENT_QUEUE_NAME Container_Name, DECODE(fcp.OS_PROCESS_ID,NULL,'Not
Running',fcp.OS_PROCESS_ID) PROCID,
fcq.MAX_PROCESSES TARGET,
fcq.RUNNING_PROCESSES ACTUAL,
fcq.ENABLED_FLAG ENABLED,
fsc.COMPONENT_NAME,
fsc.STARTUP_MODE,
fsc.COMPONENT_STATUS
from APPS.FND_CONCURRENT_QUEUES_VL fcq, APPS.FND_CP_SERVICES fcs, APPS.FND_CONCURRENT_PROCESSES
fcp, fnd_svc_components fsc
where fcq.MANAGER_TYPE = fcs.SERVICE_ID
and fcs.SERVICE_HANDLE = 'FNDCPGSC'
and fsc.concurrent_queue_id = fcq.concurrent_queue_id(+)
and fcq.concurrent_queue_id = fcp.concurrent_queue_id(+)
and fcq.application_id = fcp.queue_application_id(+)
and fcp.process_status_code(+) = 'A'
order by fcp.OS_PROCESS_ID, fsc.STARTUP_MODE

The following SQL script can be run in sqlplus connected as apps/ to determine the profile Option settings in the Database opposed to checking them in the Application:

The following SQL script can be run in sqlplus connected as apps/ to determine the profile Option settings in the Database opposed to checking them in the Application:

set linesize 155;
set pagesize 200;
set verify off;
col Profile format a20;
 col Level format a14;
col Value format a10;
col App format a3;
col Responsibility format a30;
col USER format a8;
col UPDATED_BY format a8;
select distinct fpo.profile_option_name Profile,
      fpov.profile_option_value Value,
      decode(fpov.level_id, 10001,'Site',
                       10002,'Application',
                       10003,'Responsibility',
                       10004,'User',
                       10005,'Server',
                       10006,'Organization')"LEVEL",
      fa.application_short_name App,
      fr.responsibility_name Responsibility,
      fu.user_name "USER"
from fnd_profile_option_values fpov,
fnd_profile_options fpo,
fnd_application fa,
fnd_responsibility_vl fr,
fnd_user fu,
fnd_logins fl
where fpo.profile_option_id=fpov.profile_option_id
and fa.application_id(+)=fpov.level_value
and fr.application_id(+)=fpov.level_value_application_id
and fr.responsibility_id(+)=fpov.level_value
and fu.user_id(+)=fpov.level_value
and fl.login_id(+) = fpov.LAST_UPDATE_LOGIN
and fpov.profile_option_value is not Null
and fpo.profile_option_name in
('APPS_FRAMEWORK_AGENT', 'WF_MAIL_WEB_AGENT', 'APPS_WEB_AGENT',
'APPS_SERVLET_AGENT', 'ICX_FORMS_LAUNCHER') order by 1,3;

https values

col PROFILE_OPTION_NAME format a60

set lines 2000 pages 2000

SELECT A.PROFILE_OPTION_NAME,B.PROFILE_OPTION_VALUE FROM FND_PROFILE_OPTIONS A,FND_PROFILE_OPTION_VALUES B

where a.PROFILE_OPTION_ID=b.PROFILE_OPTION_ID and b.profile_option_value like 'http:/%';

dblinks

set lines 100

set pages 100

column db_link format a40

column host format a100

select distinct owner from dba_db_links;

select OWNER,DB_LINK,CREATED from dba_db_links;

select OWNER,DB_LINK,CREATED,HOST from dba_db_links;

drop database link &n;

select Host,ACL from dba_network_acls;

find xx*  -type l | xargs ls –ltr

1. Please run the following sql query in the eBiz database to check the relevant profile options and provide the sso_profiles.csv:

Could you please confirm if the same issue is encountered when application is accessed via local login? 

1. Please run the following sql query in the eBiz database to check the relevant profile options and provide the sso_profiles.csv: 

set echo on 
set feedback on 
set pagesize 400 
set linesize 500 
column SHORT_NAME format A40 
column NAME format A50 
column LEVEL_SET format a15 
column CONTEXT format a30 
column VALUE format A60 

spool sso_profiles.csv 

select p.profile_option_name SHORT_NAME, 
decode(v.level_id, 
10001, 'Site', 
10002, 'Application', 
10003, 'Responsibility', 
10004, 'User', 
10005, 'Server', 
'UnDef') LEVEL_SET, 
decode(to_char(v.level_id), 
'10001', '', 
'10002', app.application_short_name, 
'10003', rsp.responsibility_key, 
'10005', svr.node_name, 
'10006', org.name, 
'10004', usr.user_name, 
'UnDef') "CONTEXT", 
v.profile_option_value VALUE 
from fnd_profile_options p, 
fnd_profile_option_values v, 
fnd_profile_options_tl n, 
fnd_user usr, 
fnd_application app, 
fnd_responsibility rsp, 
fnd_nodes svr, 
hr_operating_units org 
where p.profile_option_id = v.profile_option_id (+) 
and p.profile_option_name = n.profile_option_name 
and upper(p.profile_option_name) in ( 
'APPS_SSO', 
'APPS_SERVLET_AGENT', 
'APPS_AUTH_AGENT', 
'APPS_SSO_HINT_COOKIE_NAME', 
'APPLICATIONS_HOME_PAGE', 
'APPS_LOCAL_LOGIN_URL', 
'APPS_PORTAL', 
'APPS_PORTAL_LOGOUT', 
'APPS_SSO_AUTO_LINK_USER', 
'APPS_SSO_LINK_SAME_NAMES', 
'APPS_SSO_ALLOW_MULTIPLE_ACCOUNTS', 
'APPS_SSO_LOCAL_LOGIN', 
'APPS_LOCAL_CHANGE_PWD_URL', 
'APPS_SSO_CHANGE_PWD_URL', 
'APPS_SSO_LDAP_SYNC', 
'APPS_SSO_OID_IDENTITY', 
'APPS_SSO_FORGOT_PWD_URL', 
'APPS_SSO_LISTENER_TOKEN', 
'APPS_DATABASE_ID', 
'PASSWORD_CASE_OPTION','SIGNON_PASSWORD_CASE') 
and usr.user_id (+) = v.level_value 
and rsp.application_id (+) = v.level_value_application_id 
and rsp.responsibility_id (+) = v.level_value 
and app.application_id (+) = v.level_value 
and svr.node_id (+) = v.level_value 
and org.organization_id (+) = v.level_value 
order by user_profile_option_name, level_set; 

spool off 

how many concurrent users do you have at peak ?

REM 
REM SQL to count number of Apps users 
REM Run as APPS user 
REM 
select 'Number of user sessions : ' || count( distinct session_id) How_many_user_sessions 
from icx_sessions icx 
where disabled_flag != 'Y' 
and PSEUDO_FLAG = 'N' 
and (last_connect + decode(FND_PROFILE.VALUE('ICX_SESSION_TIMEOUT'), NULL,limit_time, 0,limit_time,FND_PROFILE.VALUE('ICX_SESSION_TIMEOUT')/60)/24) > sysdate 
and counter < limit_connects; 
REM 
REM 
REM END OF SQL