Configuring O4W to run in Debug mode [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Configuring O4W to run in Debug mode ======

===== Registry Setup =====

The Debugger requires desktop interaction, O4W does not.  It is necessary then to have O4W run in desktop mode.  Two changes need to be made to the Registry Key for the O4W application that is in use.  StartUpFlags should be set to the value of 1.  ShutdownFlags should be set to the value of 1.

This change to the registry settings causes the OEngineServer to create visible engines on the desktop, instead of invisible engines that have no desktop interaction.  

===== Running the OEngineServer in Manual Debug Mode =====

If you are running the OEngineServer as a service, stop the service.  From the command prompt locally on the system that you are testing/developing on (of course this also means that this has to be the system where OpenInsight is installed), manually start the engineserver: java –jar oesocketserver.jar –d 3

Now, if a debug statement is encountered, or any error occurs that would invoke the debugger, the debugger will start up in a visible mode.