System Requirements - Server

Hardware

The 446 Plattform® can be installed and executed either on a dedicated system (single server), a server with an additional database server (especially if there is already a central database server) or a distributed system environment (multiple-server with independent database, application, and web servers). The following specifications take both variants into account. With physically separated servers, a fast (e.g. 1 GB Ethernet) low latency LAN connection between the machines is necessary. Ideally, all servers should be in the same network.

We recommend that you implement a single server or a combined web and application server with an additional database server. This will make configuration and upgrades easier than a fully distributed deployment.

The 446 Plattform® supports multiple processors, processor cores as well as hyper-threading Hyper-threading is Intel's proprietary simultaneous multithreading (SMT) implementation used to improve parallelization of computations performed on x86 microprocessors. (depending on the operating system used).

Note:

Generally, the 446 Plattform® environment can be installed on virtual servers as well. The same requirements as for an installation on a real server apply here.

If all of the servers are combined on one physical machine, at least 32 GB RAM are required there, 64 GB are recommended. Additionally, at least 100 GB of free hard disk space are necessary (total of the memory requirements of the servers to be installed) as well as a buffer. At the same time, keep in mind that – depending on the log level set – free disk space of several GB is needed for log files. Generally, up to 40 GB are recommended here. They are to be reserved additionally to the 100 GB mentioned.

 

Database Server

  • RAM: 16 GB minimum, 32 GB recommended

  • HD: Depending on the ticket quantity, 40 to 90 GB of free disk space (matches up to 100,000 tickets, plus respectively 1 GB for every additional 5,000 tickets (without file attachments))

  • CPU: Quad core (or better) CPU

  • On the DB server, a sufficient amount of disk space has to be available daily for the transaction logs of the databases.

Application Server

  • RAM: 16 GB minimum, 32 GB recommended
  • HD: 2 GB free disk space and sufficient disk space for log files (the size depends on the log level set and the operational demands of the server - as a minimum, 30 GB should be available)
  • CPU: Quad core (or better) CPU
  • Fast low latency network connection to the web and DB servers

Web Server

  • RAM: 16 GB minimum, 32 GB recommended
  • HD: 2 GB free disk space and sufficient space for IIS log files (the size depends on the log level set and on the operational demands of the server - as a minimum, 10 GB should be available)
  • CPU: Quad core (or better) CPU
  • Fast low latency network connection to the application and DB servers

 

Software

The 446 Plattform® supports operating systems and software only as 64-bit versions.

 

Database Server

  • Windows Server 2019 or higher - for 446 Plattform versions released before 2026, Windows Server 2016 or later is sufficient
  • Microsoft SQL Server 2019 or higher (Standard or Enterprise Edition) - for 446 Plattform versions released before 2026, SQL Server 2016 or later is sufficient
  • The following SQL Server components must be installed:
    • Database Engine Services
    • Full-Text and Semantic Extractions for Search
    • Reporting Services - Native (SSRS)
    • SQL Management Studio (SSMS)
    • Analysis Services (only when using the Business Intelligence component)
    • Integration Services (only when using the Business Intelligence component)

Application Server

  • Windows Server 2016 or higher
  • Message Queue Service
  • .NET-Framework 4.8
  • latest Microsoft Visual C++ Redistributable Package
  • latest Microsoft Access Database Engine Redistributable

Web Server

  • Windows Server 2016 or higher
  • Message Queue Service
  • Internet Information Services incl. ASP.NET
  • .NET-Framework 4.8
  • latest Microsoft Visual C++ Redistributable Package
  • latest Microsoft Access Database Engine Redistributable

Warning:

Please exclude the following directories from anti virus scanning (real-time/on-access scan) of your anti-virus software:

Temporary ASP.NET Files

(e.g.: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files")

To ensure the access of the IIS (e.g. McAfee can block access).

Isonet-Log files

(e.g.: "D:\Isonet\Logfiles")

To avoid performance problems when working with the 446 Plattform®.

 

Configuration

In order to be able to process maintenance operations on the server(s), an administrator account on the respective servers is mandatory. Generally, this does not have to be a domain user – a local administrator is sufficient.

If it is not possible to work on the DB server directly, it is necessary to install the SQL Management Studio on one of the other servers (application or web server).

 

Network

  • Third-Party Systems

The 446 Plattform® is able to embed various third-party systems A third-party (peripheral) system is an area that lies outside the system boundaries, but to which the system can have relationships. The system environment is the sum of all peripheral systems.. Those are, amongst others:

  • ActiveDirectory (LDAP)
  • Databases by third-party developers (e.g. CMDB databases)
  • Mail servers for sending e-mails

  • Mail servers for the automatic retrieval of e-mails

For sending e-mails, the SMTP The Simple Mail Transfer Protocol is a protocol of the Internet protocol family that is used to exchange e-mails in computer networks. It is primarily used to feed in and forward e-mails. Other specialized protocols such as POP3 or IMAP are used to retrieve messages. SMTP servers traditionally accept connections on port 25 ("smtp"). [Wikipedia] protocol is used. For retrieving e-mails automatically (Mail2Ticket), any mail system can be used. By default, the following protocols are available:

  • MS Exchange WebServices (Exchange 2007 - Office 365)
  • IMAP
  • POP3

If these or similar third-party systems are to interact with the 446 Plattform®, the establishment of a connection between the web/application server and the respective third-party systems has to be ensured.

  • Firewall and Proxy

If a firewall or a proxy is set up between the clients and the server(s), the ports specified below have to be enabled.

  • File Types

Moreover, the file types CSS Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation of a document written in a markup language like HTML. CSS is a cornerstone technology of the World Wide Web, alongside HTML and JavaScript. [Wikipedia], ASPX, JS, HTC, DLL, JPG, GIF, PNG, TXT have to be able to pass through unfiltered. In addition to these file types, those existing as attachments on the system have to be forwarded unfiltered as well. From experience, these are: DOC, DOCX, XLS, XLSX, PDF, XML, HTM(L), EML, as well as various other file types.

  • Server and Network Ports

The ports that have to be available in the network (TCP) must be open in both directions generally. If a port does not require this, a footnote can be found next to the respective port in the following section.

Between web and application server:

  • 80 (443 optional)
  • 1801 (Message Queue)
  • 7774 (Mail2Ticket)
  • 7775 (Service Level Management)*
  • 7776 (Logging Manager)*
  • 7777 (Security Manager)*
  • 7779 (Agent)*
  • 7780 (This is the default value. It can be adjusted in the GlobalConfiguration table in the master DB: Key SecurityManager.CacheController.Port - from .)
  • 8888 (Workflow Manager)*
  • 8889 (Port for the Cache-Controller)*
  • 9999 (Messaging Manager)*

All mentioned ports beginning with 7 or 8 generally only have to be enabled between the web and application server. You can find the ports being an exception here under “Between the client and the necessary servers”.

The ports marked with * only need one direction of communication. The direction always is to the server the service has been installed on (from the web and DB to the application server).

Between web and DB server:

  • 80 (443 optional – necessary when using SSL Secure Sockets Layer, the old name for Transport Layer Security, a network protocol for secure data transmission. [Wikipedia])
  • 1433 (SQL Server)

Between application and DB server:

  • 80 (443 optional – necessary when using SSL)
  • 1433 (SQL Server)

Note:

If the DB Server does not run on the standard port TCP 1433, UDP 1434 must also be released in addition to the TCP port used and the SQL browser service must be started on the DB Server.

Between the client and the respective servers:

  • 80 (443 optional – necessary when using SSL) - web server
  • 8888 (this port is only necessary, if the Workflow Designer is to be executed on the client) – application server

 

Database server

  • General Information

In order to be able to work effectively with the database server, some settings, which are to be configured generally, are necessary.

The SQLOLEDB driver for database connections is still supported, but no longer maintained. The driver recommended by Microsoft is the MSOLEDB and must be installed separately. The download can be found here: OLEDB Driver for SQL Server.

The following services have to be running:

  • SQL Server
  • SQL Server Full Text Search
  • SQL Server Reporting Services

All of the other available services allow for using further features of the SQL server. This may be necessary, if you have special requirements, e.g. regarding the automatic backup or the Reporting Services. They are, however, not necessary on principle.

Note:

The standard collation must be case insensitive, preferably Latin1_General_CI_AS.

  • Full Text Search in Attachments

In order to be able to use the full text search in attachments (e.g. extended search, Knowledge Base), so-called filters have to be installed. The most common here are the MS Office iFilters as well as the Adobe filter package.

You can download the filters here:

Office file types: http://www.microsoft.com/de-DE/download/details.aspx?id=17062

Adobe file types – x64: http://www.adobe.com/support/downloads/detail.jsp?ftpID=5542

Subsequently, the following commands have to be executed in the SQL Management Studio:

use master

GO

sp_fulltext_service 'load_os_resources',1;

GO

sp_fulltext_service 'verify_signature’, 0;

GO

For the changes to be applied, restart the SQL Server Service after the execution.

  • Permissions
  • Drive

On the database server, a drive or at least a folder has to be shared with the support. It is sufficient to have an administrative share where, for example, C$ can be accessed. This authorization is sufficient, so no explicit release for a folder is required.

Administratively shared folders are not visible to anyone on the network. Only people who know that this folder exists will be able to view and access it, provided they are authorized to do so. Administrative shares are set up by adding a dollar sign $ after the share name. [Source: edv-lehrgang.de]

The support has to have read and write permissions to this share. This is necessary for performing backup or recovery tasks during the update.

The following permissions to the databases itself are necessary:

  • Read and write permissions
  • Backup permissions
  • Recovery permissions
  • Creating new databases
  • Changing the 446 Plattform® databases
  • Creating, deleting, and modifying all database objects (including, for example, tables, keys, saved procedures, assemblies Compiled program classes are summarized and provided as executable programs in so-called assemblies. These typically have the extensions .exe or .dll. [Wikipedia])

If this requirement cannot be met, a contact has to be available during the necessary times.

  • Additional Options to be Activated for MS SQL Server 20XX
  • Activating Remote Connections
  • Start > SQL Server 20XX > Configuration Tools > SQL Server Configuration Manager
  • In the tree on the left: SQL Server Network Configuration > Protocols for MSSQLSERVER
  • Activate the option Named pipes and TCP/IP in the right array
  • Compatibility

  • When using the Service Portfolio, it can positively influence performance if the compatibility level of the TXPE database is not increased above 110 (SQL Server 2012).

  • Reporting Services

The Reporting Services do not necessarily have to be installed on the database server; they can be installed on any other server as well. However, it is necessary that the URL used for the access to the Reporting Services can be accessed from all hosts.

A member of support must have access to the folder ...\ReportingServices. This is necessary for expanding the configuration of the Reporting Services, in order to allow the 446 Plattform® to work with them. Moreover, it is necessary to be able to analyze the log files in case of problems.

Generally, there are no specific requirements for the basic configuration of the Reporting Services, which can be performed via the tool Reporting Services Configuration.

  • Real-time communication Server - Client (SignalR and WebSocket)

As of Microsoft IIS 8.0, which was installed in Windows Server 2012 and Windows 8.0, the WebSocket protocol is available. You can install it on the server with the following PowerShell command:

Add-WindowsFeature Web-WebSockets

  • Push Notifications

Global Push Notifications have been implemented in the 446 Plattform® (version 2016). These are active for all users if they have not deactivated the notifications in their own options.

SignalR uses the WebSocket protocol (RFC 6455) to transmit notifications, if supported by the IIS and browser.

Note:

The fallback is an open HTTP(S) connection, which is limited for each browser. You notice this fallback by the fact that after a certain number of open ticket detail menus, none of the windows will work anymore. Every refresh is not answered. If a window is closed, all other open windows will work again.