Step 1:
Place the <name>.prog script under the bin directory for your applications top directory.
For example, call the script AD_DEMO.prog and place it under $CUSTOM_TOP/bin
Step 2:
Make a symbolic link from your script to $FND_TOP/bin/fndcpesr
For example, if the script is called AD_DEMO.prog use this:
ln -s $FND_TOP/bin/fndcpesr AD_DEMO
This link should be named the same as your script without the .prog extension.
Put the link for your script in the same directory where the script is located.
Step 3:
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.
For the example above:
Use AD_DEMO
Step 4:
Your script will be passed at least 4 parameters, from $1 to $4.
$1 = orauser/pwd
$2 = userid(apps)
$3 = username,
$4 = request_id
Any other parameters you define will be passed in as $5 and higher.
Make sure your script returns an exit status also.
Place the <name>.prog script under the bin directory for your applications top directory.
For example, call the script AD_DEMO.prog and place it under $CUSTOM_TOP/bin
Step 2:
Make a symbolic link from your script to $FND_TOP/bin/fndcpesr
For example, if the script is called AD_DEMO.prog use this:
ln -s $FND_TOP/bin/fndcpesr AD_DEMO
This link should be named the same as your script without the .prog extension.
Put the link for your script in the same directory where the script is located.
Step 3:
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.
For the example above:
Use AD_DEMO
Step 4:
Your script will be passed at least 4 parameters, from $1 to $4.
$1 = orauser/pwd
$2 = userid(apps)
$3 = username,
$4 = request_id
Any other parameters you define will be passed in as $5 and higher.
Make sure your script returns an exit status also.
No comments:
Post a Comment