Zephyr Enterprise Data Center (for Windows On-Premise Installations only)

OS	Windows Server 2008 / 2012 / 2016 Windows 7 Enterprise / Windows 8 Enterprise / Windows 10 Enterprise
CPU	Quad-core CPU Intel Pentium or AMD Opteron (2Ghz or higher)
RAM	Minimum 8GB; Preferred 12GB RAM recommendations can be found here
Disk Space	At least 5GB Free (250GB-1TB recommended for large enterprise installations)
Networking	Wired Ethernet Static IP address REQUIRED† Ports: 80, 443 (if HTTPS), 8005, 9300, 5701, 5702, 37000, 37001 Firewall (if present): Allow ports 80, 443 (if HTTPS). Must support WebSocket protocol Proxy (if present): Must support WebSocket protocol Nodes should have at least 1Gbps Ethernet connectivity (10Gbps recommended)
Account	Administrator access to the machine Installer and services needs to "Run As Administrator"
Software	Java: Oracle JDK 8 Note: NO other Tomcat can be installed on the machine. JRE is not supported††

Zephyr Data Center (for Linux On-Premise Installations only)

OS	RedHat Enterprise 64-bit RHEL 7.0 CentOS 64-bit Ubuntu/Debian 64-bit SUSE/openSUSE 64-bit
CPU	Quad-core CPU Intel Pentium or AMD Opteron (2Ghz or higher)
RAM	Minimum 8GB; Preferred 12GB
Disk Space	At least 5GB Free (250GB-1TB recommended for large enterprise installations)
Networking	Wired Ethernet Static IP address REQUIRED† Ports: 80, 443 (if HTTPS), 8005, 9300, 5701, 5702, 37000, 37001 Firewall (if present): Allow ports 80, 443 (if HTTPS). Must support WebSocket protocol Proxy (if present): Must support WebSocket protocol Nodes should have at least 1Gbps Ethernet connectivity (10Gbps recommended)
Account	Superuser (root) access to the machine Installer and services needs to run as "root"
Software	Java: Oracle JDK 8 Connector: JDBC 5.1.40 Note: NO other Tomcat can be installed on the machine. JRE is not supported††

Supported Databases

MySQL	Database Version: 5.6 JDBC Driver Version: 5.1.40
Microsoft SQL Server	Version 2012 / 2014 / 2016 JDBC Driver Version: 4.2
Oracle	Database Version: 11g

Zephyr Client

OS	Any Desktop OS
Browser	Any one of these three with versions that support Web Sockets: Chrome Internet Explorer Firefox
Networking	Client machine must have access to port 80 for HTTP connection (or 443 for HTTPS) to the Zephyr Server
Other	Screen resolution of 1280x1024 (1280x900 for widescreen) or higher

ZBots

OS	Windows Server 2008 / 2012 / 2016 Windows 7 Enterprise / Windows 8 Enterprise / Windows 10 Enterprise Linux (RedHat, Fedora, Ubuntu, CentOS, SUSE) MacOS Only 32 bit supported
CPU	Dual-core CPU Intel Pentium or AMD Opteron (2Ghz or higher)
RAM	Minimum 1GB
Disk Space	At least 100MB Free
Networking	Wired Ethernet
Account	Administrator access to the machine Installer and services needs to "Run As Administrator"
Software	Oracle JDK 8. JRE is not supported. 32-bit only

Additional Notes

All port numbers mentioned are by default, and can be configured to fit your specific environment setup. If any firewalls or proxies are present, it is required that they support the WebSocket protocol.

Ports Explained:

80, 443(if HTTPS), 8005 and 8009 are used by tomcat and can be configured in the server.xml file under zephyr\tomcat\conf\
9300 is used by Elastic search
5701, 5702, 37000, 37001 are used by Hazelcast
Database system - 3306 (unless changed) for MySQL and 1433 (unless changed) for Microsoft SQL Server
Elastic Search - 9300 on all nodes of the cluster include the one where Elastic search is installed
Zephyr Instances - 5701,5702 (inbound ports) and 37000,37001 (outbound ports)
Load Balancer - 80 (unless changed) for load balancer access

Software Version Explained:

Elasticsearch 5.5.0 is strictly required for installing Zephyr Data Center.
Oracle JDK 8u101 or higher required. JRE is not supported
No other database should be present on the server node
Zephyr Data Center requires a separate installation of the desired Zephyr Data Center Requirements not included in the installation package

Additional deployment requirements:

The Zephyr instances need to be able to access a shared storage for storing common data (ex: attachments, etc) with a capacity of 100GB which could be further part of a HA cluster on its' own since this device is to be available without fail to all the nodes as long as the cluster is functional.
Nodes must be configured with the same timezone and keep the current time synchronized. Using NTPD (Network Time Protocol Daemon) or some similar service is a good way to arrange it.
Nodes must be able to communicate with each other based on IP address. (hosts file needs to be updated as required for this communication to work)

Browser not supported