Licensing

Full licenses include 3 cores of OpenShift for every virtual processor core (VPC) of Cloud Pak for Integration.

To review the license agreements for any of the following full IBM Cloud Pak for Integration licenses, click the link for that license:

• IBM Cloud Pak for Integration 2021.4.1 (L-RJON-C7QG3S)

• IBM Cloud Pak for Integration 2021.3.1 (L-RJON-C5CSNH)

• IBM Cloud Pak for Integration 2021.2.1 (L-RJON-BZFQU2)

• IBM Cloud Pak for Integration 2021.1.1 (L-RJON-BXUPZ2)

• IBM Cloud Pak for Integration 2020.4.1 (L-RJON-BUVMQX)

• IBM Cloud Pak for Integration 2020.3.1 (L-RJON-BQPGWD)

Reserved or limited edition licenses do not include OpenShift entitlement. They are intended for organizations that either have an existing Red Hat OpenShift entitlement, or commit to using Cloud Pak for Integration on public cloud environments with managed OpenShift. Prior IBM approval is required.

The reserved or limited edition IBM Cloud Pak for Integration licenses can be found here:

• IBM Cloud Pak for Integration Reserved 2021.4.1 (L-RJON-C7QFZX)

• IBM Cloud Pak for Integration Limited Edition 2021.3.1 (L-RJON-C5CSM2)

• IBM Cloud Pak for Integration Limited Edition 2021.2.1 (L-RJON-BZFQSB)

• IBM Cloud Pak for Integration Limited Edition 2021.1.1 (L-RJON-BXUQ34)

• IBM Cloud Pak for Integration Limited Edition 2020.4.1 (L-RJON-BUVMYB)

• IBM Cloud Pak for Integration Limited Edition 2020.3.1 (L-RJON-BSTLF7)

The full IBM Cloud Pak for Integration licenses can be accessed on the cluster at the following address:

https://<home>/integration/static/media/<license_title>.txt

To find values for the placeholders in the URL:

• <home> is the host of the Cloud Pak, for example, cpd-namespace.acme.cloud.com. To get the value of <home>, do one of the following:

  • in the OpenShift web console, select the Project (namespace) where the instance of the Cloud Pak instance is deployed, then locate and click the route called cpd.

  • run the this command in OpenShift Container Platform CLI, replacing <namespace> with the project/namespace where the Cloud Pak instance is deployed:

  oc get route cpd -n <namespace>

• <license_title> can take one of the following values:

  • LA_cs-reserved

  • LA_de

  • LA_de-reserved

  • LA_el

  • LA_el-reserved

  • LA_en

  • LA_en-reserved

  • LA_es

  • LA_es-reserved

  • LA_fr

  • LA_fr-reserved

  • LA_in

  • LA_in-reserved

  • LA_it

  • LA_it-reserved

  • LA_ja

  • LA_ja-reserved

  • LA_ko

  • LA_ko-reserved

  • LA_lt

  • LA_lt-reserved

  • LA_pl

  • LA_pl-reserved

  • LA_pt

  • LA_pt-reserved

  • LA_ru

  • LA_ru-reserved

  • LA_sl

  • LA_sl-reserved

  • LA_tr.txt

  • LA_tr-reserved

  • LA_zh

  • LA_zh-reserved

  • LA_zh_TW

  • LA_zh_TW-reserved

  • non_ibm_license

  • non_ibm_license-reserved

  • notices

  • notices-reserved

Instances in Cloud Pak for Integration are charged at different rates based on their ratios. The ratios apply to the deployed instances. Entitlements of Cloud Pak for Integration that are used in these ratios can be reused in other ratios at any time, as long as the total entitlement is not exceeded. There is no limit to the number of times that entitlements can be used in different combinations.

Production License Ratio

Non-Production License Ratio

The deployment ratios apply to the bundled programs within Cloud Pak for Integration only. Additional Cloud Pak for Integration instances can be deployed without requiring Cloud Pak for Integration VPCs to be counted against their deployment. These include features such as Platform UI, Automation assets, and integration tracing.

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 instances, not for other 3rd party deployments or custom code. If you deploy other code or components (such as agents used for monitoring IBM Cloud Pak for Integration capabilities), you must make additional unrestricted OpenShift licenses available to the cluster. However, the workload that you run on unrestricted OpenShift entitlement doesn’t need to be deployed separately. These agents, which run alongside the integration components and then send the monitoring data out to a separate monitoring component, can be run in the same nodes or namespaces as components running in restricted Red Hat OpenShift Container Platform cores. You must ensure that for all non-restricted workloads, a sufficient number of unrestricted cores of OpenShift are available to the cluster. See Restricted OpenShift entitlement for IBM Cloud Paks for more information.

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 instances (charged and non-charged), there must also be RH OpenShift entitlement for the containers where the IBM Cloud Pak foundational 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.

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 Data Foundation (formerly OpenShift Container Storage)

• IBM Spectrum Protect Plus

The entitlement is limited to 12TB of allocated storage of Red Hat OpenShift Data Foundation. 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. In addition 4TB of allocated storage is available for IBM Spectrum Protect Plus.

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. This starts from when the customer first purchases Cloud Pak for Integration. If the customer purchased Cloud Pak for Integration before December 11th, 2020, the entitlement lasts for 36 months, starting from December 11th, 2020. An entitlement to IBM Storage Suite for IBM Cloud Paks ends when the entitlement to IBM Cloud Pak for Integration ends, for example, at the end of a subscription term, or if the client's Subscription and Support entitlement ends. An additional entitlement to IBM Storage Suite for IBM Cloud Paks can be purchased separately.

When deploying MQ in containers under Cloud Pak for Integration licensing, you can choose the Native HA configuration for High Availability. This option is designed for container deployments of MQ without external dependencies, such as shared storage or kernel modifications. When deployed in this configuration, an active MQ Queue Manager replicates to 2 additional Queue Managers, which are used only as replicas for this active Queue Manager. Licensing for this configuration requires that the active Queue Manager be licensed using the MQ Advanced ratio, but the replica Queue Managers do not require licensing, meaning they don't consume Cloud Pak for Integration VPCs at any ratio. However, all Queue Managers are deployed on Red Hat OpenShift, and all OpenShift cores require entitlement.

When deploying Aspera High Speed Transfer Server in a container in IBM Cloud Pak for Integration, entitlement enables the use of Aspera High Speed Transfer Server at 1 Gigabit per second. For a production deployment 4 VPCs of IBM Cloud Pak for Integration entitles the use of 1 Gigabit per second.

For non-production deployments 2 VPCs of IBM Cloud Pak for Integration entitles the use of 1 Gigabit per second.

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 and is also 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.

The "API Connect Enterprise" license provides entitlement to the full API Connect product and tracks usage by the number of installed VPCs.

The "IBM Cloud Pak for Integration - API Calls" is an add-on that entitles you to track usage by the monthly number of API calls instead of the number of installed VPCs.

For more information, see API Connect licenses in the API Connect documentation.

The "IBM DataPower Gateway Virtual Edition - Production Edition" license is included in Cloud Pak for Integration. While you are able to deploy a gateway instance in either production or nonproduction mode, a production image will always be deployed which is specific to Cloud Pak for Integration. This means that the licensing metrics and annotations on the gateway pods will always reflect the production edition, even if deployed in nonproduction usage. However, the Cloud Pak ratio does change depending on the license usage. When production is chosen as the license usage, the ratio is 1:1 for VPCs. When nonproduction is chosen as the license usage, the ratio is 2:1 for VPCs.

A custom datapower-cp4i image is always used when a gateway instance is created within Cloud Pak for Integration, including when used as an API runtime within API Connect. This datapower-cp4i image is based on the datapower-prod (production) image, and also includes the Integration Module. For more information, see Cloud Pak for Integration: Gateway runtime.

There is no charge to use the Operations Dashboard capability that is 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).