About
Zephyr Data Center is a Zephyr Enterprise solution with horizontal scalability support for high availability, scalability, and performance. It involves deploying Zephyr Enterprise on multiple nodes, which are stateless engines where all the business logic resides, along with an external database and a shared folder as shown below:
...
Load Balancer - balances the load across the cluster nodes.
Elasticsearch – a search engine deployed on the server node as a micro service or as a separate process in the virtual private network.
Shared database – a shared database used by the nodes. Zephyr supports MySQL, MS SQL Server, and Oracle Database.
Shared directory – a shared folder where attachments are stored. In a cluster environment, this folder must be shared with write permissions. Network-attached storage (NAS) and similar devices are supported.
...
) and similar devices are supported.
| Note |
|---|
It is recommended to have this clustered deployment behind a firewall. |
Recommended Configurations
The deployment components may vary depending on the number of concurrent users who will work with Zephyr Data Center. There are three recommended configurations:
Configuration 1: Up to 100 concurrent users
Component | Number of Nodes | vCPU | System Memory | Application Memory | Storage |
|---|---|---|---|---|---|
Application | 1 (single node) | 4 | 16 GB | 8 GB | 350 GB* |
Elasticsearch | |||||
Database |
* Depending on the database size.
Configuration 2: 100 - 500 concurrent users
Component | Number of Nodes | vCPU | System Memory | Application Memory | Storage |
|---|---|---|---|---|---|
Application | 2 | 4 | 16 GB | 16 GB | 350 GB |
Elasticsearch | 1 | 4 | 16 GB | 8 GB | 350 GB |
Database | 1 | 8 | 16 GB | 16 GB | 350 GB* |
Load Balancer | A load balancer to distribute load among the application nodes | ||||
Shared | Shared among the application nodes to store attachment files for Requirements, Test Cases and Executions | ||||
* Depending on the database size.
Configuration 3: Over 500 concurrent users
Component | Number of Nodes | vCPU | System Memory | Application Memory | Storage |
|---|---|---|---|---|---|
Application | 4 | 4 | 16 GB | 16 GB | 350 GB |
Elasticsearch | 3 | 4 | 16 GB | 8 GB | 350 GB |
Database | 1 | 16 | 32 GB | 16 GB | 350 GB* |
Load Balancer | A load balancer to distribute load among the application nodes | ||||
Shared | Shared among the application nodes to store attachment files for Requirements, Test Cases and Executions | ||||
* Depending on the database size.
| Info |
|---|
|
Requirements
The same Java version must be installed on all the nodes.
The same time zone must be set on all the nodes and the current time must be synchronized (use the Network Time Protocol daemon (ntpd) or a similar service).
Installation procedure
To install Zephyr Enterprise on cluster nodes, you need to perform the following:
1. Install a database
You can installone of the following database management systems on any computer where Zephyr is not installed:
...
| Note |
|---|
You must have a connector JAR file for your MySQL, Microsoft SQL Server or Oracle database. |
2. Install Elasticsearch
Install Elasticsearch 56.58.01 (a search engine) on a separate node where Zephyr is not installed and configure it for your cluster environment.
3. Install Zephyr Enterprise on your nodes
| Note |
|---|
When installing Zephyr on your nodes, keep in mind the following:
|
...
9. Copy the HAZELCAST_USERNAME and HAZELCAST_PASSWORD values and paste them to the zephyr/tomcat/webapps/flex/WEB-INF/classes/cluster.properties file on the other nodes.
4. Set up a shared directory
| Expand | ||
|---|---|---|
| ||
Share a folder by using NAS (network-attached storage) or a similar device: 1. Create a shared folder with read/write access in NAS. 2. On all the nodes, open the Program Files\Zephyr\tomcat\webapps\flex\WEB-INF\classes\jdbc.properties file, find the line
and replace the C:/Program Files/Zephyr part with the IP address of the NAS shared folder. For example:
|
...
Now you can use your nodes.
See Also
Upgrading Zephyr Enterprise
Support and Troubleshooting
...