Licensing

Full licenses include 3 cores of Restricted Red Hat OpenShift Container Platform for each 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 2022.2.1 (L-RJON-CD3JKX)

• 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)

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 Limited Edition 2022.2.1 and IBM Cloud Pak for Integration Reserved 2022.2.1 (L-RJON-CJR2WN)

• 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)

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 that is called cpd.

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

  oc get route cpd -n <namespace>

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

• Other documents:

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

• Process Mining Platform - Conversion Flat Entitlement: A customer with Cloud Pak for Integration entitlement is allowed to convert 3 VPCs of Cloud Pak for Integration for 1 installation of the Process Mining Platform. Regardless of the number of Cloud Pak for Integration entitlements, the customer is limited to a one-time listed conversion to provide entitlement to the Process Mining Platform.

• With every installation of IBM Process Mining Platform, the customer gets entitlement to 3 Process Mining Processes, 20 Million Events, 1 Analyst User, 3 Business Users, and 2 Task Mining Agents.

Non-Production License Ratio

The following table explains which components consume OpenShift entitlement, Cloud Pak for Integration entitlement by using license ratios, or both:

Deployments of IBM API Connect (which always include deployments of IBM DataPower as the secure gateway runtime), sometimes report the DataPower instance to the License Service as "DataPower", not "API Connect". Because DataPower is deployed at the same ratio as API Connect, reporting the instance by a different name does not change the total VPCs reported.

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.

For first-time purchases of Cloud Pak for Integration from July 1st, 2022 onwards, there is entitlement to limited quantities of IBM Spectrum Fusion for 12 months. This entitlement only applies to the first purchase and expires 12 months after purchase, or when the entitlement to Cloud Pak for Integration ends (if within 12 months).

The entitlement includes 6 TB of primary storage, which includes OpenShift Data Foundation Essentials. Also included is 6 TB of Backup Storage and 6 TB of Metadata Management. Customers are entitled to use this software-defined storage for any data usage during the 12 month entitlement. This covers any data usage, not just data used within Cloud Pak for Integration.

The entitlement to OpenShift Data Foundation Essentials that is included in this offer cannot be used in a public cloud-managed OpenShift environment.

Additional purchases of Cloud Pak for Integration do not provide entitlement for any additional quantity of IBM Spectrum Fusion or for any additional length of time for entitlement. If additional storage quantity is needed or additional time is required, then new entitlement for IBM Spectrum Fusion should be purchased separately.

Customers who purchased Cloud Pak for Integration for the first time before July 1, 2022 have different entitlement for software-defined storage, and these entitlements are not impacted by this new entitlement. Customers who purchased Cloud Pak for Integration before July 1, 2022 do not get entitlement to Spectrum Fusion.

When deploying MQ in containers under Cloud Pak for Integration licensing, you can choose the Native high-availability (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. However, the replica Queue Managers do not require licensing, because they don't consume Cloud Pak for Integration VPCs at any ratio. By contrast, if Queue Managers are deployed on Red Hat OpenShift Container Platform, all OpenShift cores require entitlement.

MQ Native HA can also be deployed in containers on other Kubernetes platforms. For more information, see Native HA.

When deploying MQ in containers under Cloud Pak for Integration licensing, another option for high availability (HA) is "multi-instance queue managers":

• This option is designed for deployments where an active MQ queue manager writes persistent messages and logging data to network-attached storage.

• The active MQ queue manager has a lock on the network-attached storage.

• A replica queue manager, which is connected to the same storage, is ready to take over in case of the failure of the active queue manager. This failure releases the storage lock and allows the replica queue manager to become the active queue manager.

When deploying MQ in multi-instance configurations outside of containers, the active queue manager is fully licensed by the regular MQ or MQ Advanced license, but the replica queue manager is licensed using the MQ HA Replica or MQ Advanced HA Replica part.

When deploying MQ in a multi-instance configuration in containers (under Cloud Pak for Integration licensing), a different approach is needed, because the replica queue manager is not tracked by the License Service. To ensure license consistency, the active queue manager uses a ratio that includes the licensing cost of the replica queue manager. To address this, the License Information document provides an option with a "Deployment model" called Multi-Instance Containers; select that option when deploying this type of configuration.

When deploying Aspera High Speed Transfer Server in a container in IBM Cloud Pak for Integration, the following entitlement enables the use of Aspera High Speed Transfer Server at a bandwidth speed of 1 Gigabit per second:

• For a production deployments, 4 VPCs of Cloud Pak for Integration.

• For nonproduction deployments, 2 VPCs of Cloud Pak for Integration.

Aspera High Speed Transfer Server must be deployed in a container within the OpenShift Container Service environment that supports Cloud Pak for Integration. The customer must have sufficient OpenShift entitlement for deployment in this container.

For deployments of Aspera High Speed Transfer Server outside Cloud Pak for Integration containers, the entitlement ratio remains the same as for deployment in containers, and is also fixed at a bandwidth speed of 1 Gigabit per second:

• For production use of stand-alone Aspera High Speed Transfer Server, 4 VPCs of Cloud Pak for Integration.

• For nonproduction use of stand-alone Aspera High Speed Transfer Server, 2 VPCs of Cloud Pak for Integration.

Note that bandwidth measure is used to represent the value provided by Aspera High Speed Transfer Server, rather than the ratio of Cloud Pak for Integration VPCs to deployment cores of 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. Customers need to track and report the number of API Calls made each month. The entitlement is counted on a month-by-month basis rather than being averaged or aggregated over the period of the subscription license. For more information, see Tracking API volume for auditing and compliance.

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. In addition to the Integration Module, customers using DataPower with Cloud Pak for Integration entitlements are entitled to use the Application Optimization Module and the B2B Module at no additional charge.

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 nonproduction).