MQ and Tivoli Licensing.

The IBM MQ and Tivoli licensing reference. The MQ Advanced versus MQ Standard split, the Tivoli portfolio editions, the PVU and VPC entitlement, sub capacity coverage, and the common deployment patterns that drive over consumption.

What is inside.

• The edition structure for MQ (Standard, Advanced, Appliance, FTE) and Tivoli (Monitoring, NetCool, OMNIbus, Workload Scheduler, Identity Manager). The entitlement boundary for each edition.
• The PVU and VPC metric definitions for MQ and Tivoli. The sub capacity eligibility map, the ILMT requirement, the per core conversion ratios.
• MQ deployment patterns: clustered queue managers, multi instance, replicated data queue managers. The PVU implications of each pattern and the common over deployment traps.
• The Tivoli monitoring agent footprint. The PVU count of the monitored servers. The distinction between the management server entitlement and the agent entitlement. The shelfware risk.
• Sub capacity coverage for MQ and Tivoli. The ILMT scan coverage of the MQ and Tivoli binaries. The bundle file reading for the MQ Appliance. The audit position on sub capacity reporting.
• Migration patterns: MQ to App Connect, Tivoli to Instana, NetCool to Watson AIOps. The contractual handling, the swap rights, the support and subscription credit option.
• The MQ and Tivoli audit posture. The IBM tendency to audit the middleware estate. The PVU evidence required, the sub capacity reporting standard, the version compliance question.
• The buyer side close position on MQ and Tivoli. The four commercial asks, the three contractual asks, the two operational disciplines. The relationship to the broader middleware portfolio.

Who this is for.

• The integration architect operating the MQ messaging estate.
• The operations director managing the Tivoli monitoring stack.
• The procurement lead negotiating the middleware renewal.
• The CIO consolidating the middleware portfolio onto Cloud Pak.