General (Settings)

Introduction

General (Settings) can be accessed by clicking the 'General' tab on the Settings screen.

Click 'General' Tab


Under General (Settings), you can access:

  • Configuration
  • Master Password Configuration
  • Storage Settings

Under Notifications, you can access:

  • Email Notifications

Under License, you can access:

  • License

Under Troubleshooting (Settings), you can access:

  • Logging

Under Extensions (Settings), you can access:

  • Extensions
  • Key-Value Stores

Under Advanced (Settings), you can access:

  • Move Routes Between Integrations
  • Import Artifact Pair Information
  • Upgrade Backup Files

Configuration 

The Configuration section allows the administrator to set the change detection intervals of the connected repositories and to create a label for their Tasktop instance identifying the environment name and type (testing or production).

Change Detection

Selecting Repeat Method

Configuring Change Detection Settings

  • Repeat Method: The method in which Tasktop detects changed artifacts in your external repositories. You can configure repeat method to run on a time interval (e.g., 1 minute or 5 minutes) or an advanced schedule using cron expression (e.g., every 30 minutes from 9am-5pm from Monday to Friday). 

          You can learn more in our FAQ here.

  • Change Detection Interval: The time between polling requests made by Tasktop to your external repositories to detect only changed artifacts. This defaults to 1 minute, but can be customized as desired.
    • Note: this global setting can be overridden with an integration-specific change detection interval, by updating the Change Detection settings for that integration

  • Full Scan Interval: The time between polling requests to detect changed artifacts, in which all artifacts that have previously synchronized in the integration are scanned.

    Not all changes to an artifact will register as a change. Some repositories do not mark items as changed when (for example) a relationship is added or an attachment has changed. These may not be picked up by regular Change Detection, but will be picked up by a Full Scan. You can review our connector docs to see types of updates that will require a full scan. The Full Scan Interval defaults to 24 hours on the General (Settings) screen, but can be overridden with an integration-specific full scan interval, by updating the Change Detection settings for that integration

    Note that since the Full Scan only scans artifacts that have previously synchronized, artifacts that are newly eligible for synchronization due to updated artifact filtering or routing will not be picked up by the Full Scan. These artifacts will only be processed by clicking the 'process all artifactsbutton, or when a new integration-eligible change is made to them.

    Full scans can be disabled globally on the General (Settings) screen, or on a per-integration basis via the Change Detection screen. This feature is especially useful for users that do not want to overload their repositories. To disable full scan, uncheck the 'Full Scan Enabled' box for the desired collection. If you choose to disable full scans, note that twinless artifact updates will not work and some artifact updates may be missed. 

          You can learn more about change detection and full scan styles in our FAQ here.

  • Integration Maximum Concurrency: This limits the number of events processed concurrently by each integration. Increasing this value will enable more artifact changes to flow concurrently, whereas decreasing this value will reduce the level of concurrent changes. Changing this value has the potential to affect the load on the end-points of an integration, and may have an adverse effect on performance if set too high. The default setting (10) should be used unless advised to change by Tasktop Support.

Environment Type and Name

Tasktop administrators can also set an environment type (testing or production) and name for their instance in the Configuration panel.  This will create a label visible in the upper left corner of the screen while navigating throughout the Tasktop UI, to allow users to easily identify which Tasktop instance they are utilizing.

Once set, you will see the environment type & name label displayed in Tasktop

Label is displayed in upper left corner

Master Password Configuration

This feature is not applicable to Tasktop Cloud.

After installation, you will be prompted to set a Master Password.

Set Master Password Prompt

The Master Password is used to encrypt the credentials used in your repository connections and proxy settings, along with any other configuration values that are considered secret, which could include API keys and tokens. 256 bit AES encryption is used. Tasktop Integration Hub will automatically use the stored Master Password to decrypt repository credentials.

Normally you will not need to re-enter your Master Password.  However, if the stored Master Password is missing, or if you'd like to change your Master Password from the General (Settings) screen, you will need to enter your current Master Password.

The Master Password is encrypted and stored separately from the encrypted repository credentials.  On Windows, the encrypted Master Password is stored in the Windows Registry, encrypted using the Windows Data Protection (DPAPI). On Linux, the encrypted Master Password is stored in the Home Directory of the User running Tasktop Integration Hub.

If desired, you can change or reset the Master Password from the General (Settings) screen.  

  • Change Master Password: In order to change the Master Password, you must enter your current Master Password.  
  • Reset: If resetting the Master Password, you will not need to enter your current Master Password, but previously encrypted repository passwords will be lost, and must be provided after resetting.

Change or Reset Master Password

Storage Settings 

This feature is not applicable to Tasktop Cloud.

Tasktop automatically stores operational data to a pre-configured Derby database.  This is suitable for evaluation purposes only, and is not supported for production environments.  Configuring Tasktop to utilize an external database will enable you to perform frequent back-ups without having to stop Tasktop Integration Hub, and ensure that your Tasktop Integration Hub practices are consistent with your existing disaster and recovery process. 

(lightbulb) Please see our  Hardware Requirements to see which databases are supported for storing operational data.

Migrating from the Internal Database to an External Database

To migrate your Tasktop operational data from the internal database to an external database, click the 'Use External Database' button.

Click 'Use External Database'

Next, click 'Configure JDBC Driver' to select the JDBC driver for your database. 

Click 'Configure JDBC Driver'

To download the JDBC driver:

  • Microsoft SQL Server: The JDBC driver for Microsoft SQL Server can be downloaded from the Microsoft support site
    • Tasktop currently supports use of the 7.0.0.jre8 driver version.
  • MySQL Server: The JDBC driver for MySQL can be downloaded from the MySQL download site
  • OracleThe JDBC driver for Oracle can be downloaded from the Oracle support site.  Note that it is best if the Oracle JDBC driver that is used matches the version of the Oracle server that you are connecting to.
  • PostgreSQL: The JDBC driver for PostgreSQL can be downloaded from the PostgreSQL download site.

(warning) Upon downloading the JDBC driver from the MySQL download site, please select 'Platform Independent' to download the correct file.

To upload the JDBC driver to Tasktop, a system administrator (a user with file system access to the machine that hosts Tasktop) must extract the *.jar file from the downloaded driver file and add the file to the designated directory:

  • On Windows, the default folder is C:\ProgramData\Tasktop\jdbc-drivers
  • On Linux, the jdbc-drivers folder can be found in the Tasktop installation directory
  • If needed, the user can change the location in which Tasktop looks for the files. This is done by changing the system property jdbc.libraries.path

Once the JDBC driver is uploaded, it can be selected from the 'Choose File' field on the Configure JDBC Driver pop-up.

Select JDBC Driver

Next, fill out the Database Connection credentials.

Authentication credentials must be in SQL server authentication mode (aka mixed-mode with SQL credentials).  Windows authentication mode is not supported.

Once the JDBC driver is successfully uploaded, enter the location, username, and password for your database.

Location formats are as follows:

You can click 'Test Connection' to confirm that your credentials have been accepted by Tasktop.  Once confirmed, click 'Save.'

You will see a warning message telling you that you are about to transfer to an External Database.  Review the entire message, ensuring that you have performed the recommended data back-up, and if approved select 'I understand...' and then 'Transfer.'

Transfer to External Database Warning

You will get a 'Database Transfer Completed' message once the transfer is complete.  You have now successfully transferred your operational data from Tasktop's internal database to your own external database.

Database Transfer Complete

Migrating from an External Database to a Different External Database

(warning) If you'd like to migrate your data from one external database to a different external database, please note that you will need to manually transfer the data from the current database to the new target database. If you do not manually transfer the data, Tasktop will not work properly once you switch to the target database settings.  Tasktop will not automatically transfer this data for you.

However, if you are simply updating the location or credentials of your current external database and will continue using the same database, you do not need to transfer any data. Tasktop will continue to work properly.

Moving between databases of the same type...

If you are migrating to a database of the same type (for example, moving from one MySQL database to a different MySQL database), transfer data from the old database to the new database and then simply update the Location, Username, and/or Password fields in the Database Connection section, click 'Test Connection,' and then 'Save.'  Read the warning message that pops up, ensuring you have taken all necessary steps, and then click 'I understand...' and 'Save.'  

Moving between databases of different types...

If you are migrating to a database of a different type (for example, moving from a MySQL database to an Oracle database), follow the instructions below:

  1. Create a new empty database in the new database
  2. Stop Tasktop
  3. Manually replace the jdbc driver jar in <program data>/Tasktop/drivers with the correct driver for the new database (not in <program data>/Tasktop/jdbc-drivers, because the new driver cannot be selected in the UI), and make sure it is named database-driver.jar 
  4. Manually edit <program data>/Tasktop/db/tasktop-db.json with the URL and credentials for the new database
  5. Start Tasktop
  6. Tasktop will create new empty tables in the new database
  7. Stop Tasktop
  8. Copy all the data from the tables in the old database to the tables in the new database, except the tables DATABASECHANGELOG and DATABASECHANGELOGLOCK (copying data for these two tables will cause errors)
  9. Start Tasktop

If your Database Transfer Fails or is Aborted

If your database transfer fails or is aborted, Tasktop will continue to use its internal database to store operational data.  The internal database is not cleared until a successful transfer is completed, so you should not notice any change in performance. 

However, we do recommend reviewing the external database and clearing any data and tables that were created as part of the failed data transfer before starting the transfer process again.

Overriding Database Access

In order to prevent risk of collisions, duplicates, and other errors, Tasktop has functionality to ensure that multiple Tasktop instances are not able to run on the same operational database.  If you connect your instance to a database that is already in use by Tasktop (note that this is not recommended), upon start-up of the new instance, the prior instance will lose database access and stop processing events. When you log on to the prior instance, you will see an error message prompting you to either update your credentials to connect to a different database, or to override database access.  If you override database access, this means that the other instance of Tasktop will lose access to that database.

When overriding, be sure to confirm that no other Tasktop instance is using the database before moving forward. If another Tasktop instance is actively using the database, it is recommended that you shut down the other instance of Tasktop before proceeding.

Override Database Access Message