Provide GBC in application path

Describes a method for providing a GBC client in your application path.

Before you begin

You created a customization project and you have a compiled version of the GBC front-end. See the Genero Browser Client User Guide.

About this task:

In this task you provide the GBC to use with your app in the gbc directory of the application path. Regardless of the GAS configuration, the application will use the GBC inside that directory.

If the gbc directory is not set, the GAS then uses the standard GBC_LOOKUP_PATH lookup mechanism.

Follow these steps to provide the GBC in the application path.

  1. Create an empty directory, named gbc in your application root directory.
    For example, in your myapps/special/app1/gbc directory.
  2. Copy your GBC to this directory.
  3. In the application configuration file, specify the application path in the PATH element.
    For instance:
    <?xml version="1.0" encoding="UTF-8" ?>
    <APPLICATION Parent="defaultgwc" xmlns:xsi="" 

    At application startup, the GAS looks for the GBC in the gbc directory.

  4. To test, save the configuration file in a GAS application group directory.

    You can save the xcf in the default application group, $(res.appdata.path)/app, directory, or in your own defined group. Alternatively, you can deploy the app.

  5. Test the application opens with the GBC as expected.
    View an application in your browser by starting the standalone dispatcher from the command line. Open the application by entering the URL, for example:
    Click on the Application information menu icon to open the Product identification pop up window. Details of the GBC in use are displayed.

If the application fails to load, see the Fix configuration issues page of the Genero Browser Client User Guide.

For production environments, it is recommended to deploy the GBC and set the default client on your GAS installation using one of the following methods: