Skip to content

Requirements

The requirements are divided in the ones for the Output Engine server and the ones for the management server.

Hint - virus scanner

An active virus scanner may slow down the installation.

Requirements for the Management Server

On the management server, the modules for administrating the output devices (easyPRIMA) and the log data (SEAL Elastic Stack) will be installed. If the preconfigured Keycloak from SEAL Systems is used as OIDC identity provider, we recommend installing it on the management server, too.

Java

Several components on the management server require Java, not all of which you may need:

  • The Keycloak OIDC identity provider
  • Elastic Stack (provides its own Java, but also works with a pre-installed Java if JAVA_HOME is set)
  • JSAPcli (required for exporting queues from easyPRIMA to SAP)
  • The PLOSSYS OCON server for PLOSSYS 4
  • The Wildfly component in the easyPRIMA installation (e. g. for providing an IPP router for PLOSSYS 4)

All of these components support Java 11. If you need one of the components listed above, provide a Java 11 installation on the management server and set the JAVA_HOME environment variable accordingly.

Hint - Java installation

For detailed instructions on how to install Java and set the required environment variables, refer to SEAL Online Service.

The installation package for "OpenJDK 11" is available on the SEAL Systems delivery platform in the FM / Runtimes directory.

OIDC Identity Provider

An OIDC identity provider has to be installed. 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 or another OIDC identity provider to be used with SEAL Systems products, refer to the SEAL Interfaces for OIDC documentation.

User and Privileges (Management Server)

For installing the management server, administrator privileges are required.

Hint - user for easyPRIMA

For running easyPRIMA, we recommend using a separate user account (service user). This can be a local or a domain user. The password for this user must never expire.

Requirements for the Output Engine Server

On the Output Engine server, the modules for administrating and processing the jobs are installed.

Hint - cluster mode

In the cluster mode, all Output Engine servers belonging to the cluster have to be installed identically.

User and Privileges (Output Engine Server)

  • For installing the Output Engine server, administrator privileges are required. The Output Engine services are running under the seal user account which will be generated during the installation.

  • The PLOSSYS CLI commands for managing the services execute bash scripts. For this, the logged-on user has to be member of the sudoers list.

DNS Server

  • No DNS server is active on the server.

  • On RHEL, disable the DNSmasq service with:

    sudo systemctl stop dnsmasq

    sudo systemctl disable dnsmasq

MongoDB

MongoDB has to be installed prior to the installation of PLOSSYS Output Engine. We recommend to use MongoDB as of version 7.0.0. For how to install and configure MongoDB, refer to the SEAL-specific MongoDB documentation.

Hint - older versions

MongoDB 4.4.4 works with PLOSSYS Output Engine 6.0.0 but has reached its end of life date in February 2024. Refer to MongoDB Software Lifecycle Schedules.

Hint - cluster installation

In case of a cluster installation, we recommend installing and configuring MongoDB in a cluster before installing PLOSSYS Output Engine. For more information about the MongoDB installation, refer to the SEAL-specific MongoDB documentation.

SEAL NATS

The SEAL NATS message broker as of version 2.9.2 has to be installed on the Output Engine server before installing PLOSSYS Output Engine. For more information about the SEAL NATS installation, refer to the SEAL NATS documentation.

SEAL Logrotate

As of version 6.0.0, the seal-logrotate service is no longer included in the PLOSSYS Output Engine bundle. The service cleans up outdated log files to free up storage space and prevent performance and memory issues. You can run PLOSSYS Output Engine without Logrotate, but we strongly recommend to install it. When running a cluster, this should be done on each server. For more information, refer to SEAL Logrotate documentation.

Next Step

Continue with: Installation

Back to top