• An Edge app is created.
  • An Application version is added.
  1. Open the App and select the App version you want to configure.
  1. Click Options > Open.
  1. Go to the Definition tab.

Entries in Settings section are optional. The red asterisk next to Services indicates that entries in Services section are mandatory.

  1. In Settings section, you can define Allowed ports and Properties. You can also add one or multiple Tunnel for remote access to the app that is installed on the gateway. This enables remote engineering of the app
  1. In Services section, click Add service.
  • New service options appear.
  1. Enter the Basic information of the service.
  • Enter Display name that is visible in local gateway UI.
  • Enter the display name also in the Devices application in Services tab.
  • Enter Image and Image tag.

Currently, version 1.0.0 of the Image registry.horizonint.cloud/gw-bif/gw-reference-app is available.

  1. Select the Network. The Network depends on the number of services you intend to add.
  • If you want to add only 1 service select Network mode host. The port of the container is directly mapped to the host. If you want to add 2 more services, select Network mode default. This mode requires defining the port mapping for the gw-reference-app. Source is always 9000. Target must be unique for each service you want to create, e.g., 9001, 9002, 9003…
  1. (Optional) Enter Volume:
  • While configuring services under an Edge app, the developer can enable either / both of Data and Settings volume for the service.
  • Enabling a volume for a service requires the /target as input. This is the path within the container where the volume will be mounted at.
  • These volumes are created at the application level and mounted to a service. If the same volume is enabled for multiple services within an app, they all share the same volume. This was done by design, due to a working assumption that developer would have control over all services being included in an Edge app and that there would be no concern if services of an app would share the same volume.
  • On enabled volume, valid target MUST be provided.
  1. (Optional) Additional volumes:
  • A developer can choose to define additional custom volume for a service, whereby the name of the volume, its target mount path has to be specified.
  • Developer can define multiple such custom volumes for a service, each of which would be identified by the name given to them.
  • If multiple services have a custom volume with the same name, then the custom volume is shared across the said services.
  • To conform to the original concept, the actual volume on the Edge device is created with the name of the app prefixed to it.
  • The original Settings & Data volumes are still available for the services along with any custom volumes that may have been defined.
  1. (Optional) Environmental variables:
  • Enter the key and value of the environmental variables.
  • Click Add to enter additional variables.
  1. (Optional) Setup:
  • Enter the maximum resources that the service can use.
  1. Click Add to confirm.
  1. Go to Open Source software license and fill in the according field.
  1. Go to Release notes and fill in the according fields.

Release notes and Open Source software license mandatory for release.
Uploading OSS license files

  1. Click Update to confirm.
  • The app is configured.