Professional Documents
Culture Documents
Creating A Java Based Concurrent Program in Oracle Apps R12 PDF
Creating A Java Based Concurrent Program in Oracle Apps R12 PDF
R12
Steps to create a Java Concurrent Program – Overview
• Create a Java file containing the Business logic and Then compile it to
generate the class file through Jdeveloper.
• Under which the java class file would be stored, in this case, the package
is “ktpl.oracle.apps.per.expense”. Once the hierarchy is
• created, right click on the latest folder, e.g., expense, and click on
“New”, goto “Java” tab and click on “Java class”.
• This will create a new class with the name provided, and under that
package.
Why Java Concurrent Program?
• Now suppose, we have to do the same for all the employees, say 500
and mail the reports to the respective employees. We’ll have to run this
concurrent program 500 times, explicitly? Solution? Simple. Java
Concurrent Program comes into the picture. Where we would loop
through all the employees and generate the report 499 times more but
submitting the Java Concurrent Program through Oracle Apps just once.
• Let’s us get deeper into this on how to achieve this using a Java
Concurrent Program.
• To make this Java class file accessible and executable from Oracle apps,
you have to implement the “JavaConcurrentProgram” interface.
In the executable, we provide the regular details like name, short name,
application name, the execution method: “Java Cocurrent Program”
The execution file name is the name of the class file we just created.
Execution File path, is the path where the file has been placed in the
server, to be specific, under $JAVA_TOP.
Based on the executable just created, create a concurrent program.
The most important part to be noted here is the “Options” where we are
putting something like: -classpath
/orab/VIS/apps/apps_st/comn/java/classes:/orab/VIS/apps/apps_st/c
omn/java/classes/*:/usr/tmp/*:/orab/VIS/apps/apps_st/appl/au/12.0
.0/java/appsborg.zip
This is nothing but we are telling the program to find all the libraries and jars in
the above. The location is custom, it can be anywhere in the server. Well, one
thing, the no. of characters to be filled in this box is limited. So, like always for
multiple, long and broad named jar files “*” works. Like in this case we have
kept our libraries and jars under “/usr/tmp”.
So first the concurrent program gets submitted and which in turn submits
another report program and params being derive programmatically.
Thanks!