Once your customization is ready, you need to build the GBC runtime that your BDL development team will be able to deploy on their development or production environments.

The command creates a zip file for the customization using the settings of the compile.mode and compile.customization parameters in <GBC_PROJECT_DIR>/custom.json. To produce a runtime package using the settings of the custom.json file, execute:

$ grunt --create-zip

You may wish to switch modes (cdev, dev, prod). To accomplish this, either change the compile.mode parameter in <GBC_PROJECT_DIR>/custom.json or use the --compile-mode option of the grunt command.

You may wish to switch customizations. To accomplish this, either change the compile.customization parameter in <GBC_PROJECT_DIR>/custom.json or use the --customization option of the grunt command.

This example specifies both the mode and customization:

grunt --customization=customization/myCustomization --compile-mode=prod --create-zip

The resulting runtime will be located in <GBC_PROJECT_DIR>/archive directory. It will be named fjs-gbc-<version>.<suffix>-build<build>-customization_<customName>.zip. This is a GBC runtime that you can deploy. You can deploy it in the same manner as you deploy the standard runtime provided by Four Js on our web site download center. See Deploy runtime with Portal.

By default, the customization suffix is "c". To change the suffix used for a customization, see Change the version customization suffix

NOTE: You can rename this file to any name that suits you.