Overview

The Device Portal consists of the following docker images.

Docker Image	Description	Required
idm/idm-device-administration-app	This service manages the commands which are used for device interaction.
idm/idm-software-management-app	This service replicates software meta-data from supported software repositories.
idm/idm-device-monitoring-app:	This service manages the monitoring / status data of the registered devices.
idm/idm-device-master-data-mgmt-app	This service manages the master data of the registered devices and machines.
idm/idm-device-app	Backend for frontend which provides access to selected features of Device Portal to devices.
idm/idm-solution-app	Backend for frontend, which provides access to selected features of Device Portal to other solutions.
idm/idm-webapp-backend	This service contains the Device Portal UI and triggers the user authentication/authorization against CIAM/MACMA. It is the entry point for human users.
idm/idm-device-tunnel-app	This service provides remote access to devices via a WebSocket connection. Authorized users are able to connect to their devices from the Device Portal UI.
idm/idm-artifact-repository-app	This service manages the artifacts (software, setup files, …) which are used by the devices. It is deployed as part of the Device Portal in form of a "Managed Artifact Repository" which supports multi-tenancy. Customers can instead/in addition operate their own "Private Artifact Repository" instance in the cloud.
bci-app/opensearch:2.19.3	OpenSearch cluster which holds the master data and status data of the devices in order to have fast response times for device data retrieval.
bci-app/opensearch-dashboards:2.19.3	This application is used to visualize Data stored in OpenSearch - mainly for 3rd-level support scenarios.
bci-app/valkey:7.2.8	This application provides a managed in-memory data store service.
bci-app/nginx:1.29.0	This application - which is used only in the cloud deployment - holds whitelisted CA certificates for device authentication and routes the device requests from the cloud-independent device endpoint to the Device BFF (idm-device), the Device Tunnel (idm-device-tunnel) or the Managed Artifact Repository (artifact-repository).
bci-kube/nexeed-ansible-operator:1.8.2	The contained jobs - which are used only in the cloud deployment - automatically rotate the TLS session resumption ticket encryption keys used to create the TLS session tickets. TLS session resumption encryption keys are used by the bci-app/nginx docker image.

Docker Image

Description

Required

idm/idm-device-administration-app

This service manages the commands which are used for device interaction.

idm/idm-software-management-app

This service replicates software meta-data from supported software repositories.

idm/idm-device-monitoring-app:

This service manages the monitoring / status data of the registered devices.

idm/idm-device-master-data-mgmt-app

This service manages the master data of the registered devices and machines.

idm/idm-device-app

Backend for frontend which provides access to selected features of Device Portal to devices.

idm/idm-solution-app

Backend for frontend, which provides access to selected features of Device Portal to other solutions.

idm/idm-webapp-backend

This service contains the Device Portal UI and triggers the user authentication/authorization against CIAM/MACMA. It is the entry point for human users.

idm/idm-device-tunnel-app

This service provides remote access to devices via a WebSocket connection. Authorized users are able to connect to their devices from the Device Portal UI.

idm/idm-artifact-repository-app

This service manages the artifacts (software, setup files, …) which are used by the devices. It is deployed as part of the Device Portal in form of a "Managed Artifact Repository" which supports multi-tenancy. Customers can instead/in addition operate their own "Private Artifact Repository" instance in the cloud.

bci-app/opensearch:2.19.3

OpenSearch cluster which holds the master data and status data of the devices in order to have fast response times for device data retrieval.

bci-app/opensearch-dashboards:2.19.3

This application is used to visualize Data stored in OpenSearch - mainly for 3rd-level support scenarios.

bci-app/valkey:7.2.8

This application provides a managed in-memory data store service.

bci-app/nginx:1.29.0

This application - which is used only in the cloud deployment - holds whitelisted CA certificates for device authentication and routes the device requests from the cloud-independent device endpoint to the Device BFF (idm-device), the Device Tunnel (idm-device-tunnel) or the Managed Artifact Repository (artifact-repository).

bci-kube/nexeed-ansible-operator:1.8.2

The contained jobs - which are used only in the cloud deployment - automatically rotate the TLS session resumption ticket encryption keys used to create the TLS session tickets. TLS session resumption encryption keys are used by the bci-app/nginx docker image.