Deploy GBC client with deployment portal

Use this procedure when you need to deploy a customized Genero Browser Client on your Genero Application Server using the deployment portal.

As a prerequisite, you have a compiled version of the GBC front-end in a zip file. See Create zip file with customization project.

The deployment portal provides you with a user interface to the action to deploy implemented by the gasadmin gbc command. The zip file is unpacked in the $(res.gbc.deployment) path, which resolves to the $(res.appdata.path)/gbc_deployment directory.
Tip: As an alternative to the deployment portal, you can deploy the GBC using the gasadmin gbc command with the deploy option. For an example see Deploy GBC.
  1. Open the deployment portal page.
    For example, on your local machine enter this URL in your browser: http://localhost:6394/ws/r/services/DeploymentService/html.
    Note: This example assumes the standalone dispatcher on your GAS installation is already started on you local machine at the default port number.
    On a remote machine, you need to specify the appropriate URL for the server and port in your browser, for example: http://zeus:8090/ws/r/services/DeploymentService/html.
    Note: This example assumes you have explicitly configured the remote server's GAS configuration's ALLOW_FROM element with details to allow access from your machine.
  2. Scroll to the Deploy a new Genero Browser Client section.
  3. Select the Choose file button to open a system dialog screen.
  4. Locate the client you wish to deploy (it must be in a zip file) using the dialog to upload it.

    Once the file is uploaded, its name is displayed to the right of the Choose file button.

  5. To deploy it, click on the Deploy button.

    The new client is deployed and is displayed in a row of the table.

What to do next

If you wish to set this as the default client, see the procedure detailed in Set default GBC client with deployment portal.