PURPOSE

-------
This paper is intended to give full instructions for installing and setting up Parallel
Concurrent Processing in Unix Server

Setting Up Parallel Concurrent Processing On Unix Server

--------------------------------------------------------
Setup:
=====
You have installed an Oracle Applications Release 10.7,11 or 11i or Higher against its
certified Oracle Database on Node 1. This installation is up and running correctly, and
you are able to run jobs through the concurrent manager without errors.

Additionally, you create Node 2, which has same APPL_TOP in Node 1, and connect to
the same operating system.

Parallel Concurrent Processing requires two OR more nodes with identical APPL_TOP
Under this setup, when applying a patch you need to apply the copy(C) and
generate(g)driver To all nodes and apply the database patch driver only once since both
nodes go Against the same database instance.

Steps Used for Implementing Parallel Concurrent Processing:

1. On Node 1, log in as applmgr user and Source all your environment files to fully set
your environment.

At the prompt type:

$ id

This should return output that looks similar to:

uid=1003(applmgr) gid=102(ad)

You need this information when you are creating the applmgr user on
Node 2. If the applmgr user on Node 2 does not have the same exact
uid and gid Then this will cause errors later when one of the nodes
tries to login and Start processes on the other node.

2. On Node 2, create the applmgr users with the same uid and gid as
found In Step #1.

3. On each node in the applmgr's $HOME directory create a .rhosts file.

Within this file place an entry so that the applmgr user from each
node is able to rsh into the other node without providing a pwd.

Example text within the .rhosts file that would be located on Node 2:
 Node1.us.oracle.com applmgr

Example text within the .rhosts file that would be located on Node 1:

Node2.us.oracle.com applmgr

At this point, if you were logged in on Node 1 as applmgr, you should

be able to Type "rsh node2" at the UNIX prompt and log into Node 2 as
applmgr without providing a password. The same process should be
followed so that applmgr on Node 2 can rsh into Node 1 without a Pwd.

4. Make sure the PATH variable for the applmgr user on each node
includes the ping utility. You can type "which ping" to check if it
is already in your path. If it is not type "where is ping" to find
it. Then include this directory in your PATH.

5. While logged into Node 2 as applmgr make sure you can make a sqlplus
connection to the database on Node 1 without having to use the sign.
Example: sqlplus system/manager

This will ensure the $ORACLE_HOME/network/admin/tnsnames.ora file and

the TWO_TASK variables are set correctly.

6. On each Node make sure the Environment Variable APPLDCP set to ON in

the environment file, which should be under$APPL_TOP.
Once this environment file is sourced, your managers may experience
difficulty coming up in a non-parallel environment, so make sure the
APPLDCP set to OFF in a non-parallel environment.

7. On each Node edit the dcpstart file located under the $FND_TOP/bin
directory:Check How to edit dcpstart file in in the end of thisnote.

8. Make sure the PMON method is set to LOCK mode.

9. On each node modify the TNSNAMES.ORA file to include FNDFS entry for
other node. The TNSNAMES.ORA file located under 8.0.6 oracle home:

<ORACLE_HOME>\<SID>ORA\8.0.6\NET80\ADMIN

10. Create symbolic links between the top level directories on each
node to be able to view the report output file generated on another
node, or use the NFS to mount the log and output files to eachnode.

11. Add these three Environment Variable to the Environment File

APPSORA.env and source APPSORA.env from DCPSTART script on eachode:
 PRINTER=noprint
export PRINTER

REPORTS60_NO_DUMMY_PRINTER="YES"
export REPORTS60_NO_DUMMY_PRINTER

TK_PRINT_STATUS="echo %n is valid"
export TK_PRINT_STATUS

12. Start the Internal Concurrent Manger, you should be able to do that
from Node1 Or Node2.

13. From Oracle Application under Sysadmin Responsibility Navigate to:

Concurrent/manager/administer and see if the managers are coming up
on their proper nodes.

14. Configuring Concurrent Managers on the application:

============================================

Perform the following steps in order to register the nodes and

distribute the Concurrent managers on these nodes:

1. Log into Oracle Applications as SYSADMIN with System Administrator

Responsibility

2. Navigate to Install > Nodes and register the names of all the
potential Nodes in the PCP setup

3. Navigate to Concurrent > Manager > Define and set up the primary
node for your Internal Concurrent Manager. This is the node on
which the ICM Prefers to run, when the node is available.

4. Navigate to Concurrent > Manager > Define and define a new manager
of type: Internal Monitor

a. To do this, from the manager type pull down list choose FNDIMON.

b. Define the primary and secondary node names and assign a standard
work-shift with one process

5. Repeat the step above and define one Internal Monitor "IM" for
Each node in the setup, except the primary node of ICM

6. Finally, set up the primary and secondary node names for all the
 concurrent managers according to the desired distribution.

How to edit the dcpstart file:

======================
Edit dcpstart on each concurrent processing server:

If you are setting up parallel concurrent processing, you need to edit the file dcpstart in
$FND_TOP/bin directory of each concurrent processing server to set Environment
variable values for the server.

-Copy the dcpstart file to each server's applmgr home directory:

To edit a dcpstart file, open the file with an editor and find the following lines:

ORACLE_HOME=<pathname>; export ORACLE_HOME

ORACLE_SID=<database>; export ORACLE_SID
#TWO_TASK=<database connect string>; export TWO_TASK

Change the variable value to the correct values on the server.

Either ORACLE_SID or TWO_TASK should be set.
You can leave the TWO_TASK line with the comment marker at the beginning of the
line(#)if you do not use that variable.
If you set TWO_TASK, however, comment the ORACLE_SID line.
Here is an example if TWO_TASK is set:

ORACLE_HOME=/d01/oracle/8.0.6; export ORACLE_HOME

#ORACLE_SID=proddb; export ORACLE_SID
TWO_TASK=aprod1; export TWO_TASK

Below this line find the line that runs the environment file.The environment filenames Is
typically<dbname>.env, where <dbname>is the name of the database in which the
current product group is installed.

Specify here the full path and filename of the concurrent processing server's Environment
file. If you installed product files on a local disk, the environment file is in the server's
top applications directory. Otherwise it is in the applmgr Home directory. Here is an
example: . /d01/appl/11.5.0/appsora.env

-Each server needs a copy of the edited dcpstart file in its applmgr home directory.

RELATED DOCUMENTS
-----------------
Oracle Applications System Administrator's Guide Release 11i Page: 5-63