/
Application Provider

Application Provider

May 07, 2025

Via the Application Management functionality, Application Developers can provide Edge Applications (Apps) for the Machines of Operators for specialized workloads. Apps - in this context - are a collection of Docker Containers that run on the Edge Device assigned to a Machine. This document describes how an App Developer can provide an App via the Hub.


The App providing process is split into the following chapters:

  1. Application Development

  2. Application Upload and Registration

  3. Availability Management (see below)

When an App has been uploaded, registered and made available, an Operators can install an App.  For the Application installation process, please click here.



Application Availability Management

After a new Application (version) is uploaded and registered, it appears in the Manage Applications overview of the Hub for users with the App Developer role. By default, the version of the App is in the PUBLISHED state. Therefore, it is directly visible and installable to your customers if it is either marked as public or provided via the compatibility mechanism (see below).

Public Application Mechanism

When an Application is marked as "public" in the App Definition and the Application is published, it is visible for any tenant on the symmedia Hub and installable for every Operator-licensed Asset. The "public" flag is managed on Application level and can be overwritten by registering a new Version for the App. For Assets that are licensed by the Service Provider, the compatibility mechanism is used to manage Application availability. All Applications in the "published" state that are available to the public are visible to all Service Providers and can be defined as compatible for their Machine Models.

Compatibility Mechanism

Service Providers can enable their customers to install Applications that have been marked as compatible to their machines.



Display of App title, state, description and App image.

When an Application is marked as and the Application is published, it is visible for any tenant on the symmedia Hub and installable for every Operator-licensed Asset.

For Assets that are licensed by the Service Provider, the compatibility mechanism is used to manage Application availability. All Applications in the "published" state that are available to the public are visible to all Service Providers and can be defined as compatible for their Machine Models.

List of Application versions with information about:

  • Search for a certain version within the list of Application versions using the filter button and typing a version into the search field.

  • Sort the list of Application versions by using the buttons in the top row.
  • Filter the list of Application versions for the states "Disabled" or "Publish" via the filter button .

  • Customize the displayed columns by clicking on .
    • Check the entries from the list of columns to be displayed in the overview.
    • Align the sequence of the entries by dragging & dropping the entries in your desired order.

The selections will be permanently stored for your user and can be reset to factory setting by clicking .

  • Click to change the state of the respective App version:

    • NEW

    • PUBLISHED

    • DISABLED

NEW

...coming soon.

PUBLISHED

Once a version is published, it can be viewed and installed by the Operator. An additional requirement is that the application version is made available to the Operator.

DISABLED

Versions that are outdated and should no longer be installed can be deactivated. It can and will happen that there are still installations with a deactivated version. These installations can still be updated with the same version (e.g. for a configuration update). These installations will still be visible to the operator. For new installations, disabled versions cannot be selected.

Application State Calculation by Version States

The state of the entire application is calculated from the version states. When a version is published, the entire application is automatically set to PUBLISHED and is visible to other tenants. If there is no published version, the state changes to DISABLED. Once an application state has left the NEW state, it can't return to NEW. If an application is new and disabled and has no published versions, the state is displayed as DISABLED. Once any version is set to published, the state of the application changes to PUBLISHED.

Looking for labels? They can now be found in the details panel on the floating action bar.

Related content