Licensing

This document provides information about licensing and entitlements for IBM Cloud Pak® for Integration.

Full licenses

The full IBM Cloud Pak for Integration licenses can be found here:

License versions

License Use Description
L-RJON-BUVMQX Production or non production IBM Cloud Pak for Integration 2020.4.1
L-RJON-BUVMYB Production or non production IBM Cloud Pak for Integration Limited Edition 2020.4.1
L-RJON-BQPGWD Production or non production IBM Cloud Pak for Integration 2020.3.1
L-RJON-BN7PN3 Production or non production IBM Cloud Pak for Integration 2020.2.1
Note: A "limited Edition" license is different from a regular license in that it doesn't include any OpenShift entitlement. It is provided to organizations that have existing Red Hat OpenShift entitlement or plan to use the license only on public cloud environments with managed OpenShift. Prior IBM approval is required.

What do you get with your purchase of Cloud Pak for Integration, and what is your entitlement?

IBM Cloud Pak for Integration offers a single, unified platform for integration, with a choice of integration offerings, built into a Red Hat OpenShift Container Platform to enable deployment using Kubernetes features. The product is supported on both x86 and Linux for IBM z.

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. Not all offerings or components of IBM Cloud Pak for Integration are supported currently on Linux on IBM z.

When you deploy bundled offerings—such as API Connect, MQ, or Aspera—under the IBM Cloud Pak for Integration license, you must not exceed the maximum entitlement at any time. Deployment of Red Hat OpenShift Container Platform is required for deployment of bundled offerings within IBM Cloud Pak for Integration.

Differences in License terms

The license terms for Cloud Pak for Integration supersede the license terms of the bundled offerings. However, this policy applies only when there is a conflict of terms. Terms which apply to the bundled programs still apply, if not superseded. Examples of this situation are deployments of IBM App Connect which allow for instances to be deployed without charge for development use or unit/functional test use.

Note: All deployments of App Connect which are deployed on Red Hat OpenShift Container Platform must have sufficient entitlement for the Red Hat OpenShift Container Platform cores that are used.

License ratios

Components of the Cloud Pak for Integration are charged at different rates based on their ratios.

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

When bundled offerings such as API Connect, MQ, or Aspera are deployed as part of a IBM Cloud Pak for Integration deployment, deployment of Red Hat OpenShift Container Platform is required. License entitlement for the Red Hat OpenShift Container Platform is provided 3:1 with the number of IBM Cloud Pak for Integration virtual processor cores (VPCs) to which the customer has entitlement. This means the customer gets 3 cores of Red Hat OpenShift Container Platform for each VPC of Cloud Pak for Integration to which they have entitlement. The licenses for Red Hat OpenShift Container Platform that are included in the IBM Cloud Pak for Integration entitlement are restricted licenses. They can be used only for deployments of IBM Cloud Pak for Integration components, not for other 3rd party deployments or custom code.

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 IBM Cloud® Platform Common Services are running. These are required for each RH OpenShift cluster deployed.

Because 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.

Limited entitlement to IBM Storage Suite for IBM Cloud Paks

A limited entitlement to IBM Storage Suite for IBM Cloud Paks is included with entitlement to IBM Cloud Pak for Integration. Not all features of IBM Storage Suite for IBM Cloud Paks are included in this entitlement.

These features are included:

  • IBM Spectrum Scale

  • IBM Spectrum Virtualize

  • IBM Spectrum Discover

  • Red Hat OpenShift Container Storage

The entitlement is limited to 12TB of allocated storage of Red Hat OpenShift Container Storage. There is an additional entitlement of 12TB of allocated storage that can be used in aggregate across IBM Spectrum Scale, IBM Spectrum Virtualize, and IBM Spectrum Discover.

This entitlement to IBM Storage Suite for IBM Cloud Paks is available once per customer, and is not dependent on the number of VPCs of Cloud Pak for Integration that have been purchased. The limited entitlement lasts for 36 months. Additional entitlement to IBM Storage Suite for IBM Cloud Paks can be purchased separately.

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?

Entitlement consumption
Note: Deployments of IBM API Connect which include deployments of IBM DataPower as the secure gateway component may report the DataPower instance to the License Service as "DataPower", not "API Connect". Because DataPower is deployed at the same ratio as API Connect, this does not change the total VPCs reported.
Note: App Connect flows that are created in App Connect Designer include additional containers in the App Connect Pod to account for the features created in Designer. These additional containers in the pod increase the reported chargeable size. Therefore, IBM recommends that you review the default container size to ensure the reported total reflects your actual usage.

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.

For containers under IBM Cloud Pak for Integration VPC entitlements, the license service available to Cloud Pak deployments can be configured to report the deployments of each bundled offering in each container. It can also report the container size and how that relates—using the VPC-to-license ratio—to IBM Cloud Pak for Integration entitlements.

VPC consumption reporting

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.

VPC consumption reporting

For more information about the IBM Cloud Platform License Service as used by deployments of IBM Cloud Pak for Integration please refer to the appropriate Knowledge Center here https://www.ibm.com/support/knowledgecenter/SSHKN6/license-service/1.x.x/license_service.html