Service overview
The services, or background services, are essential to the application’s functionality. This overview not only provides a quick insight into the current status but also serves as a starting point for analysis should a problem arise. Generally speaking, each service runs in its own Docker container.
Name | Task |
|---|---|
codemeter | Container containing a service from Wibu Systems. This checks the licence against the system’s hardware environment. |
configurator | The Master Service is responsible for monitoring the services, particularly during updates. |
datawriter | Receives data and writes it to the database |
edifact | This service monitors a folder, reads the files and passes the data – e.g. MSCONS data – to the datawriter. |
excelwcf | Provides WCF functionality for external programs. |
licence | This container reads the codemeter licence information and publishes it so that other modules can use the licence information. |
limitation | This service limits the size of the database by deleting various system-generated data at regular intervals. Currently limited data:
|
logger | This service receives log entries, thereby enabling centralised logging. |
maintenance | When enabled, this service collects system information and, for customers with a service contract, can send this information to KBR at regular intervals for system monitoring purposes. |
mobile | Service for the mobile web application |
monitoring | This service monitors objects and, if necessary, sends a notification by email. Objects currently being monitored:
|
proxy | A central reverse proxy based on nginx, which resolves the URLs and forwards the requests to the individual containers or services. |
queryBusmaster | This service retrieves from the database all metering point measured variables for which the data request is enabled. The data request can be enabled or disabled at the metering point (list of measured variables). The data requests are sent via RabbitMQ to the workflow service, which then executes them. This service also receives the data sent by the Busmaster via RabbitMQ:
|
rabbitmq | RabbitMQ is what is known as a message broker – in other words, software that relays messages between different applications or services. Among other things, this service facilitates communication between the services. RabbitMQ uses the AMQP and MQTT protocols. |
schedule | This service retrieves the schedules from the database and publishes their executions to the other services. |
structuralcalculation | This service calculates the structural data for all media. The term “structural data” refers both to the system metering points of distributions and location media, and to the data relating to allocation objects. The commands for performing the calculations are sent via RabbitMQ to the workflow service, which then executes them. |
transformation | This service performs data compression. The transformations and the data retention periods can be edited in visual energy Web via the project properties. The commands for performing transformations or limiting the data are sent via RabbitMQ to the workflow service, which then executes them. |
web | The web service that hosts the website. |
workflow | This service receives commands (schedules, triggers and workflow assignments) and executes the corresponding workflows. |
LED colour indicator
Colour value | Process or service | Event |
|---|---|---|
Black / Grey | No current information. Target unavailable or cannot be reached. | No events |
Red | Stopped or terminated. | Error |
Yellow | - | Warning |
Green | Started and available. |
|