Before installing Teamwork Cloud, ensure that the system requirements described in this chapter are met. Recommended system and storage requirements| Note |
|---|
| title | Note on system requirements |
|---|
| System requirements are dictated by the intended deployment, taking into account the overall load which the environment will experience, including: - Number of concurrent users
- Level of activity (commits) per day
- Overall number and size of the projects stored in Teamwork Cloud.
The database (Cassandra) can be located on the same server as Teamwork Cloud or on a separate server. Storage requirements apply only to the node where the database is located. The product hosting nodes can be virtualized without any issues if the host is not oversubscribed on its resources. | Info |
|---|
| Recommended minimum sizing stated above applies to each node in a multi-node cluster. |
|
| Note |
|---|
| title | Note on storage requirements |
|---|
| For on-premises deployment, Apache Cassandra is designed to run on multiple independent servers. Each Cassandra node should have Directly Attached Storage (DAS) composed of NVMe drives for optimum performance. Traditional network-attached storage solutions that rely on IP-based connections (iSCSI, NFS, or SAN) are not recommended for on-premises deployments, as they introduce additional latencies and anti-patterns. To learn more, see the following topics: For cloud deployment, use storage technologies that have been benchmarked for Cassandra. Modern solid-state/flash arrays with fast interconnects are preferred. Note that Teamwork Cloud is not compatible with managed Cassandra services, such as Amazon Keyspaces. To learn more, see the following topics: |
| Resource requirements by deployment type |
|---|
| Deployment type | Recommended system requirements | Recommended storage requirements |
|---|
| Teamwork Cloud AND Cassandra on Linux | - 96 -128 GB ECC RAM
- >=16 processor threads (equivalent or better than the Intel Xeon E-2278G, or their AMD counterparts, supporting x86-64 architecture)
1TB NVMe/SSD DAS storage
| - 3 Solid State Drives with high IOPS
- (recommended ~400K)
NVMe or SSD drives are highly suitable due to their low latency and high throughput. - 3 separate disk mounts
Data, commit logs, and applications have different access patterns and should reside on separate disks to avoid I/O contention. For a detailed example, please see Preparing the operating system
| Only Cassandra (Linux only)
| - 48 - 64 GB ECC RAM
- >=8 processor threads (equivalent or better than the Intel Xeon E-2234, or their AMD counterparts, supporting x86-64 architecture)
1TB NVMe/SSD DAS storage
| | Only Teamwork Cloud | - 48 - 64 GB ECC RAM
- >=8 processor threads (equivalent or better than the Intel Xeon E-2234, or their AMD counterparts, supporting x86-64 architecture)
- >250GB storage
| | Web Application Platform for small and medium deployments (5, 10, 25, or 50 connection licenses) | - 32 GB of RAM dedicated exclusively to Web Application Platform services and additional RAM per OS requirements
- CPU with 8 cores running at 2.1 GHz
- For deployments on Linux, the open file limit must be no less than 20,000 files.
| - 100 GB of free space on the disk, NVMe or SSD
| | Web Application Platform for large enterprise deployments (75, 100, or unlimited connection licenses) | - 64 GB of RAM dedicated exclusively to Web Application Platform services and additional RAM per OS requirements
- CPU with 16 cores running at 2.1 GHz
- For deployments on Linux, the open file limit must be no less than 20,000 files.
| - 200 GB of free space on the disk, NVMe or SSD
|
| Note |
|---|
| title | Deployments with unlimited licenses |
|---|
| If you have a deployment with an unlimited license or are in doubt about what hardware to use, contact your account executive for hardware recommendations to accommodate your specific needs. |
| Note |
|---|
| title | Note on Web Application Platform |
|---|
| When installing Web Application Platform for production purposes, it is recommended to install it on a separate machine. |
Software requirementsTeamwork Cloud supports the following operating systems: For a fully working environment, you will also need the following: - Cassandra
is compatible with OpenJDK 11.0 (tested with Eclipse Temurin™ by ADOPTIUM 11.0.14)Teamwork Cloud is compatible with OpenJDK 17.0 (tested with Eclipse Temurin™ by ADOPTIUM 17.0.8- (check the compatible version here)
- Java compatible with Teamwork Cloud (twcloud service) and Cassandra (check version here)
- IMPORTANT. To use modeling tools with DSLS licenses, Microsoft Visual C++ Redistributable must be installed (see Latest supported Visual C++ Redistributable downloads). This applies to Windows OS only.
- FlexNet or DSLS license serverCassandra 4.0.x, 4.1.x
- A static IP address for each node.
Open ports 1101, 2181, 2552, 7000, 7001, 7199, 9042, and 9142 between servers in a cluster. Open ports 3579, 8111, 8443, and 10002 (default) for clients. The port number 10002 can be changed according to the port assigned to secure connections between the client software and Teamwork Cloud.
The following table lists the ports that Teamwork Cloud services use and their descriptions. Port traffic is TCP unless otherwise specified. | Service | Port | Description |
|---|
| FlexNet server (lmadmin) | 1101 | FLEXnet server port |
| 8090 | License management web interface HTTP port |
| 27000-27009 | Internal license server manager port |
|
|
| | Cassandra | 7000 | Internode cluster communication port (not used if TLS is enabled) |
| 7199 | JMX monitoring port of the Cassandra node |
| 9042 | Native client port for processing database operations |
|
|
| | Teamwork Cloud | 2468 | JMX metrics reporting port for monitoring stack |
| 2552 | Teamwork Cloud default remote server port |
| 3579 | Default Teamwork Cloud port when SSL is not enabled |
| 8111 | REST API HTTPS port |
| 10002 | Default port for encrypted TLS client-server communication. |
|
|
| | Web Application Platform | 8443 | Web Application Platform HTTPS port (Authentication, Collaborator…) |
|
|
| | Zookeeper | 2181 | Zookeeper internal port |
| Info |
|---|
| title | If deploying on Amazon EC2 |
|---|
| | When deploying on Amazon EC2, we recommend using the m5-2xlarge, r5-2xlarge, or i3-2xlarge instances. Depending on the workload, you may want to go to the -4xlarge instances, but for most users, the -2xlarge will suffice. The m5 instances meet the minimum system requirements and will be acceptable for small deployments. The r5 instances provide more memory for the same CPU density. The i3 instances should be used when workloads have a higher level of user concurrency due to the significantly improved performance of the ephemeral NVMe storage. |
|
