Skip to main content Skip to complementary content

Installing or upgrading Compose

The following topic describes how to install and upgrade Qlik Compose.

Installation Instructions

Information note

For best performance when using cloud-based databases (such as, Snowflake) as your data source or data warehouse, it is strongly recommended to install Qlik Compose on a machine (such as Amazon EC2) located in the same region as your database instance.

  1. Run the Compose setup file (Qlik_Compose_<version.number>.exe).

    The Qlik Compose setup wizard opens.

  2. Click Next. Select I accept the terms of the license agreement and then click Next again.
  3. Optionally change the installation directory and then click Next.
  4. Click Next and then click Next again to start the installation.
  5. When the installation completes, click Finish to exit the Wizard.

    Information note

    As part of the installation, a new Windows Service called Qlik Compose is created.

  6. Open the Qlik Compose console as described in Accessing Qlik Compose.

    Information note

    When you first open the Qlik Compose Console, you will be prompted to register an appropriate license. Register the license that you received from Qlik.

Upgrade Instructions

Information note

Depending on your existing Compose version, you may also need to perform additional version-specific upgrade tasks. It is therefore strongly recommended to review the release notes for the new version before upgrading.

  1. Stop all Compose tasks and services.

  2. After the Qlik Compose service has been stopped by the Installer, make sure that all child processes are also stopped.
  3. Information note

    Compose runs a check to verify the termination of tasks and processes before running an upgrade. If any processes are found to be still running, the installation will be aborted.

  4. Run the Qlik Compose setup wizard.
  5. Start all Compose tasks and services.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!