Which GBC client is used for an application?

As an administrator, you have options for specifying which GBC client an application uses. You can specify a default application to use for all GBC clients, and you have several options for overriding the default at the application level.

Set a default GBC client for all applications to use

The GAS uses two items to identify the default GBC client:
  • The GAS looks for a file named "_default", which contains the name of the GBC client to be used as the default. Once this file is located, it is read to identify the name of the GBC client to use.
  • The GBC_LOOKUP_PATH environment variable defines the search path used to find the _default file.

To go into deeper detail, see How the GAS finds the default GBC client to use.

To change the name of the GBC client in the _default file, you do not need to edit the file directly.

To reset the default GBC client to the GBC delivered with the FGLGWS package, see Reset GBC client to use version provided by the FGLGWS package

Specify a GBC client for a specific application

For an application, there are three methods for overriding the GAS default and specifying a GBC client to use, listed below in order of precedence:
  1. A client is provided at appdir/gbc in the application path. See Provide the GBC in the application path.
  2. A client is specified using the ?gbc=gbc_name query string parameter. See Specify the GBC client in the application URL.
  3. A client is specified by the <GBC> element in the application configuration file (.xcf). See Specify the GBC client in the application configuration file.

Test the GBC client you are currently developing

When in development mode, you may wish to test your customized GBC client without deploying it. You can override the GAS dispatcher to use your customized client as it is being developed, without having to move it from your GBC project directory. See Test a GBC client during development.