IBM Integration Bus and ACE Licensing

IBM Integration Bus, the integration broker many estates still run, has a successor in App Connect Enterprise, and the move between them is one of the most overlooked audit moments in middleware. The product changes, the entitlement has to change with it, and the gap is where the finding lives. A migration is a licensing event, not just an upgrade.

From Integration Bus to App Connect Enterprise

IBM Integration Bus, the descendant of the older message broker line, is licensed on capacity, typically PVU where value units per core times the allocated cores set the count, or VPC for the editions metered on virtual processor cores. App Connect Enterprise, often called ACE, is the modern continuation of the same integration capability and combines the broker with newer connectivity. It is metered on capacity too, but the entitlement, the edition structure, and the packaging are not identical to the older product. Running ACE on an Integration Bus entitlement, or the reverse, is the kind of mismatch an audit is built to find.

Where the migration creates exposure

• New product on an old entitlement: ACE deployed while the entitlement still names Integration Bus
• Parallel running: the old and new products live at once during cutover, each needing coverage
• Capacity growth at migration: the new deployment sized larger than the entitlement that was carried over
• Sub-capacity reporting gap: the reporting tool not updated to track the new product, voiding the virtual count

How sub-capacity applies to both

Both Integration Bus and ACE can be licensed sub-capacity, meaning you license the virtual cores running the software rather than every core on the host, but only with an approved tool such as ILMT deployed within 90 days, running continuously, and producing quarterly reports retained two years. The migration trap is that the reporting tool keeps watching the old product signature and never picks up the new one, so the period after cutover has no valid sub-capacity record and defaults to full-capacity. The software was upgraded; the reporting was not, and the count pays for the difference.

How buyers defend it

We map the integration estate across both products and align each deployment to the entitlement that actually covers it, treating the migration as the licensing event it is. Where ACE runs on an Integration Bus entitlement, we test whether a trade up or conversion right applies before accepting a shortfall, because IBM migration paths often carry one. Where parallel running inflated the count during cutover, we contain it to the overlap window rather than the full lookback. And we confirm the reporting tool sees the new product so the sub-capacity claim holds for the period after migration.