How do I set up or debug a Hub connector (IMS, DB2, Kafka, JDBC, SOAP, MQ)?

Q: How do I set up or debug a Hub connector (IMS, DB2, Kafka, JDBC, SOAP, MQ)?

Match the Hub connector to the backend, fill the connection profile, then test connection and test asset before building a flow.

Pick the connector that matches the backend, not a nearby one. IMS DB, CICS, DB2, Kafka, JDBC, SOAP, and MQ are separate assets and connection models in OL Integration.

Use Mainframe connectors, IBM i connectors, or on-prem / legacy connectors as appropriate.

Setup

ol list connectors (or Designer) → create a module with that connector.
Fill the connection profile (host, port, credentials, code page, SSL).
Add assets (copybook, PCML, SQL, OpenAPI, and so on) then test connection and test asset before you build a flow.

Debug

Test asset in Hub or ol test asset / ol test-operation so you isolate connector vs flow.
Connector logs (including SDK-based ones) are on the runtime/agent that actually talks to the host — not only the Hub UI.
A 404 on a docs URL does not mean the connector is unsupported; use the current Hub connector catalog.

Host prerequisites (for example IMS DB libraries, DB2 packages, Kafka ACLs) are backend requirements. OpenLegacy cannot invent access the host does not grant.