IBM Concert

https://www.ibm.com/docs/en/concert/2.3.x
Admin
IBM Concert is an AI-powered platform for discovering, analyzing, and securing applications with...
Tokens:540,716
Snippets:3,782
Trust Score:10
Update:23 hours ago
Show doc for...
Tokens:
Raw
### Copy quickstart params file for all products

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=vm-installing

Example command to copy the concert-dataapps-workflows-vm-quickstart-params.ini file when installing all three products: Concert, Concert Workflows, and Concert Data Apps.

```bourne
cp $INSTALL_DIR/etc/sample-params/concert-dataapps-workflows-vm-quickstart-params.ini $INSTALL_DIR/etc/params.ini
```

--------------------------------

### Example params.ini configuration

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=dvmv-installing-concert-concert-workflows-concert-data-apps-in-air-gapped-environment-vm

Example configuration for the params.ini file. Products to install must match what was downloaded on an internet-connected VM. IMAGE_REGISTRY_PREFIX must start with cp.icr.io/cp for air-gap recognition; no registry credentials are needed on the air-gapped VM.

```plaintext-ibm
# Products to install must match with what was downloaded on an internet connected VM )
INSTALL_CONCERT=TRUE
INSTALL_DATAAPPS=TRUE
INSTALL_WORKFLOWS=TRUE

# VM-specific configuration
INSTALL_VM=TRUE
WORKFLOWS_INSTANCE_ADDRESS=${INSTANCE_ADDRESS}
```

--------------------------------

### Run installation setup script

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=dvmv-installing-concert-concert-workflows-concert-data-apps-in-air-gapped-environment-vm

Runs the setup script to deploy Concert, Concert Workflows, and Concert Data Apps on the air-gapped VM. Replace <user> and <password> with your credentials.

```plaintext-ibm
./bin/setup --license_acceptance=yes --username=<user> --password=<password>
```

--------------------------------

### Example etc/params.ini configuration for airgap installation

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=dk-installing-concert-concert-workflows-concert-data-apps-in-air-gapped-environment-kubernetes

Example configuration for airgap installation. Set REG_USER to your private registry username, IMAGE_REGISTRY_PREFIX to your private registry address (without protocol), and the SUFFIX variables to the namespace/path used during mirroring.

```plaintext-ibm
INSTALL_CONCERT=true
INSTALL_WORKFLOWS=true
INSTALL_DATAAPPS=true

HUB_NS=solis-hub
CONCERT_NS=concert
WORKFLOWS_NS=concert-workflows
DATAAPPS_NS=concert-dataapps

# Private registry settings - SUFFIX env variables need to be overwritten
REG_USER=regadmin
IMAGE_REGISTRY_PREFIX=tokyo1.fyre.ibm.com:5000
HUB_IMAGE_REGISTRY_SUFFIX=/pacca
CONCERT_IMAGE_REGISTRY_SUFFIX=/pacca
WORKFLOWS_IMAGE_REGISTRY_SUFFIX=/pacca
DATAAPPS_IMAGE_REGISTRY_SUFFIX=/pacca

WORKFLOWS_INSTALL_ALL_INTEGRATIONS=false
WORKFLOWS_INSTANCE_ADDRESS=solis-gw-concert-workflows.apps.vienna.cp.fyre.ibm.com
```

--------------------------------

### Copy quickstart params file for all products

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=kubernetes-installing-ocp-cluster

Copies the concert-dataapps-workflows-k8s-quickstart-params.ini file to params.ini for installing Concert, Concert Workflows, and Concert Data Apps.

```bourne
cp $INSTALL_DIR/etc/sample-params/concert-dataapps-workflows-k8s-quickstart-params.ini $INSTALL_DIR/etc/params.ini
```

--------------------------------

### Run the install-concert-k8s setup script

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=kubernetes-scaling-resources

Command to run the setup script with required parameters: license acceptance, username, password, and registry password (entitlement key). This script installs Concert with the configured scaling level.

```plaintext
./ibm-concert/bin/setup --license_acceptance=<y> --username=<user> --password=<password> --registry_password=<registry_entitlement_key>
```

--------------------------------

### Install backup service script

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=vm-backing-up-restoring

Starts the backup service and timer. Must be re-run after any changes to the service file to apply the latest changes.

```plaintext-ibm
./ibm-concert/ibm-concert-std/systemd/backup/install_backup_service
```

--------------------------------

### Run bin/setup to prepare Concert Workflows instance

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=dvmv-migrating-from-rapid-infrastructure-automation-concert-workflows-vm

Runs the setup script with license acceptance, default username and password, and registry password (entitlement key). The username and password become the initial login credentials. A successful installation returns a 'DEPLOYMENT SUCCESSFUL' message.

```bourne
$INSTALL_DIR/bin/setup --license_acceptance=y --username=<user> --password=<password> --registry_password=<registry_entitlement_key>

```

--------------------------------

### Install pgvector for PostgreSQL 14

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=vm-setting-up-external-data-repositories-concert

Example command to install pgvector for PostgreSQL version 14.

```plaintext
sudo apt-get install postgresql-14-pgvector
```

--------------------------------

### Run installation setup script

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=installation-setting-up-custom-storage-concert-workflows

Run the bin/setup script to prepare your machine. Use the --username, --password, and --registry_password options. If --password is not specified, the tool prompts for it. For cp.icr.io/cp, the registry password is the entitlement key.

```plaintext
$INSTALL_DIR/bin/setup --license_acceptance=y --username=<user> --password=<password> --registry_password=<registry_entitlement_key>
```

--------------------------------

### Example custom.conf settings

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=vm-setting-up-custom-postgresql-configuration

Example configuration settings for max_connections and shared_buffers.

```plaintext
max_connections=200
shared_buffers=3840MB
```

--------------------------------

### Install pgvector extension

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=vm-setting-up-external-data-repositories-concert

Install the pgvector extension for PostgreSQL using apt-get. Replace <PostgreSQL-version> with your PostgreSQL version, for example postgresql-14-pgvector.

```plaintext
sudo apt-get install postgresql-<PostgreSQL-version>-pgvector
```

--------------------------------

### Sample params.ini for Kubernetes installation

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=kubernetes-installing-cluster-hardened-security-configuration

Sample configuration file for installing Hub, Concert, Data Apps, and Workflows on a Kubernetes cluster. Set INSTALL_EKS to true for EKS, otherwise leave blank or false for OCP. Required parameters include namespaces and storage classes; optional parameters are available in params.ini.all.

```plaintext
# INSTALL_EKS: Set as True if installing on EKS
INSTALL_EKS=
# This example is to install Hub, Concert, Data Apps and Workflows on a Kubernetes cluster.
REG_USER=cp

IMAGE_REGISTRY_PREFIX=cp.icr.io/cp


# The parameters are for Hub deployment.
#namespace for Hub
HUB_NS=
HUB_IMAGE_REGISTRY_SUFFIX=/solis-hub
SCALE_CONFIG_HUB=level_1
# storage class for Hub
STORAGE_CLASS_HUB=

# The parameters are for Concert deployment.
INSTALL_CONCERT=true
# namespace for Concert
CONCERT_NS=
CONCERT_IMAGE_REGISTRY_SUFFIX=/concert
SCALE_CONFIG_CONCERT=level_1
#storage class for Concert
STORAGE_CLASS_CONCERT=

# The parameters are for DataApps deployment.
INSTALL_DATAAPPS=true
# namespace for Data Apps
DATAAPPS_NS=
DATAAPPS_IMAGE_REGISTRY_SUFFIX=/concert
SCALE_CONFIG_DATAAPPS=level_1
#storage class for Dataapps
STORAGE_CLASS_DATAAPPS=

# The parameters are for Workflows deployment.
INSTALL_WORKFLOWS=true
#namespace for Workflows
WORKFLOWS_NS=
WORKFLOWS_IMAGE_REGISTRY_SUFFIX=/concert  
# workflows instance address. e.g. solis-gw-workflows.apps.test.cp.fyre.ibm.com  
WORKFLOWS_INSTANCE_ADDRESS=
# OPTIONAL- storage class  pass the storage class name for workflows if not bringing your own repositories.
STORAGE_CLASS_WORKFLOWS=
# workflows installation type
WORKFLOWS_INSTALLATION_TYPE=no-svc-acc
# The FaaS integration is not supported.
WORKFLOWS_ENABLE_FAAS=false
```

--------------------------------

### GET /concert/core/api/v1/applications/{id}

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=uad-updating-application-definition-by-using-application-patch-api

Retrieves the details of a specific application, including its current associations. Used in the example workflow to get the current associations before updating.

```APIDOC
## GET /concert/core/api/v1/applications/{id}

### Description
Retrieves the details of a specific application, including its current associations. Used in the example workflow to get the current associations before updating.

### Method
GET

### Endpoint
/concert/core/api/v1/applications/{id}

### Parameters
#### Path Parameters
- **id** (string) - Required - The ID of the application to retrieve.

### Request Example
curl -X GET \
  -H "Authorization: C_API_KEY $API_KEY" \
  -H 'InstanceId: YOUR_INSTANCE_ID' \
  "https://YOUR_CONCERT_HOST/concert/core/api/v1/applications/$APP_ID" \
  -k

### Response
#### Success Response (200)
No response body is documented.

### Notes
- Authentication: Use `Authorization: C_API_KEY <base64-encoded-api-key>` header.
- Instance ID: Use `InstanceId: <instance-id>` header.
```

--------------------------------

### Example params.ini configuration

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=vm-installing-fips-enabled

Example contents of the params.ini file showing key configuration parameters for installing Concert and Concert Workflows. Parameters include Docker executable, installation flags, image registry prefixes, and Workflows-specific settings. Note that FaaS integration is not supported in FIPS-enabled environments.

```bourne
DOCKER_EXE=<podman|docker>

INSTALL_VM=true
INSTALL_CONCERT=true
IMAGE_REGISTRY_PREFIX=cp.icr.io/cp
HUB_IMAGE_REGISTRY_SUFFIX=/solis-hub
CONCERT_IMAGE_REGISTRY_SUFFIX=/concert

INSTALL_WORKFLOWS=true
WORKFLOWS_IMAGE_REGISTRY_SUFFIX=/concert         
WORKFLOWS_INSTANCE_ADDRESS=hostname.domain.com <FQDN of your VM>
#namespace for Workflows(optional:default will be concert-workflows)
WORKFLOWS_NS=
#For enabling AI feature in workflow
WORKFLOWS_OVERRIDE_VALUES=
# The FaaS integration is not supported in FIPS-enabled environments.
WORKFLOWS_ENABLE_FAAS=false
# Enable Istio for mutual TLS communication between cluster pods.
WORKFLOWS_ENABLE_ISTIO=true
# Determines whether all integrations are installed. By default all are installed.
WORKFLOWS_INSTALL_ALL_INTEGRATIONS=
```

--------------------------------

### Copy sample params.ini file

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=dvmv-migrating-from-rapid-infrastructure-automation-concert-workflows-vm

Copies the workflows-quickstart-vm-params.ini sample file to params.ini in the installation directory. If prompted, confirm to overwrite the file.

```bourne
cp $INSTALL_DIR/etc/sample-params/workflows-quickstart-vm-params.ini $INSTALL_DIR/etc/params.ini
```

--------------------------------

### Disable NM Cloud Setup and install kernel modules on RHEL 10

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=vm-installing-fips-enabled

For RHEL 10 VMs: disables nm-cloud-setup, installs kernel-modules-extra and vim, then reboots.

```plaintext-ibm
sudo su -
systemctl disable nm-cloud-setup.service nm-cloud-setup.timer
dnf install -y kernel-modules-extra
dnf install -y vim
systemctl reboot
```

--------------------------------

### Start Concert Workflows instance

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=kubernetes-stopping-starting-concert-workflows

Command to start the Concert Workflows instance. By default, the Concert Workflows namespace is used; replace <CW_namespace_name> if installed in a different namespace.

```plaintext
cw-start.sh [--namespace=<CW_namespace_name>] [--force] [--verbose] [--help]
```

--------------------------------

### Example Ubuntu sources configuration with added components

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=workers-installing-remote-worker

Shows the expected configuration after adding restricted, universe, and multiverse to the Components row.

```bourne
Types: deb
URIs: http://us.archive.ubuntu.com/ubuntu/
Suites: noble noble-updates noble-backports
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
```

--------------------------------

### Install additional kernel modules for K3s on RHEL 10

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=planning-system-requirements-vm

On RHEL 10 systems, after disabling NM Cloud Setup, install the kernel-modules-extra package required for K3s.

```plaintext
sudo dnf install -y kernel-modules-extra
```

--------------------------------

### Example: Create new Docker storage directories (root user)

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=vm-setting-up-alternate-storage-path

Example commands to create the custom storage directories under /mnt/docker-storage.

```plaintext
mkdir -p /mnt/docker-storage/docker/data
mkdir -p /mnt/docker-storage/docker/run
```

--------------------------------

### Install remote worker without Puppeteer add-on

Source: https://www.ibm.com/docs/en/concert/2.3.x?topic=blocks-chromium

Example command to install a remote worker without the Puppeteer add-on. This is the baseline command before adding the --optional-addons=addon-puppeteer option.

```bash
./install_rw.sh --license-acceptance=y --server-hostname=10.11.12.13 --worker-group-name=my-group --worker-group-secret-key=327fgs8d7dfdsf
```
Tokens:
Raw