Before you begin

You have created the runtime zip of your customization project. See Create a runtime zip

NOTE: In this procedure, the full name of the created runtime zip file is used. You can, however, rename the file to a shorter, simpler name once it is created. It can be much easier to manage a file renamed as myCust.zip than to use the default runtime zip file name!

Deployment options

There are two options for deploying the runtime:

• Use your web browser to navigate to the deployment page (typically located at http://my.server.com:6394/ua/r/admin/DeploymentApp) and upload the fjs-gbc-<version>.<suffix>-build<build>-customization_<customName>.zip file. This option is only available if you have access to the Deployment App.

• If the Deployment App is not accessible, you need to have console access to the server and a way to transfer the fjs-gbc-<version>[.<suffix>]-build<build>-customization_<customName>.zip file to the server. Once the file is on the server, you need to execute the following command from the server console to deploy the GBC:

$ gasadmin gbc --deploy fjs-gbc-<version>[.<suffix>]-build<build>-customization_<customName>.zip

Using the deployed customization

Once the GBC is deployed, you can render your application using the deployed GBC with the following URL:

http://my.server.com:6394/ua/r/<appName>?gbc=fjs-gbc-<version>[.<suffix>]-build<build>-customization_<customName>

Or you can set it as the default:

gasadmin gbc --default fjs-gbc-<version>[.<suffix>]-build<build>-customization_<customName>

The default GBC will be used if one uses no query string parameter, as in this example URL:

http://my.server.com:6394/ua/r/<appName>