Skip to main content

Infrastructure prerequisites

The Runtime Manager service requires the following components to be set up before it can be started:
  • PostgreSQL - version 13 or higher for managing application data
  • MongoDB - version 4.4 or higher for managing runtime data
  • Redis - version 6.0 or higher (if required)
  • Kafka - version 2.8 or higher for event-driven communication between services
  • OAuth2 Authentication - Ensure a compatible OAuth2 authorization server is configured.

Dependencies

Change the application name

Default Value: application-manager -> must be changed to runtime-manager (valid for < 4.7.5 releases).Starting with 4.7.5 version this property is no longer needed.

Core service configuration

Database configuration

The Runtime Manager uses the same PostgreSQL (to store application data) and MongoDB (to manage runtime data) as application-manager. Configure these database connections with the following environment variables:

PostgreSQL (Application data)

MongoDB (Runtime data)

Redis configuration

Kafka configuration

Kafka connection

Kafka OAuth Authentication

Kafka OAuth authentication secures communication between services using the Kafka message broker. The client ID and secret are used to obtain an access token from the token endpoint.

Authentication configuration

OpenID Connect configuration

The service account configuration approach is deprecated but still supported for backward compatibility. In newer deployments, consider using the standard OAuth2 client configuration.

File storage configuration

S3-compatible storage is used for storing application files, exports, and imports. The Runtime Manager supports MinIO, AWS S3, and other S3-compatible storage solutions.

Ingress configuration

For exposing the Runtime manager service, configure public, admin and adminInstances ingress settings:
Note: Replace placeholders in environment variables with the appropriate values for your environment before starting the service.
Last modified on July 18, 2025