How the GAS finds the default GBC client to use

If an application has not requested a specific GBC client, a default GBC client is used. A file named _default is the mechanism used to specify the default GBC client for all users.

In this _default file, there is a single line that has the name of one GBC client.

When the application launches, the GAS searches the directories specified by GBC_LOOKUP_PATH. When it finds the _default file, it reads its contents to find the name of the GBC client to use. There may be multiple _default files across various directories; the first occurrence found is used. See Finding the GBC client for more information about GBC_LOOKUP_PATH and the directories involved.

While you can edit the _default file directly, it is recommended you use the Deployment App to specify the GBC client for a GAS. When you specify a default client using the Deployment App, it updates the _default file for you. If you do not have the Deployment App set up, you can use the gasadmin tool to update that same _default file.
Tip:

A GAS restart is not required when you update the _default file.

Finding the GBC client

To find the GBC client, the GAS looks at the paths defined by the GBC_LOOKUP_PATH environment variable. The value of GBC_LOOKUP_PATH is set by the GAS configuration file (as.xcf). By default, it will look in these directories, in this order:
  • 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 set res.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.
Important:

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.