System Requirements

Supported Versions

• 2017
• 2019

Extended Support

• N/A

Configuration Settings

• The database must be case sensitive. We recommend Latin1_General_100_CS_AS_KS_WS.

  • This can be configured using the following command (replace dbName with the name of your database): 

  ALTER DATABASE dbName COLLATE Latin1_General_100_CS_AS_KS_WS;

• We recommend monitoring the size of your transaction log, as very large transaction logs can cause database connection errors.
• We recommend using JDBC driver mssql-jdbc-7.0.0.jre8.jarwhen transferring from operational database to SQL Server.

Necessary User Permissions

• The user must be a SQL authenticated user (not a Windows authenticated user)
• Additionally, the user must have the following roles granted:

• • db_datareader
  • db_datawriter
  • db_ddladmin

 Note: Instance and Database name options can be specified by attaching ";instanceName=;databaseName=" to the end of the JDBC URL in Hub. If using JDBC driver mssql-jdbc-10.2.x or later, the “;trustServerCertificate=“ parameter and its corresponding value is required by the driver.

Supported Versions

• 19c
• 21c

Extended Support

• 18c (End-of-Service-Life Date: 18 Jan 2023) 

 If you are interested in extended support, please reach out to support.

Configuration Settings

• The database must be case-sensitive (this is the default configuration).
• The database must be configured with the AL32UTF8 character set.

ALTER DATABASE dbName CHARACTER SET AL32UTF8;

Necessary User Permissions:

User must have CREATE SEQUENCE, CREATE TABLE, CREATE SESSION permissions, as well as sufficient quota. Typical user creation might look as follows:

CREATE USER tasktop_hub IDENTIFIED BY a_password DEFAULT TABLESPACE tasktop_hub;

GRANT CREATE SESSION TO tasktop_hub;

GRANT CREATE SEQUENCE, CREATE TABLE TO tasktop_hub;
ALTER USER tasktop_hub QUOTA UNLIMITED ON tasktop_hub;

Troubleshooting

• To resolve error ORA-30036 (UNABLE TO EXTEND SEGMENT BY 8 IN UNDO TABLESPACE), please refer to the following documentation.  

Supported Versions

• 5.7.7+ (excluding 5.7.0 - 5.7.6) (Enterprise Edition only)
• 8.0 (Enterprise Edition and Community Edition)

Extended Support

• N/A

Configuration Settings

The following settings must be applied before connecting Hub to MySQL:

• The database must be case sensitive.

  • This can be configured using the following command (replace dbName with the name of your database): 

    ALTER DATABASE dbName COLLATE = 'utf8_bin'

• The database default charset must be UTF-8, ALTER DATABASE dbName CHARACTER SET = 'utf8'
  • You can also create the database with these settings: CREATE DATABASE dbName CHARACTER SET = 'utf8'
• We recommend using JDBC driver version 8.0 or later when transferring from an operational database to MySQL Server.
• innodb_default_row_format must be DYNAMIC
• innodb_file_format must be Barracuda
• innodb_file_per_table must be ON
• innodb_large_prefix must be ON

• innodb_buffer_pool_size must be minimum 1G

  • This size is highly dependent on customer hardware and data size — the number above is only a recommendation. Please consult with Tasktop Support if you have any questions.
• max_allowed_packet property must be minimum 64M
  
  • If this is set too low, you will see a Packet for query is too large error on the Activity screen.
• max_connections property should be minimum 500
  • Note: The number of connections Hub uses is highly dependent on customer configuration, hardware, and load — the number above is only a recommendation. Please consult with Tasktop Support if you have any questions.

 Note: innodb settings are the default settings for MySQL, so you will not need to make any changes to those settings unless they have been changed previously. The innodb settings apply globally to all MySQL databases on the server, while the character set is specific to the database.

 Configuring Hub with the MySQL external operational database will prohibit the synchronization of 4-byte characters due to MySQL's default UTF8 encoding being limited to 3 bytes. Examples of 4-byte characters include but are not limited to some emojis and some Chinese characters. If you may be synchronizing 4-byte characters, consider using another supported database.

Necessary User Permissions

The following provides sufficient permissions for the tasktop_hub user on the tasktop_hub database:

REVOKE ALL PRIVILEGES, GRANT OPTION FROM tasktop_hub;

GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, ALTER, INDEX, LOCK TABLES, REFERENCES ON tasktop_hub.* TO tasktop_hub

General Support

• 2017
• 2019

Extended Support

• N/A

General Support

• 19c
• 21c

Extended Support

• 18c (End-of-Service-Life Date: 18 Jan 2023)

We recommend using JDBC driver version 8.0 or later when creating a SQL connection for Enterprise Data Stream integrations.

General Support

• 5.7.7+
• 8.0
  

Extended Support

• N/A

Note: The user must be a SQL authenticated user (and not a Windows authenticated user)

For SQL Server, please refer to Microsoft documentation for more information.

Location

• Example Format: jdbc:sqlserver://hostServerName;instanceName=MyInstance;databasename=MyDatabaseName

You can enable encrypted connections by setting 'encrypt=true' (e.g., jdbc:sqlserver://<server-name>:1433;encrypt=true;trustServerCertificate=false). If the certificate for the MySQL server is self-signed you'll need to set 'trustServerCertificate=true' (e.g., jdbc:sqlserver://<server-name>:1433;encrypt=true;trustServerCertificate=true)

If using JDBC driver mssql-jdbc-10.2.x or later, the “;trustServerCertificate=“ parameter and its corresponding value is required by the driver.

 Note: Some older editions may be missing security updates and will need to apply security service packs to use a self-signed certificate and encryption. You may experience certificate errors if the SQL Server is using a self-signed or corporate certificate. To work around this, you will need to disable certificate validation in the JDBC driver or add the certificate to the JDBC’s truststore.

For Oracle, please refer to this whitepaper for an overview of how to set up connections to encrypted Oracle server. For a guide to configuring the Oracle server to support SSL, please refer to Oracle documentation.

Location

• Example Format: jdbc:oracle:thin:@hostServerName:oracleServerPort/SID

For the most part assuming that the server is set up properly, you can follow Case#2 in the white paper and simply use a URL with the following format: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCPS)(PORT=2484)(HOST=<hostname>))(CONNECT_DATA=(SERVICE_NAME=<servicename>))). On the server, make sure to disable client authentication by setting 'SSL_CLIENT_AUTHENTICATION=FALSE ' in the listener.ora and sqlnet.ora files.

For unencrypted connections, the protocol should be TCP and the port would generally be 1521, but the URL would otherwise be the same. The above example connection string is formatted in the 'Oracle Net connection descriptor' format, but Hub also accepts 'Thin-style service name' connection strings such as jdbc:oracle:thin:@<hostname>:1521:<servicename>.

If the certificate for the Oracle server is self-signed, but you still want to use SSL, you will need to follow Case#1 in the white paper. As described in the paper, only anonymous cipher suites are permitted when trying to use SSL without server authentication. You can specify the cipher suites in the sqlnet.ora file on the Oracle server.

 Note: Some versions of Oracle do not by default support anonymous cipher suites. Thus, they will need to be imported to the server before enabling them.

For MySQL, refer to MySQL documentation for the details on how to set up your connection.

Location

• Example Format: jdbc:mysql://hostServerName:mysqlServerPort/MyDatabaseName

To enable encryption on older MySQL servers (5.6.25 and earlier or 5.7.5 and earlier) you need to set the connection property 'useSSL=true' (e.g., jdbc:mysql://<server-name>:3306?useSSL=true). Later versions will implicitly try to connect using an encrypted connection. Regardless of the version, the client will only enforce that the server uses TLS if the property 'requireSSL=true' is set.

If the certificate for the MySQL server is self-signed you will need to set 'verifyServerCertificate=false' (e.g., jdbc:mysql://<server-name>:3306?useSSL=true&verifyServerCertificate=false).

A deployment managing up to 150,000 artifacts in up to 500 projects with up to 50,000 updates/month (typically up to 1,000 active users, and up to 15 integrations).

• 8 GB system memory
• 2 x 3 GHz processor, 4 cores
• 150 GB free disk space

A deployment managing up to 1,000,000 artifacts in up to 2000 projects with up to 200,000 updates/month (typically more than 2,000 active users, and 20+ integrations).

• 16 GB system memory
• 4 x 3 GHz processors, 8 cores
• 250 GB free disk space

If your deployment exceeds any of the guidelines from the Large Deployment, please consult with Tasktop Support.

For extra-large deployments, the specific characteristics of the integrations are crucial when determining proper instance sizing. As a result, no general recommendations can be offered for extra-large deployments.