Skip to content

Hardening and scaling

This page collects what you need to run IBM i APIs and the MCP server reliably in production: security, access control, availability, deployment, and monitoring. Each section links to the product guide with the details.

Security

A default Hub installation has predefined credentials, an HTTP listener, and no encrypted IBM i connection. Complete this checklist before you make APIs available:

  • Change the default user IDs and passwords of the Admin API and the Functional API.
  • Configure HTTPS for the API listener.
  • Configure a TLS connection to IBM i.
  • Change the encryption key for sensitive properties, and encrypt all stored credentials.
  • Restrict access to the APIs to allowed source IP addresses.
  • Add rate limiting and other security policies to protect the Functional APIs, for example in an API manager.

See Security hardening and IBM i TLS connection configuration.

Authentication and access control

  • OAuth. Use the authorization server to authenticate with an OAuth provider instead of Basic authentication. See OAuth configuration.
  • User groups and permissions. Assign users to groups and give each group access to specific Program Calls, Data APIs, and RPA Calls. See User groups and permissions.
  • MCP tools. The same permissions apply to the generated MCP tools. The MCP server provides only the tools that the signed-in user is allowed to use, and users cannot invoke other tools. See MCP integration.

Request validation and API lifecycle

  • Define parameter mapping and validation rules so that the Hub rejects invalid requests before they reach IBM i. See API parameters and validation.
  • Activate and deactivate APIs without changing their definitions. See Managing Hub APIs.
  • For screen automation, restrict direct access to the RPA Hub to localhost or an IP allow-list. See the RPA Hub user guide.

Control which tools AI agents see

The MCP server loads the tools from the Hub when it starts and can reload them on a schedule. Configure the tool initialization, the reload interval, and the schema logging to match how often your APIs change. See Tool initialization and reload configuration. Use the MCP Explorer to review the tools that agents can see.

Availability and scaling

Observability and log aggregation

  • Logs. Each module writes an output log and an error log to the log folder. See Log files.
  • Log levels. The Hub and MCP log at INFO by default; the RPA Hub logs its own packages at DEBUG. To log only warnings and errors, set the InfoConnect packages to WARN; use DEBUG only while troubleshooting. See Log levels.
  • Health checks. The Hub and the MCP server provide /actuator/health. The Hub health check reports only that the process is up. It does not check the metadata database or the connection to IBM i. See Health check.
  • Aggregation tools. The log files are plain files in a known folder, so your standard log shipper can forward them to platforms such as Splunk or the Elastic stack.
  • Outbound calls from IBM i. webTF records transaction tracking and exception details that you can stream into log aggregation, alerting, and monitoring platforms. See the webTF user guide.