App Management

The App Management API provides a way to manage Glue42 Enterprise apps. It offers abstractions for:

• App - a program as a logical entity, registered in Glue42 Enterprise with some metadata (name, description, icon, etc.) and with all the configuration needed to spawn one or more instances of it. The App Management API provides facilities for retrieving app metadata and for detecting when an app is started.

For details on how to define and configure an app, see the App Configuration section.

• Instance - a running copy of an app. The App Management API provides facilities for starting and stopping app instances and tracking app-related events.

Glue42 Enterprise can obtain app configurations from a local store, from a remote REST service, or from a Glue42 Server. The settings for the app configuration stores are defined in the system.json file of Glue42 Enterprise located in %LocalAppData%\Tick42\GlueDesktop\config, under the "appStores" top-level key, which accepts an array of objects defining one or more app stores.

In the standard Glue42 Enterprise deployment model, app definitions aren't stored locally on the user machine, but are served remotely. If Glue42 Enterprise is configured to use a remote app store, it will poll it periodically and discover new app definitions. The store implementation is usually connected to an entitlement system based on which different users can have different apps or versions of the same app. In effect, Glue42 Enterprise lets users run multiple versions of the same app simultaneously and allows for seamless forward/backward app rolling.

Note that Glue42 Enterprise respects the FDC3 standards and can retrieve standard Glue42, as well as FDC3-compliant app definitions. For more details on working with FDC3-compliant apps, see the FDC3 Compliance section, the FDC3 App Directory documentation and the FDC3 Application schema.

Local

To configure Glue42 Enterprise to load app configuration files from a local path, set the "type" property of the app store configuration object to "path" and specify a relative or an absolute path to the app definitions. The environment variables set by Glue42 Enterprise can also be used as values:

{
    "appStores": [
        {
            "type": "path",
            "details": {
                "path": "../config/apps"
            }
        },
        {
            "type": "path",
            "details": {
                "path": "%GD3-APP-STORE%"
            }
        },
        {
            "type": "path",
            "details": {
                "path": "%GLUE-USER-DATA%/apps"
            }
        }
    ]
}

Each app store object has the following properties:

The "details" object for a local path app store has the following properties:

Remote

App configurations can also be obtained from remote app stores via a REST service.

For a reference implementation of a remote app configurations store, see the Node.js REST Config example that implements the FDC3 App Directory and is compatible with Glue42 Enterprise. This basic implementation doesn't take the user into account and returns the same set of data for all requests. For instructions on running the sample server on your machine, see the README file in the repository.

For a .NET implementation of a remote app configurations store, see the .NET REST Config example.

To configure a connection to the REST service providing the remote app store, add a new entry to the "appStores" top-level key of the system.json file and set its "type" to "rest":

{
    "appStores": [
        {
            "type": "rest",
            "details": {
                "url": "http://localhost:3000/appd/v1/apps/search",
                "auth": "no-auth",
                "pollInterval": 30000,
                "enablePersistentCache": true,
                "cacheFolder": "%LocalAppData%/Tick42/UserData/%GLUE-ENV%-%GLUE-REGION%/gcsCache/"
            }
        }
    ]
}

Each app store object has the following properties:

The "details" object for a remote app store has the following properties:

The remote store must return app definitions in the following response shape:

{
    "applications": [
        // List of app definition objects.
        {}, {}
    ]
}

Glue42 Server

You can also use the Glue42 Server for hosting and retrieving app stores. The Glue42 Server is a complete server-side solution for providing data to Glue42. To configure Glue42 Enterprise to fetch app configurations from a Glue42 Server, set the "type" property of the app store configuration object to "server":

{
    "appStores": [
        {
            "type": "server"
        }
    ]
}

Each app store object has the following properties:

If you are using only a Glue42 Server for retrieving app configurations, you can set the "appStores" key to an empty array. Glue42 Enterprise will automatically try to connect to the Glue42 Server using the configuration for it, and will retrieve the app configurations from it, if any.