Specify the GBC client in the application URL
For a single application, you can specify the GBC client to use in the URL query string
(?gbc=deployed-gbc-name
).
http://myApplicationServer:6394/ua/r/gwc-demo?gbc=my-gbc
Finding the GBC client
- If the GAS was started with a dispatcher override that sets
res.path.gbc.user
to a directory, this directory is searched first. Using a dispatcher override to setres.path.gbc.user
is a convenience intended for testing and development. Its use is not recommended for production sites. - Next, the directory specified by the
res.gbc.deployment
resource in the GAS configuration file (as.xcf). This resource defines the GBC deployment directory for the GAS. - Finally, the GBC folder in the FGL program directory. The GAS configuration file identifies this
folder as
$(res.fgldir)/web_utilities/gbc
.
While it is possible to add paths to GBC_LOOKUP_PATH, it is recommended that you do NOT modify the value for this environment variable. If you deploy the GBC clients using either the Deployment App or the gasadmin deployment mechanism, your GBC clients will be in the correct location.
Next steps
Once you have completed your configuration, you can verify that the correct GBC client is used. Enter the application URL in a browser; this example uses the local standalone dispatcher:
http://localhost:6394/ua/r/myapp.
To find out which GBC client is being used, click on the Settings icon. In the dialog that opens, the version information is displayed. It contains the GBC version number appended with the customization suffix defined in the GBC customization being used. It also provides the build timestamp of the customization package.
If your application does not load, the issue may be with your customized GBC runtime package. See topics such as Fix configuration issues in the Genero Browser Client User Guide.