Requirements¶
SEAL Systems recommends installing SEAL Operator on a separate server and not on the same server as the backend system. Also, SEAL Operator should not be installed on the management server on which easyPRIMA and Elastic Stack are running as another version of MongoDB is installed there.
Hint - active virus scanner
An active virus scanner may slow down the installation.
Server Requirements¶
User and Privileges¶
To install SEAL Operator, a user account with local Administrator privileges is required. By default, the SEAL Operator services are running under the Local Service system account.
If you want to manage SEAL Operator services via Operator CLI, privileges for executing PowerShell scripts are required. With the installation, the privileges are also required but can be specified explicitly then. The execution policy has to be set to RemoteSigned at least. For more information about execution policies, refer to the Microsoft documentation. To set the execution policy, open a new PowerShell (Administrator) and execute the following command:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
Hint - impermanent
The execution policy might be overwritten by a group policy.
No DNS Server¶
No DNS server is active on the server.
Microsoft C++¶
"Microsoft C++ 2015" Runtime is installed on the server.
Hint - installation package
The installation packages for "Microsoft C++ 2015" Runtime are available on the SEAL Systems delivery platform in the msvc2015 directory.
OIDC Identity Provider¶
An OIDC identity provider is installed. SEAL Systems provides a preconfigured Keycloak installer 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 detailed instructions regarding Keycloak or another OIDC identity provider to be used with SEAL Systems products, refer to the SEAL Interfaces for OIDC documentation.
MongoDB¶
MongoDB has to be installed prior to the installation of SEAL Operator. 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.
As of SEAL Operator 1.5.1 a replica set has to be configured in MongoDB and the database initiatlized. For more information refer to Configuring a Shared Replica Set and Initializing the Database.
When using MongoDB in a cluster, also refer to the required steps described in Connecting the Database Servers to the Cluster.
Hint - older versions
MongoDB 4.4.4 works with SEAL Operator 1.6.0 but has reached its end of life date in February 2024. Refer to MongoDB Software Lifecycle Schedules.
SEAL NATS¶
The SEAL NATS message broker as of version 2.9.2 has to be installed on the SEAL Operator server before installing SEAL Operator. For more information about the SEAL NATS installation, refer to the SEAL NATS documentation.
SEAL Logrotate¶
As of version 1.6.0, seal-logrotate is no longer included in the installation of SEAL Operator. Logrotate cleans up outdated log files to free up storage space and prevent performance and memory issues. We strongly recommend to install SEAL Logrotate separately, either before or after the installation of SEAL Operator. For more information, refer to SEAL Logrotate documentation.
Next Step¶
Continue with: Install SEAL Operator