This document provides information about licensing and entitlements for IBM Cloud Pak for Integration.
The full IBM Cloud Pak for Integration licenses can be found here:
What do you purchase and what are you entitled to with Cloud Pak for Integration?
IBM Cloud Pak for Integration (5737-I89)
Supported on x86, built for Red Hat OpenShift Container Platform
The product offers a single, unified platforms for integration, with a choice of integration offerings, built into a Red Hat OpenShift Container Platform to enable deployment using Kubernetes features.
The program contains bundled offerings which include:
IBM API Connect
IBM App Connect
IBM Aspera High Speed Transfer Server
IBM DataPower Gateway Virtual Edition
IBM Event Streams
IBM MQ and IBM MQ Advanced
These offerings can be run in containers as a part of the program or as standalone deployments of these offerings outside of IBM Cloud Pak for Integration. Licensing for IBM Cloud Pak for Integration is by the VPC metric, either perpetual, monthly or a Committed Term License.
What is my enterprise entitled to install?
Deploying bundled offerings under the Cloud Pak for Integration license requires that the maximum entitlement is not exceeded at any time.
Deployments of bundled offerings under the Cloud Pak for Integration license use a ratio of IBM Cloud Pak for Integration VPC entitlements to map to bundled offering VPC entitlements. These entitlements and ratios apply whether the bundled offerings are being deployed standalone outside IBM Cloud Pak for Integration or in containers within a IBM Cloud Pak for Integration deployment. Non-production ratios can be used for both standalone and container deployments.
Production License Ratio
|Capability||VPC to License Ratio|
|App Connect Enterprise||1 : 3|
|API Connect||1 : 1|
|DataPower||1 : 1|
|MQ Advanced||2 : 1|
|MQ Advanced High Availability Replica||10 : 1|
|MQ base||4 : 1|
|MQ High Availability Replica||20 : 1|
|Event Streams||1 : 1|
|Aspera High Speed Transfer Server 1 Gbps||1 : 4|
Non-Production License Ratio
|Capability||VPC to License Ratio|
|App Connect Enterprise||2 : 3|
|API Connect||2 : 1|
|DataPower||2 : 1|
|MQ Advanced||4 : 1|
|MQ Advanced High Availability Replica||20 : 1|
|MQ base||8 : 1|
|MQ High Availability Replica||40 : 1|
|Event Streams||2 : 1|
|Aspera High Speed Transfer Server 1 Gbps||1 : 2|
Red Hat OpenShift licenses
Deployments of bundled offerings such as API Connect, MQ or Aspera as part of a IBM Cloud Pak for Integration deployment require deployment of Red Hat OpenShift Container Platform. The license entitlement for Red Hat OpenShift Container Platform is provided 1:1 with the number of IBM Cloud Pak for Integration VPCs that the customer has entitlement to.
This number of VPCs of RH OpenShift doesn’t vary by the ratio of the bundled offerings. Therefore, the number of cores required for deployment of bundled offerings in IBM Cloud Pak for Integration can exceed the number of RH OpenShift VPCs available as part of the license entitlement for IBM Cloud Pak for Integration. In these cases, the customer should acquire additional license entitlement for RH OpenShift to ensure they are correctly licensed at all times.
In addition to requiring RH OpenShift entitlement for IBM Cloud Pak for Integration components (charged and non-charged), there must also be RH OpenShift entitlement for the containers where the Cloud Pak Common Services are running. These are required for each RH OpenShift cluster deployed.
Note that as customer deployments of IBM Cloud Pak for Integration bundled offerings might vary through the ratio for each offering and for production vs. non-production, customers will need to ensure they have sufficient RH OpenShift entitlement for all deployments at all times.
Aspera deployments and bandwidth entitlements
When deploying Aspera High Speed Transfer Server in a container in IBM Cloud Pak for Integration, additional entitlement enables the use of a higher bandwidth entitlement. For a production deployment 4 VPCs of IBM Cloud Pak for Integration entitles the use of 1 Gigabit per second. An additional 4 VPCs of IBM Cloud Pak for Integration will provide entitlement to use an additional 1 Gigabit per second. For non-production deployments 2 VPCs of IBM Cloud Pak for Integration entitles the use of 1 Gigabit per second etc.
The Aspera High Speed Transfer Server must be deployed in a container deployed in the OpenShift Container Service environment supporting IBM Cloud Pak for Integration. The customer must have sufficient OpenShift entitlement for the Aspera High Speed Transfer Server container deployment.
For deployments of Aspera High Speed Transfer Server outside IBM Cloud Pak for Integration containers, the ratio remains the same but is fixed at 1 Gigabit per second. 4 VPCs of IBM Cloud Pak for Integration entitle deployment of Aspera High Speed Transfer Server ‘standalone’ at a bandwidth speed of 1 Gigabit per second for production use. 2 VPCs of IBM Cloud Pak for Integration are for 1 Gigabit per second for non-production use.
The ratio of IBM Cloud Pak for Integration VPCs to deployment cores of Aspera High Speed Transfer Server is not used, but instead a measure of bandwidth is used to represent the value provided by Aspera High Speed Transfer Server.
What consumes IBM Cloud Pak for Integration license entitlements according to the ratio?
Non-charged entitlements for Cloud Pak for Integration
The deployment ratios apply to the bundled programs within Cloud Pak for Integration only. Additional Cloud Pak for Integration components can be deployed without requiring Cloud Pak for Integration VPCs to be counted against their deployment. These include features such as Platform Navigator, Asset Repository, and Operations Dashboard.
Operations Dashboard add-on part
There is no charge to use the Operations Dashboard component included in Cloud Pak for Integration, but it is subject to some restrictions around data retention and other aspects. These restrictions can be removed by purchasing the Operations Dashboard add-on part which is sold using the VPC metric.
Customers wanting to use the unrestricted Operations Dashboard need to buy sufficient VPCs of the Operations Dashboard add-on part to match the number of VPCs of the bundled program or programs with which they are using the Dashboard. They don’t need to buy VPCs equal to their total Cloud Pak for Integration VPC entitlement if they are not using the Dashboard with some of their deployed bundled programs (production or non-production).
Reporting on deployment inside and across OpenShift clusters
Products reporting using the PVU metric
Customers with entitlements outside IBM Cloud Pak for Integration may have been using licensing using PVUs and reporting deployments with ILMT for sub-capacity measurements.
ILMT would keep a track of what software programs were deployed on what physical hardware and provide reporting for customers to provide to IBM as requested in order to demonstrate compliance to entitlement capacity.
IBM Cloud Pak for Integration reporting using the VPC metric.
Deployments under IBM Cloud Pak for Integration entitlement can continue to be deployed on the same hardware, and in the same VMs as previously measured and reported with PVUs. However, under the VPC metric there is no requirement to use ILMT. Customers still are required to keep a record of the size of deployments to report to IBM as requested.
Deployments of bundled programs in containers under IBM Cloud Pak for Integration VPC entitlements can be reported using the container size through reporting using the License Service available to Cloud Pak deployments.
This can be configured to report on the deployments of each bundled program in each container, along with the container size, and how that relates, using the ratio, to IBM Cloud Pak for Integration entitlements.
This deployment reporting is aggregated for each OpenShift cluster to provide a high-water mark of deployment to track against customer IBM Cloud Pak for Integration entitlements.