OpsIQ

Licensing ​

OpsIQ requires a license key to run. This page explains how to obtain one and how it is installed.

Getting a license key ​

Your OpsIQ license key comes from your Fresche sales or support contact. It is a 43-character key tied to your agreement.

If you do not have a key yet, or your existing key is close to expiring, reach out to your Fresche contact to obtain one.

Installing the key ​

You do not activate the license as a separate step — the installer applies it for you during installation. Supply the key through the OPSIQ_LICENSE_KEY environment variable before you run the installer, set the way your workstation terminal expects:

bash
export OPSIQ_LICENSE_KEY='your-43-character-license-key'
powershell
$env:OPSIQ_LICENSE_KEY = 'your-43-character-license-key'
bat
REM The quotes wrap the whole NAME=VALUE pair, so cmd strips them from the value.
set "OPSIQ_LICENSE_KEY=your-43-character-license-key"

If you do not set it, the installer prompts you for it. Once installed, the key is stored on the IBM i in a data area named PW_407 in a dedicated library. For the standard instance (opsiq) that library is OIQ1; an additional, side-by-side instance gets its own library named after the instance — see --license-library in Installation Options.

If the box already has a valid license — for example, you are reinstalling — you can tell the installer to leave it alone. See --skip-license in Installation Options.

When a license expires ​

License keys have an expiry date. When a key expires, nobody can sign in — the login page shows Authentication service temporarily unavailable — and chat, investigations, and anything else that reads live data from your IBM i fail. To confirm it is a license problem, see Runtime Issues.

Renewing a license ​

To renew, obtain a fresh key from your Fresche contact, then apply it by re-running the installer with the new key. The installer does not carry your Anthropic API key over from the existing install, so supply it again too — set OPSIQ_AI_API_KEY as below, or the installer asks for it. (On a tools-only install, leave it out.) Run this from the folder you unzipped the installer into (see Get the installer):

bash
export OPSIQ_LICENSE_KEY='your-new-43-character-license-key'
export OPSIQ_AI_API_KEY='your-anthropic-api-key'

./opsiq-install install \
  --host your-ibm-i.example.com \
  --ssh-user YOURPROFILE \
  --accept-license yes
powershell
$env:OPSIQ_LICENSE_KEY = 'your-new-43-character-license-key'
$env:OPSIQ_AI_API_KEY = 'your-anthropic-api-key'

.\opsiq-install.exe install `
  --host your-ibm-i.example.com `
  --ssh-user YOURPROFILE `
  --accept-license yes
bat
REM The quotes wrap the whole NAME=VALUE pair, so cmd strips them from the value.
set "OPSIQ_LICENSE_KEY=your-new-43-character-license-key"
set "OPSIQ_AI_API_KEY=your-anthropic-api-key"

.\opsiq-install.exe install ^
  --host your-ibm-i.example.com ^
  --ssh-user YOURPROFILE ^
  --accept-license yes
bash
export OPSIQ_LICENSE_KEY='your-new-43-character-license-key'
export OPSIQ_AI_API_KEY='your-anthropic-api-key'

./opsiq-install.exe install \
  --host your-ibm-i.example.com \
  --ssh-user YOURPROFILE \
  --accept-license yes

Once the run finishes, clear the secrets from your shell as shown at the end of Step 2. If you set ANTHROPIC_API_KEY in .env.local, that key still wins over the one you give the installer — see Upgrading OpsIQ.

The installer adds the new key alongside any existing ones, so a valid renewed key takes effect. Re-running the installer on an installed box is an upgrade: it restarts the services and health-checks the tools server as part of the run, so there is nothing to restart by hand. When it finishes with ✓ Install complete — all checks passed., the tools server is running with a valid license.

INFO

OpsIQ does not yet have a dedicated "renew license" command — re-running the installer with the new key is the supported path today. If you would rather not re-run the installer, your Fresche contact can help apply a renewal key.