Skip to content

Overview

Architecture Overview

Hint - PLOSSYS netdome/PLOSSYS 4

"PLOSSYS 4" and "PLOSSYS netdome" are used synonymously in the context of SEAL Operator.

Version

This documentation describes SEAL Operator 1.6.0.755.

Components of SEAL Operator

SEAL Operator includes the following components:

  • SEAL Operator

    Main application as server for the different connectors and different panels such as SEAL Print Client or Web Portal consisting of several microservices such as seal-operator-server, seal-operator-ui or seal-operator-fileupload

  • SEAL Print Client

    As Web user interface for creating output jobs, SEAL Print Client is provided as connector and panel for SEAL Operator.

  • Web Portal

    As Web user interface for digital distribution and secure sending of documents, Web Portal is provided as connector and panel for SEAL Operator.

  • Connector

    A connector establishes the connection between the SEAL Operator server and the backend system, for example, PLOSSYS Output Engine or SharePoint.

  • SEAL NATS

    For a better message handling, NATS has been introduced as message broker as of SEAL Operator 1.5.0. For this, a SEAL Systems-specific SEAL NATS package is available. For more information about SEAL NATS, refer to the SEAL NATS documentation.

  • Identity provider

    The identity provider is a service connected with the OAuth 2.0/OpenID Connect (OIDC) protocol. It is responsible for the user authentication and the mapping of rights and roles. A preconfigured Keycloak identity provider is provided by SEAL Systems for test purposes. In practice, another OIDC identity provider already installed at the customer's will be used for the user authentication and authorization. For more information about Keycloak and other OIDC identity provider used with SEAL Systems products, refer to the SEAL Interfaces for OIDC documentation.

  • Consul

    The Consul configuration service provides the system configuration in on-premise installations. It is used for discovering services via Domain Name System (DNS) and managing the distributed configuration in a cluster. In a cloud environment, the container orchestration system is used for this.

  • MongoDB

    The SEAL-specific MongoDB database contains the complete data such as documents, panels, tasks, user settings and so on.

    Hint - separate installation

    As of SEAL Operator 1.3.0, MongoDB is no longer included in the installation of SEAL Operator. For how to install and configure MongoDB, refer to the SEAL-specific MongoDB documentation.

  • Credential store

    The credential store administrates the user-specific credentials. In the standard installation, MongoDB is used as credential store. For how to change the token used for encrypting the credentials, refer to Change the Token for Encrypting the Credentials on Windows and Change the Token for Encrypting the Credentials on Linux.

  • SEAL Operator CLI

    With the command line tool, SEAL Operator CLI, the services of SEAL Operator can be managed and the configuration can be exported and imported.

  • SEAL OP-CLI

    With the command line tool, SEAL OP-CLI, the documents, tasks, panels and lists of SEAL Operator can be managed. For more information, refer to the separate SEAL OP-CLI documentation.

Used Software and Versions

SEAL Operator uses the following software:

  • Node 20.12.2
Back to top