Configure for GBC development and troubleshooting

Configure a development environment to troubleshoot an Genero Browser Client (GBC) application.

To troubleshoot and debug an application, you may need to view the application log files and the AUI tree. To make these items available, configure the GAS to launch the GBC applications in debug mode.

This procedure will cause all applications to launch in debug mode. To launch a specific application in debug mode, add the query string parameter debugMode=1 to the application URL. For example: http://localhost:6394/ua/r/HelloWorld?debugMode=1. This debug method can be useful when you just want to troubleshoot one application. For more information on this method, see URI Examples.

Warning:

The --development option forces the GBC into debug mode. This may effect the behavior of the GBC in the browser. For example, the prompt that usually displays when the user presses the browser's back button is no longer displayed:

Are you sure you want to leave this page?

In the GAS configuration file (default $FGLASDIR/etc/as.xcf), change the res.uaproxy.param resource:
From:
```
<RESOURCE Id="res.uaproxy.param" Source="INTERNAL"></RESOURCE>
```
To:
```
<RESOURCE Id="res.uaproxy.param" Source="INTERNAL">--development</RESOURCE>
```
Tip:
Alternatively, you can run the dispatcher from the command line and override the settings in the GAS configuration file for res.uaproxy.param. For example: httpdispatch.exe -E res.uaproxy.param=--development
Restart the dispatcher.
The dispatcher must be restarted whenever you modify the application server configuration file in order for the changes to take effect.
Enter the application URL in your browser.
You now see the Debug Tools icon (next to the close application icon) on the right-hand side of your web application window. For more information, see the Genero Browser Client User Guide.