The system architecture is designed to be completely distributed and scalable, capable of executing in both private and public clouds and using Kubernetes for clustering.

Development and Operation APIs

User Interfaces

User Interfaces (3.1)

There are five different user interfaces:

Desktop Client, available as a local client, which is designed to be used by the solution designer. See Desktop Client User Interface (3.1)

Note!
In this documentation, the name ‘desktop’ refers to Desktop Client.

Web Desktop, available in a browser, which is designed to be used by the solution designer. See Web Desktop(3.1)
Web Interface, is designed to be used for execution, scaling, monitoring, logging, and troubleshooting. See Web Interface(3.1)
Desktop Online, is opened in a browser. It offers a mix of the same functionalities as the Desktop Client and the Web Interface. It also offers an exclusive functionality, the Archive Inspector. See Desktop Online User Interface (3.1).
Command Line Tools, see Command Line Interfaces(3.1)

Zones

Architecturally, Usage Engine is comprised of three Zones.

Control Zone, also called Platform
Execution Zone
Access Zone

The Zones are used for different purposes. The Control Zone is used to control the platform and is intended for Administrators. The Execution Zone is where the various configured workflows are executed according to what has been configured by the end users (via the Access zone). The Control Zone contains the Platform and the Database.

Container Orchestration

The container orchestration is done through Kubernetes using the REST interface.

The Kubernetes operator enables you to setup a dynamic cluster that can scale up or down automatically by using:

Configurable monitoring and triggers
Configurable conditions
Configurable commands

This is done using Execution Context Deployments (ECDs) (3.0).

Container HTTP API

A HTTP API is provided for transferring files between containers.

External References

Profile that allows you to use configuration values that originate from property files or exported environment variables.

Monitoring APIs

The architecture uses best-of-breed industry standards for non-core functions like logging, monitoring, and alarming.

The APIs are standardized; JSON for logs and events, and REST or JMX for metrics.

The Events are filtered in the Event Manager, and apart from sending them to a database, or as a mail or SNMP Trap, you can also send them to System Log.

Lifecycle Management

In order to provide for Life Cycle Management that ensures repeatability and minimizes human errors and downtime for operational procedures like; deploying and updating use cases, scaling and upgrading, the following is included:

Deployment using Helm and Docker repositories, see Installation - Private Cloud(3.0) and Installation - AWS(3.0)
EC Deployment interface for use case depleoyment, see Execution Context Deployments (ECDs) (3.0)
Automatic scaling, see Execution Context Deployments (ECDs) (3.0)
Custom healing, see Workflow Types (3.0)

System Overview (3.1)