3.0 System Requirements

Multiple-Appliance Deployments Are the Focus of This Guide

All-in-One deployments are covered in Section A.0, Creating an All-in-One Deployment.

The following sections outline platform, version, and other requirements for your multi-appliance TeamWorks deployment.

Administrative Workstations and Browsers

Table 3-1 Administrative Workstations and Browsers





Windows, Mac, or Linux

Capable of running a listed browser

Mozilla Firefox

Latest version

Microsoft Edge with Chromium

Latest version

Windows only


Latest version

Supported but not tested on Linux. Supported and tested on Windows and Mac.


Latest version

Mac only

Appliance Disk Space

  • See Worksheet 15—Storage Planning Summary

Planning for disk space varies widely according to organization needs and the planning process is covered in the TeamWorks 18.2.1 Planning Your TeamWorks Deployment—Best Practices guide.

General guidelines are summarized in the following sections of the Planning Best Practices guide:

Appliance Shared Storage (/vashare Mount Point) Platforms

  • See Worksheet 15—Storage Planning Summary

The TeamWorks appliances in a Multi-appliance deployment access a commonly-shared NFS storage disk that you will identify and create in Section 4.0, Setting Up NFS Shared Storage.

Table 3-2 Shared Storage Platforms (/vashare Mount Point)




Exported mount point on one of the following:

  • SLES 12

  • SLES 15

NFS on Windows is not supported.

Appliance Memory and CPU

Table 3-3 Memory and CPU




  • 16 GB RAM

    1.5 GB Operating System

    8 GB Java Heap (always 1/2 total system memory)

  • 4 CPUs

TeamWorks Search

Less than 1,000 Users

  • 8 GB RAM

  • 2 CPUs

More than 1,000 Users

  • 12 GB RAM

  • 2 CPUs


Less than 1,000 Users

  • 8 GB RAM

    2 GB Operating System

    2 GB Memcached

    4 GB Java Heap

  • 2 CPUs

More than 1,000 Users

  • 12 GB RAM

    2 GB Operating System

    3 GB Memcached

    7 GB Java Heap

  • 2 CPUs

Content Editor

  • 16 GB RAM

  • 4 CPUs

Web Application Access (End Users)

Table 3-4 Browsers for End User Web Application Access




Mozilla Firefox; Google Chrome (latest versions)


Microsoft Edge with Chromium , Mozilla Firefox; Google Chrome (latest versions)


Safari; Mozilla Firefox (latest versions)

TeamWorks Software

You must download and prepare the TeamWorks software in Section 5.0, Downloading and Preparing the TeamWorks Software.

IP Addresses

Each appliance requires the following.

Table 3-5 IP Addresses



IP Address

  • A static address that is associated with a DNS host name.


Network Mask

  • The appropriate network mask for the IP address.


Gateway IP Address

  • The gateway for the IP address subnet.


DNS Host Name

  • The DNS name associated with the IP address.

    Example: TeamWorks-1.myorg.local

DNS IP Address

  • Up to three IP addresses of DNS servers for the IP address subnet.


NTP IP Address or DNS Name

  • Up to three IP addresses or DNS names of reliable NTP servers used to coordinate time on your organization’s network—especially your LDAP directory servers.

    Example: time.myorg.local

If using VMware, Micro Focus recommends setting up NTP in accordance with the VMware best practices guidelines.

(Optional) Network Proxy

  • If you want TeamWorks to connect through a forward proxy server for web requests, such as online updates, you can specify this as part of the initial configuration.

    You need the proxy server’s URL and a username and password if authentication is required.

    You can also use the Port 9443 > Network Services icon to set and manage this. See Changing Network Settings in the TeamWorks 18.2.1: Administrative UI Reference.

LDAP Directory Services (Users and Groups)

Table 3-6 LDAP Directory Services

Directory Service






  • 2018






  • Version 9.1 and later


Active Directory


  • Active Directory - no version specified


Content Editor Requires an SSL Connection with Each TeamWorks Appliance

If you integrate the Content Editor appliance with your TeamWorks appliances, the connections between the Content Editor and each TeamWorks appliance must be secured through certificates issued by an industry-recognized Certificate Authority.

You must install a valid certificate in each TeamWorks appliance’s and Content Editor appliance’s JVM Certificates key store by using the information found in Certificates in the TeamWorks 18.2.1: Administrative UI Reference.

IMPORTANT:The use of self-signed certificates for securing inter-appliance communications is not supported in TeamWorks 18.2 and later.

Mobile Device Platforms

IMPORTANT:Accessing TeamWorks through a web browser on a mobile device is not recommended unless an app is not available for the device.

For more information about the TeamWorks mobile app, see the TeamWorks User Help.

Table 3-7 Mobile Devices


Supported Versions

iOS Phones and Tablets

  • iOS 12.x or later

    The native app is available as a free download in the Apple App Store.

Android Phones and Tablets

  • Android phones and tablets for Android 8.1 or later

    The native app is available in the Android app store.

SQL Database Server

Table 3-8 SQL Database Server

Database Type

Supported Platforms

PostgreSQL (10 and later)

  • Linux

Microsoft SQL Server

  • 2019

  • 2016

  • 2014 (not formally tested)

Virtualization Hypervisor Platform

Table 3-9 Virtualization Hypervisor Platform

Hypervisor Type

Supported Versions


  • A VMware ESXi 6.x host server with the latest update for hosting the appliance VMs.

    For the most up-to-date compatibility matrix of supported VMware host servers, see the VMware Compatibility Guide provided by VMware.

  • A VMware vSphere client 6.x or later for accessing the host server and the appliances for initial configuration.

    Not all versions of the vSphere client are compatible with versions of VMware ESXi. See the VMware Product Interoperability Matrixes provided by VMware.

  • VMware vMotion is supported when running TeamWorks on VMware ESXi.