Installing Concert, Concert Workflows, and Concert Data Apps using quick-start mode

Edit online

This procedure describes how to install Concert, Concert Workflows, and Concert Data Apps using the quick-start mode for quick deployment on a virtual machine (VM).

In quick-start mode, a default params.ini file with predefined configuration values is automatically created and used to install all components (Concert, Concert Workflows, and Concert Data Apps). If you prefer to select specific components to install or customize the configuration, see Installing on a VM for the manual installation procedure.

Note: Quick-start mode is supported only on x86 VMs. IBM Power (ppc64le) VMs do not support installation using quick-start mode.

Before you begin

Ensure the environment meets the following requirements before starting the installation:

System requirements: Verify the VM specifications in System requirements.
IBM entitlement key: Obtain a valid key as described in Obtaining an IBM entitlement API key.
User access: Log in as a root user or ensure sudo privileges for all commands.

Instructions

Complete the following steps as the root user to install Concert, Concert Workflows, and Concert Data Apps in quick-start mode:

Download and extract latest software packages:
1. Download the latest software packages from the public GitHub repository: https://github.com/IBM/Concert/releases
```
wget https://github.com/IBM/Concert/releases/download/v3.0.0/ibm-concert-x86.tar.gz
```
2. Extract the package:
```
tar xfz ibm-concert-x86.tar.gz
```
Set the IBM Container Registry password to your entitlement key:
```
export REG_PASS=<IBM entitlement key>
```
Important: Replace <IBM entitlement key> with your actual IBM entitlement key. This key is required to pull container images from the IBM Container Registry.
Run the installation script in quick-start mode:
```
./ibm-concert/bin/setup --quickstart-vm --license_acceptance=y
```
Note: The --license_acceptance=y parameter automatically accepts the IBM Concert license agreement. Ensure you have reviewed and agreed to the license terms before using this option.

Verify installation:

Upon successful installation completion, you will see:

The default username and password for initial login.
The application URL(s) to access the IBM Concert web interface.

Sample output:

================================================================================
Wed Apr 22 03:33:37 PM UTC 2026 INFO INSTALLATION SUMMARY
================================================================================
Wed Apr 22 03:33:37 PM UTC 2026 INFO Products successfully installed: 4
Wed Apr 22 03:33:37 PM UTC 2026 INFO
Wed Apr 22 03:33:37 PM UTC 2026 INFO   You can access IBM Concert at: https://vienna2202.dev.fyre.ibm.com:12443
Wed Apr 22 03:33:37 PM UTC 2026 INFO
Wed Apr 22 03:33:37 PM UTC 2026 INFO   Admin username:   ibmconcert
Wed Apr 22 03:33:37 PM UTC 2026 INFO   Initial password: ********
Wed Apr 22 03:33:37 PM UTC 2026 INFO
Wed Apr 22 03:33:37 PM UTC 2026 INFO Note: In cloud environments (e.g., with LoadBalancers), the external IP address
Wed Apr 22 03:33:37 PM UTC 2026 INFO       or hostname may differ from the locally determined address shown above
Wed Apr 22 03:33:37 PM UTC 2026 INFO
================================================================================


================================================================================
Wed Apr 22 03:33:37 PM UTC 2026 INFO DEPLOYMENT SUCCESSFUL
================================================================================

If you encounter any errors during installation, check the installation logs:
```
./ibm-concert/localstorage/logs/prod_install_logs_<timestamp>.log
```

Log in with your credentials. Use the same username and password that you received after successful installation.
Important: It is recommended to change the default password after your initial login for security purposes.

Next steps

After accessing the product, manage user permissions through the Managing users and roles guide.

If you encounter issues during installation or operation, see Troubleshooting .