System Requirements


Supported Operating Systems

Tasktop Sync is supported on the following operating systems and versions. Versions tested by Tasktop are indicated below.

  • 32-bit or 64-bit Windows; Windows Server 2007, 2008, 2012, 2016 or 2019 are recommended.
  • Red Hat Enterprise Linux 5, 6, 7 or 8; GTK2 and X Windows are required.
    • To force GTK2, add the following to the TasktopSync.ini file before -vmargs:
      --launcher.GTK_version 
      2
  • SUSE Linux Enterprise Server 11, 12, 15; GTK2 and X Windows are required.
    • To force GTK2, add the following to the TasktopSync.ini file before -vmargs:
      --launcher.GTK_version
      2

Java Run me Environment

Tasktop Sync is packaged with a JRE and there is no need to install a JRE separately. Tasktop Sync uses Oracle Java 1.8.0-u91.

Networking

Tasktop Sync requires an IPv6 or IPv4 network to access target ALM repositories. Access to some repositories is limited to IPv4, so please check the Tasktop Sync documentation speci c to the repositories to be synchronized prior to con guring the network.

Tasktop Sync should be located on the same network (or very nearby) to the target ALM repositories in order to minimize latency between servers. Recommended network throughput is 100Mbps with a latency of less than 50ms. When synchronizing large attachments (i.e., sizes > 20MB) greater throughput may be desired.

Hardware Sizing for Deployment Scenarios

The following hardware is recommended for three sample Tasktop Sync deployment scenarios.

Disk space is primarily used for caching and storing transient data that can be used to enhance the synchronization process. The amount of disk space needed is proportional to the size of the collection of artifacts that are being synchronized.

Processor sizes below are based on the equivalent to a 2007 Opteron or 2007 Xeon processor. 


Small Deployment

A deployment with one Sync Mapping managing up to 20,000 ALM artifacts and up to 200 active users.

  • 4 GB system memory
  • 1 GHz processor, 2 cores
  • 30 GB free disk space

Small deployment system sizing is roughly equivalent to an EC2 M3 Medium Instance.

Medium Deployment

A deployment with several Sync Mappings managing up to 100,000 ALM artifacts and up to 1,000 active users.

  • 6 GB system memory
  • 2 GHz processor, 2 cores
  • 50 GB free disk space

Medium deployment system sizing is roughly equivalent to an EC2 M3 Large Instance.

Large Deployment

A deployment with many Sync Mappings involving many ALM repositories and managing 200,000+ ALM artifacts and over 1,000 active users.

  • 8 GB system memory
  • (2) 3 GHz processors, 4 cores
  • 100 GB free disk space

Large deployment system sizing is roughly equivalent to an EC2 M3 Large or M3 Extra Large Instance.