IBM MQ and mqweb version support¶
Not certified yet
ADR-0002 requires documenting supported IBM MQ/mqweb versions and deployment modes. No combination is certified in this repository yet. The matrix below records intent, unknowns, and the evidence required before a row can move to Supported.
Authority: design question 13, FND-004 (live MQ environment), MSG-001 (mqweb semantics spike).
Connectivity baseline¶
First-release downstream access is mqweb REST only (ADR-0002). Native PCF/MQI is deferred. Implications:
- mqweb must be installed, enabled, reachable, and authorized.
- Standalone mqweb vs full-install mqweb capabilities differ — both must be tested before support claims.
- REST does not provide MQI transaction/syncpoint or high-throughput semantics.
Support matrix (TBD)¶
Status legend:
| Status | Meaning |
|---|---|
| Unknown | Not tested; do not deploy for production use |
| Planned | In scope for validation via FND-004 / MSG-001 |
| Supported | Documented, tested, listed in release notes — none yet |
| IBM MQ major | Platform | mqweb deployment mode | Admin REST | Messaging REST | Status | Notes |
|---|---|---|---|---|---|---|
| IBM MQ 9.4.x | Linux x86_64 (Kind) | Full install (Helm) | Planned | Planned | Planned | MKurator Kind stack 9.4.5.1-r1; FND-004 e2e reachability |
| IBM MQ 9.4.x | Linux x86_64 (Docker) | Full install | Planned | Planned | Planned | MKurator hack/mq-docker; lighter local path |
| TBD | Linux x86_64 | Standalone mqweb | Unknown | Unknown | Unknown | Capability gaps vs full install |
| TBD | Linux arm64 | Full install | Unknown | Unknown | Unknown | Container multi-arch build exists; MQ validation TBD |
| TBD | Windows | Full install | Unknown | Unknown | Unknown | Not prioritized until evidence |
| TBD | z/OS | TBD | Unknown | Unknown | Unknown | Explicit later extension (feature scope) |
Replace TBD cells with tested version ranges when FND-004 records evidence. Do not infer support from IBM documentation alone.
Messaging REST risks (pre-certification)¶
These behaviours must be proven non-destructive before browse ships (MSG-001):
- Browse vs get/consume semantics on target mqweb versions
- Payload formats and size limits
- Selector and property support gaps vs native clients
Operator guidance until certified¶
- Treat all MQ versions as unsupported for production AI-driven access.
- Use the bootstrap server without MQ connectivity for MCP host integration testing.
- Track roadmap for FND-004 and MSG-001 completion.
- Never claim exactly-once, transactional, or high-throughput behaviour over REST (ADR-0002 guardrails).