Tag: reference

[reference] MOPS 4.0 Reference / Binder Configuration File Format

Configuration file example config.json:

[reference] MOPS 4.0 Reference / Configuration Reference

The reference material below documents system configuration settings found in MOPS 4.0.

[reference] MOPS 4.0 Reference / Configuration Reference

Binder Settings These settings controls the Binder, our application that presents Help and Manuals pages. The syntax of the configuration file is described here: Binder configuration file.

[reference] MOPS 4.0 Reference / ENV File Format

The .env file in the Docker Compose context is used to define environment variables that can be referenced in the docker-compose.yml file, allowing configuration values such as ports, image versions, and other settings to be managed centrally and dynamically.

[reference] MOPS 4.0 Reference / Ingress Configuration File Format

Configuration file example:

[reference] MOPS 4.0 Reference / Manual JWKS Download

This document describes how to download and store a file containing the public keys of an OpenID Connect identity issuer.

[reference] MOPS 4.0 Reference / MOPS 4.0 Native Service Configuration

Overview Structure Below is a native service configuration file illustrated as a JSON diagram:

[reference] MOPS 4.0 Reference / MOPS 4.0 Reference

The documentation provided within this section is primarily targeted users that performs administrative tasks on the MOPS 4.0 system.

[reference] MOPS 4.0 Reference / CMS Condition Monitor Settings

Format Path Filename Purpose JSON ./conf/mops-cms-conditionmonitor/ config.json MQTT configuration JSON ./conf/mops-cms-conditionmonitor/ db-config.json Database configuration Configuration file example config.json:

[reference] MOPS 4.0 Reference / CMS Alert Manager Settings

These settings mainly involves CMS communication with other nodes using MQTT and connections to the alert database.

[reference] MOPS 4.0 Reference / CMS E-Mail Channel Service Settings

These settings involves SMTP and email connectivity.

[reference] MOPS 4.0 Reference / CMS Notification Service Settings

These settings controls how this service communicates with the event broker over MQTT and logging of notification.

[reference] MOPS 4.0 Reference / Directory Service Settings

This configuration controls database connections, security settings, MQTT messaging, HTTP server behavior, and logging outputs and levels for the Directory Service - the main backend service.

[reference] MOPS 4.0 Reference / Directory Data Service Settings

This configuration controls database connections, security settings, MQTT messaging, HTTP server behavior, and logging outputs and levels for the Directory Data Service.

[reference] MOPS 4.0 Reference / Excel Add in Service Settings

The configuration of the Excel Add-in service.

[reference] MOPS 4.0 Reference / PQIS Core Service Settings

This configuration controls database connections, security settings, MQTT messaging, HTTP server behavior, and logging outputs and levels for the PQIS Core Service.

[reference] MOPS 4.0 Reference / Event Broker Service Settings

These settings configure the event broker’s logging outputs (all logs to stdout and a file), define listeners for MQTT (port 1883) and WebSocket (port 9001) protocols using IPv4.

[reference] MOPS 4.0 Reference / General Settings

Format Path Filename Purpose JSON ./conf/general/ general-config.json Configuration of the Directory Service Configuration file example:

[reference] MOPS 4.0 Reference / KeyCloak Settings

Keycloak can handle identity and access management for MOPS 4.0 without need of Internet connection. KeyCloak settings configures this functionallity.

[reference] MOPS 4.0 Reference / Shell Service Settings

The configuration of the Shell service.