Requirements¶
The requirements are divided in the ones for the PLOSSYS 5 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.
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 PLOSSYS 5 Server¶
On the PLOSSYS 5 server, the modules for administrating and processing the jobs are installed.
Hint - cluster mode
In the cluster mode, all PLOSSYS 5 servers belonging to the cluster have to be installed identically.
User and Privileges (PLOSSYS 5 Server)¶
-
For installing the PLOSSYS 5 server, administrator privileges are required. The PLOSSYS 5 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 as of version 4.4.4 has to be installed.
Hint - separate installation
As of PLOSSYS 5.3.2, MongoDB is no longer included in the installation of PLOSSYS 5. For how to install and configure MongoDB, refer to the SEAL-specific MongoDB documentation.
Hint - cluster installation
In case of a cluster installation, we recommend installing and configuring MongoDB in a cluster before installing PLOSSYS 5. 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 PLOSSYS 5 server before installing PLOSSYS 5. For more information about the SEAL NATS installation, refer to the SEAL NATS documentation.
Next Step¶
Continue with: Installation