Kbase P39258: How to monitor execution progress of the AppServer's remote
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/27/2003 |
|
Status: Unverified
GOAL:
How to monitor execution progress of the AppServer's remote procedure
FACT(s) (Environment):
Progress 9.1x
FIX:
In the distributed environment such as with AppServer,
the execution of the procedures is tightly coupled and encapsulated
within the Progress session where they run. Once the remote procedure
is run on the AppServer, its execution starts in the separate session
and the client application has to wait for that request to finish.
Basically, there are two ways to invoke the procedure execution
on the AppServer: synchronous and asynchronous. The first
one causes that the client application waits until the remote procedure
finishes. The asynchronous run will start the execution on the AppServer
and return control immediately back to the client application, which will
then react upon receiving the PROCEDURE-COMPLETE event.
If one assume that the remote procedure execution
might take considerable amount of time, then RUN...ASYNCHRONOUS call
could be used. The procedure that was started that way could write some
information in the temporary log file about how much of the job has
executed so far.
When it is required to see that information from the client application,
one could call another procedure on the AppServer that would read in the
temporary log file and return its content or status back to the client
application.