Server prerequisites

This document contains server requirements and other prerequisites for the proper functioning of the Team assistant platform. These requirements may be presented to customers.

Supported Browsers (for Users)

• Microsoft Edge
• Google Chrome
• Mozilla Firefox
• Android WebView
• iOS Safari

Administration Requirements (for Consultants and Administrators)

• Database Access: SQL Management Studio, SQL Developer
• Supported Browsers: Google Chrome

Hardware and Software Requirements for TAS

Minimum, Standard, and Extended Configuration

Recommended Configuration (1-2 TAS Instances, DB on the Same Machine)

• Processor: 6 cores/threads
• RAM: 24 GB or more
• HDD: 210 GB
• Network Bandwidth: 100 Mbps or more

Supported Databases and Operating Systems

Databases

• Oracle XE/SE/EE 12 or higher (Recommended: Oracle XE 21c)
• MSSQL Express 2017 or higher (Recommended: SQL Server 2022)

Supported Server OS for TAS

• Linux: Red Hat EL 8 / Rocky Linux 8 / Oracle Linux 8 / Ubuntu 20.04, 22.04 / Debian 12 (Recommended: Red Hat 8)
• Windows: Windows Server 2022 or higher (Recommended: Windows Server 2022 - WSL 2, nested virtualization required)

Recommended Disk Partitioning for Linux Installations

Expected Workload Assumptions:

• Backups on an external system
• Database on the same server
• Up to 10 concurrent logged-in users, up to 500 active users
• Maximum of one running test instance at a time
• Optimally structured templates with up to 100 tasks
• For DMS files exceeding thousands of items (>10GB), increase HDD capacity

Prerequisites (Customer)

Requirements for TAS Instance Installation

• Infrastructure & Internal Policies (Backup policies, internet access, etc.)
• Software Installation Policies (e.g., which disk/partition to install DB, TAS, and DMS files)
• Database Location (Dedicated machine or same server)
• Backup Policy

Network Access

• TAS requires port access for HTTP communication: 443 (optionally 80 for redirection)
• Server installation and management require:
  • SSH (Linux): Port 22
  • RDP (Windows): Port 3389
• Internet access is required for installation (proxy is sufficient)

DNS - Domains

• Each TAS instance (test/production) requires a DNS record pointing to the server (typically a third-level domain).
  • Examples:
    • tas.domain.com
    • test.domain.com
• Obtain a valid certificate for all domains, usually a corporate certificate is sufficient.

DMS (Document Management System)

• Is file processing required? (Higher performance and RAM usage)
• Is full-text file search needed? (Higher performance and RAM usage)

SMTP Configuration

• SMTP server address for sending emails
• If authentication is required: username & password (or alternative email sending method such as sendmail)
• Sender Email Address for TAS system emails (typically the same as the SMTP login)

MSSQL Configuration

• User Account for Database Connection:
  • SQL Authentication or AD Account
  • The user must have db_owner permissions for the assigned database
  • Default schema should not be dbo (e.g., tas)
  • Database should use Czech_100_CI_AS collation and have READ_COMMITTED_SNAPSHOT ON enabled

Authentication

Supported Authentication Methods

• Password
• AD
• ADFS
• Apache Kerberos
• Azure AD
• OAuth2
• SAML2

AD Authentication Requirements

• Server Address, Port, Organization RDN, Service User Credentials, and DN
• Filter (DN) for Organization/Groups for Authentication & Synchronization
• Username Format: sAMAccountName (with or without email)

Organizational Structure & Synchronization

• Determine how users are structured
• If possible, create a test user
• Identify the technology used (OpenLDAP, MS AD)
• Consider differences in user creation and authentication

Methods for Extracting Organizational Structure, Management, and Users

• AD (users only)
• External System (CSV, WS, etc.)
• Manual Entry

TAS Monitoring (Nagios)

TAS functional components can be monitored via GET requests to the application endpoints:

• Frontend Availability: https://frontend/status → Returns "status:OK"
• Backend Availability: https://backend/status → Returns "status:OK"
• Database Connection: https://backend/status/db → Returns "status:OK"

For more detailed monitoring, use pm2 jlist under the TAS user account to return a JSON with information about running Node.js (TAS) processes, CPU usage, and memory consumption.