InfoConnect Hub overview
InfoConnect Hub is a no-code integration solution for IBM i with a web interface (from version 4.1.0). It lets you:
- Surface IBM i business logic as REST APIs.
- Replicate IBM i data in real time.
- Automate user actions on the green screen.
You can deploy the Hub on any Java-enabled infrastructure: on-premises, in the cloud or directly on IBM i. It runs stand-alone or together with other Infoview products (such as the InfoCDC change data capture solution) and with other integration services, such as an API manager or a messaging or event streaming platform.
InfoConnect Hub also provides a ready-to-use, secure MCP server (from version 4.0.0). AI agents and chatbots use it to discover and run Hub Program Call APIs and Screen Automation APIs in AI workflows.
How the Hub documentation is organized
The Hub documentation follows the path of a typical project, from the first installation to daily operations.
| Section | What it covers |
|---|---|
| Quick start | Install the Hub, surface a program and a query as APIs, replicate data to a database, and surface a green-screen script as a REST API. |
| Installation | Deployment options: a single server or VM, containers, Kubernetes, Google Cloud Run, and clusters. License setup. |
| Data replication flows | Data Flows in the web UI, sink settings, replication to databases, file sinks, dynamic data publishing, and Data Flow states and errors. |
| API and MCP enablement | Program Call APIs, Data APIs, screen automation APIs, API management, and the MCP server for AI agents. |
| Hardening and scaling | Security hardening, authentication, user groups, availability, and monitoring. |
| Tutorials and examples | Step-by-step scenarios and examples. |
Prerequisites
IBM i
- IBM i OS version V5R4 or later.
- The Hub must reach the IBM i server on these ports:
- Non-SSL communication: 446, 449, 8470, 8472, 8473, 8475 and 8476.
- SSL communication: 448, 449, 9470, 9472, 9473, 9475 and 9476.
- The host servers
*CENTRAL,*DTAQ,*RMTCMD,*SIGNONand*SRVMAPmust run in theQSYSWRKsubsystem. - If you use a secure TLS connection, apply the TLS certificate to the Central, Data Queue, Remote Command, File, Signon and DDM / DRDA services in Digital Certificate Manager.
- The IBM i user ID must be authorized to work with the IBM i objects that you want to use.
- If additional security software restricts remote execution, allow the IBM i user ID of the connection to run remote calls and to access the database, the IFS and the DDM services.
Hub infrastructure
- Java 17.0.1 or later.
- A physical, virtual or container-based environment. The sizing depends on your usage and transaction volume, see System Requirements.
- Network access to the Hub instance for users and integrated services.
- Linux and macOS:
bash. Windows: PowerShell 5.1 or later. See Installation, Services and Updates for details.