4 Steps for Host based concurrent program

Posted on June 18th, 2007 by Sanjit Anand | Print This Post | Email This Post

These are the few steps which is required to make a host based Concurrent Program.

The first steps would be , you have to create a script and save as .prog extension and put into your application top bin folder.
If your custom application is XX then the scripts should goes to $XX_TOP/bin
For example, call the script CUSTOM.prog and place it under

Step 2
Now,you have understood , the execution of unix program is bit different in oracle application. The only things you have to notice is you need to pass 4 mandatory parameter to execute host program.
The other way around is ,you can use fndcpesr and link with your host program.It means the fndcpesr will take care of your 4 mandatory parameter.

You have to simply create a soft link with $XX_TOP/bin folder.

   ln -s $FND_TOP/bin/fndcpesr <script> 

This link should be named the same as your script without the .prog extension.

Step 3
Next you have to make into system administrator responsibly follow 3 steps from these menu

• sysadmin -> concurrent-> program -> executable
• sysadmin -> concurrent-> program -> define
• sysadmin ->security -> responsibility -> request

Register the concurrent program, using an execution method of ‘Host’.
Use the name of your script without the .prog extension as the name of the executable.

Step 4

Your script will be passed at least 4 parameters, between $1 and $4.
These are:
orauser/pwd,
userid,
username,
and request_id

Any other parameters you define will be passed in $5 and higher.
Make sure your script returns an exit status also.

What additional piece need to incorporate in code
you need to simply
ORA_USER_PASS=$1
USERID=$2
USERNAME=$3
REQUESTID=$4

With or without extn ‘.prog’
You can register an host application without the prog extension. Your script will not have any extension. However in order to make this work you must have logic in your host application that parses the parameter string passed to it and extract the individual parameters out of it. This is required because the Concurrent manager passes 1 string containing all the parameters, to the host program. In programs linked to the fndcpesr
program, the fndcpesr parses it into the individual parameters.

How can you return an error status of the concurrent programs?

Yes, By default, a shell script returns success (status code 0). In case of error script traps an error, use the UNIX exit command ‘exit 1′ to return
failure (status code 1) to the concurrent manager running the program.”

Final Note of ‘fndcpesr’
fndcpesr is a standard utility available in $FND_TOP directory. Its mainly used by the application to parse arguments for shell scripts.