I have already spoken about the technical components of an executable such as the changes around the server and sql side. This entry is going to be more around the functional setup required for the process. How, though does Oracle see the program and allow the end user to make the most of it?
The first step is to register the program within the concurrent program executable definition screen which is in the Application developer responsibility. This screen (as shown below) will allow for the executable to be visible within Oracle.
in the screen above the key fields are the Execution Method (which should match the form of the code on the server be it an oracle form, pl sql, package) , the execution file name (which should match the name of the file on the server) and the application (which should match the name of the application that the file/package etc is stored on). For example if your code was on the $GL_TOP directory on your server, the application would be General Ledger. The naming is critical as to whether or not the code will be found and executed!
The next part will be to register the actual concurrent program, complete with the parameters. This is the component which has the most visibility to the outside world in that it is what they will see when they run the file. However, it also contains additional information including the print style etc that is of little use to users but can potentially impact on the program. That whole application process will be the next post.
The first step is to register the program within the concurrent program executable definition screen which is in the Application developer responsibility. This screen (as shown below) will allow for the executable to be visible within Oracle.
in the screen above the key fields are the Execution Method (which should match the form of the code on the server be it an oracle form, pl sql, package) , the execution file name (which should match the name of the file on the server) and the application (which should match the name of the application that the file/package etc is stored on). For example if your code was on the $GL_TOP directory on your server, the application would be General Ledger. The naming is critical as to whether or not the code will be found and executed!
The next part will be to register the actual concurrent program, complete with the parameters. This is the component which has the most visibility to the outside world in that it is what they will see when they run the file. However, it also contains additional information including the print style etc that is of little use to users but can potentially impact on the program. That whole application process will be the next post.
No comments:
Post a Comment