Kbase 18918: Debugging Tips For Apptivity Deployment Issues
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
GOAL:
Debugging Tips For Apptivity Deployment Issues
FACT(s) (Environment):
Apptivity 3.x
Windows 32 Intel
Windows NT 32 Intel/Windows 2000
FIX:
1) Check if there are any errors in the browser's Java console when accessing the deployed application, or in the Distribution Manager or Component Manager output (in their respective console windows, or output files if output has been redirected).
2) Determine the deployment configuration. Is the application deployed to a web server on the same machine on which the browser is being run?
If the browser is run on the deployment machine, the browser will pick up the Apptivity runtime classes from the local classpath and these classes will not be downloaded from the web server. This should not cause errors but will not serve as a realistic deployment simulation.
For a realistic deployment environment test, the browser should be run from a machine that doesn't have Apptivity installed. If two machines are not available, open a DOS window on the machine where the application is deployed to the web server and use
SET CLASSPATH=
to unset the classpath.
Then launch the browser from the command line e.g.:
C:\Program Files\Netscape\Communicator\Program\netscape.exe
This will simulate a two machine deployment where the web server will serve the Apptivity classes.
3) Verify that the Distribution Manager and Component Manager have been started with -Dapptivity.dmanager.host=<deployment host name> and -Dapptivity.cmanager.host=<deployment host name>, respectively.
If these properties haven't been set, they default to "localhost". When accessing the application via a browser on another machine, a security error relating to "connecting from localhost" will be received.