Requirements
Hardware Requirements
The hardware requirements represent minimum values and are only intended as a guide for starting the system. The actual use of the software requires considerably higher capacity and a modification of the hardware. You need to do some scaling and performance tuning, regarding that you will get proper guidance from “ KOBIL Professional Services” team.
- Intel Pentium Core 2 Duo 2.5 GHz
- 4 GByte RAM (or more for large data volumes)
- Additionally 4 GByte free hard disk space for the installation
Note: the storage requirements for the Security Server database strongly depends on the number of users and of devices added. If you activate the log levels "Debug" and "Trace", more data will be written in the log files, reducing the performance of the Security Server.
Operating Systems
Note: that only 64 bit operating systems are supported. Other requirements for the operating system used are listed in the table below.
| Operating systems | Version |
|---|---|
| WINDOWS | Windows Server 2016 - 64 Bit Windows Server 2019 - 64 Bit. |
| LINUX | Redhat Enterprise Linux 7.9 - 64 Bit Redhat Enterprise Linux 8.4 - 64 Bit. |
Preliminary Considerations
Directory Structure
Refer to the following directory structure:
<SSMS_INSTALL> refers to Installation directory with the other files and subdirectories whereas <SSMS_HOME> refers to Home directory of the installation, with the local settings and log files of the Security Server
On Linux
| Directory name | Path |
|---|---|
| <SSMS_INSTALL> | /opt/KOBIL/ |
| <SSMS_HOME> | /opt/KOBIL/SSMS/ |
On Windows
| Directory name | Path |
|---|---|
| <SSMS_INSTALL> | C:\Program Files\KOBIL Systems\SSMS |
| <SSMS_HOME> | C:\Program Files\KOBIL Systems\SSMS\home |
Directory and File Permission for Linux
During the installation, a permission script is generated, which defines the directory permissions that the Security Server user requires to operate the Security Server when this is started as a Daemon. The script is available in the following directory:
/opt/KOBIL/<SSMS_INSTALL>/configutil/etc/permissions
It can be modified or deleted if other permissions are required. Please bear in mind that eventual problems related to changing the script are not supported by KOBIL.
Database Requirements and Database Information
You will need to have installed a database management system (DBMS) to set up and adjust all the required Security Server components with the configuration utility. The Security Server currently supports the MSSQL, MySQL and Oracle Database systems. Set up a user for the corresponding DBMS with the required permissions. The system supports the UTF 8 character set. No additional character rules are needed. If you have already created a database for the Security Server, it will be automatically detected by the configuration utility. If a database administrator has created the Security Server database manually, the database must contain no tables and must be empty, otherwise the configuration utility returns the error message “This is not an Security Server database”.
Support of database collations
Security Server requires some database columns to be case sensitive (like a user’s Id), while others are treated case insensitive (like the name of a role).
- MYSQL: Security Server applies the collation type 'utf8_general_ci' as default. That means per default all columns are case insensitive. Case sensitive columns are additionally bear the BINARY attribute.
- MSSQL: Security Server applies the collation type 'Latin1_General_CI_AS' as default. That means per default all columns are case insensitive. Security Server configures case sensitive columns to have the collation type 'SQL_Latin1_General_Cp1_CS_AS'. Please note that 'Latin1' aspect of the collation types does not interfere with supported Unicode character sets.
- ORACLE: By default ORACLE is case sensitive. The possibility to change this on a per column basis has been introduced with ORACLE 12.2. Because of compatibility to ORACLE 11 and to avoid performance issues on the database side all columns in Security Server are case sensitive. That means ORACLE provides the possibility to create for example two roles wit h the names 'Testrole' and 'testrole'. When changing data directly on database level, the use of large and lower case must comply to Security Server conventions.
⚠️ ORCALE DB-service requires configuration with SECUREFILE LOB type set to "db_securefile=PREFERRED" and also the parameter "MAX_STRING_SIZE=EXTENDED"
| Database | Version |
|---|---|
| Oracle | Oracle 19c - compatibility mode 19.0.0 Oracle 12c Release 2 - compatibility mode 12.2.0 |
| MySQL | MySQL 5.7 MySQL 8.0 |
| MS SQL Server | Microsoft SQL-Server 2016 Microsoft SQL-Server 2019 |
| PostgreSQL | postgreSQL 13.4 |
Options for Creating the Security Server Database
You have various options for creating the Security Server database:
- Option A: No database exists before the Security Server installation. This means that the complete Security Server database with all the tables for every module will be created with the configuration utility. In this case, you need administrator rights for the creation of the database. Note that this option does not work with the Oracle Database, so this database must always be created before the installation.
- Option B: The database already exists without tables and is empty. This means that you first create the database without table, which are then created by the configuration utility. The database may not contain external tables. In addition, you require database permissions to create and write tables for the already existing database.
- Option C: An Security Server database with tables already exists and it must be migrated. In options A and B, the database permissions can be transferred by the configuration utility. The database administrator can thus use the configuration utility to create the complete Security Server database. After that, the database administrator gives the CU or the Security Server administrator the needed rights.