Configuration

The majority of OpsIQ's configuration is handled automatically by the installer via the parameter values you provide. This page explains what those values are and the choices behind them. For further configuration options available after installation has completed, see Configuration Options.

The Anthropic API key

OpsIQ's AI features are powered by Anthropic's Claude models, which run as a service you connect to over the internet. You provide an Anthropic API key at install time, and the installer stores it with the AI server.

Supply the key through the OPSIQ_AI_API_KEY environment variable, set in the workstation shell you run the installer from — it is read there during setup and is never set on the IBM i. The syntax depends on your terminal:

macOS / Linux / Git Bash

export OPSIQ_AI_API_KEY='your-anthropic-api-key'

Windows (PowerShell)

$env:OPSIQ_AI_API_KEY = 'your-anthropic-api-key'

Windows (Command Prompt)

set "OPSIQ_AI_API_KEY=your-anthropic-api-key"

This is the same value used in the Install guide, where you set all the installer secrets together.

If you do not set it, the installer prompts you for it.

Where does the key come from?

The Anthropic API key is separate from your OpsIQ license. If you are not sure how to obtain one, ask your Fresche contact.

If your organization routes AI traffic through a gateway instead of contacting Anthropic directly, you can point OpsIQ at it — see Configuration Options.

Managed vs. direct install

When you install OpsIQ, you choose which IBM i user profile the services run under. This is the main configuration decision.

• Managed (the default, recommended for production). The OpsIQ services run under a dedicated OPSIQ user profile, separate from the profile you log in with. This is cleaner and safer: the services have their own identity with only the authority they need. Because the installer has to hand the services off to that profile, the SSH login you install with must be a security-officer-class profile.

• Direct (for quick setup with a single admin). The services run under the same profile you install with. No special authority is required. This is the right choice for a quick evaluation, but can be problematic if multiple users need to be able to manage the services.

  See Installation Options for how to select this option.

Ports

By default OpsIQ uses these ports on the IBM i:

Service	Default port
Web UI	3000
AI server	3939
Tools	8445

On a fresh install, if any of these are already in use, the installer automatically moves that service to the next free port and reports the change. An upgrade keeps the ports the instance already uses. To choose ports yourself, see Installation Options.

Where things live on the IBM i

• Install location: /QOpenSys/opsiq/<instance>, where <instance> is the instance name (opsiq by default). See Installation Options if you run more than one copy side by side.

• Server configuration: the AI server reads a .env the installer owns and rewrites on every upgrade, and a .env.local beside it that is yours and is never rewritten. Post-install settings go in .env.local — see Configuration Options.

• Logs: each service's logs live under the install directory, in a .pm2 folder. You can view a running service's log on the box, in a PASE shell, with (the first two lines are required — see PASE shell setup):

  PATH=/QOpenSys/pkgs/lib/nodejs22/bin:/QOpenSys/pkgs/bin:$PATH; export PATH
  PM2_HOME=/QOpenSys/opsiq/opsiq/.pm2; export PM2_HOME
  pm2 logs opsiq-server-opsiq --err

  Replace opsiq-server-opsiq with opsiq-tools-opsiq or opsiq-web-ui-opsiq for the other services. (The final word is the instance name.)

  The AI server and the web UI also keep dated log files of their own — see their own log files.

• Chat history, sessions and the audit log: a single database file, <install-root>/apps/opsiq-server/opsiq-chat.db (/QOpenSys/opsiq/opsiq/apps/opsiq-server/opsiq-chat.db for the default install). How it is protected is covered in the Data & Security FAQ.

• License: stored in a data area named PW_407 in a dedicated library (OIQ1 by default). See Licensing.