IBM Cloud Pak for

Integration

Packaging, Pricing & Sizing

Guide
Dec 2nd, 2021

IBM Confidential
© 2021 IBM Corporation
Purpose of this deck
 To explain and clarify how CP4I is packaged, how it is sold
 Covers most common deployment and pricing questions for different deployment options
 Explains how sizing works
 Should be used in combination with other Seismic resources to answer customer questions
Licensing FAQ OCP Entitlement calculator

© 2021 IBM Corporation

Cloud Pak for Integration | Package Entitled through CP4I VPCs
(OpenShift uses 3:1 ratio per CP4I VPC)
IBM Cloud Pak for Integration
• All components
Capabilities: Foundation: are deployed on
Paid (CP4I VPCs use ratio to deploy components) Red Hat OpenShift OpenShift cores.
Run on entitled OpenShift cores • All OpenShift
worker node cores
API Connect App Connect Unpaid (no CP4I VPCs consumed) need entitlement.
Value-add features for Cloud Paks • CP4I provides
MQ/MQ Advanced Event Streams
entitlement to 3
Aspera DataPower Foundation cores of OpenShift
Event Endpoint Services for each 1 VPC of
Management Logging,
Automation CP4I
Monitoring, Foundation
RPA Process Mining Access Control,
Metering, Licensing

Unpaid (no CP4I VPCs consumed if used).

Value-add features for CP4I

Ops Dashboard Automation Assets

Storage Suite for Cloud
Platform Nav Paks

CP4I Add-on components: Confluent Platform API Calls Aspera Enterprise

© 2021 IBM Corporation 3
Selling/Licensing CP4I | New Sale
• Cloud Pak for Integration (CP4I) licensed in VPCs – measuring deployed capacity
• Sold as Subscription, monthly or perpetual

License type Part Number Cost

Subscription (CTL) D2689LL $934/VPC/Month
Perpetual D20ZBLL $28000/VPC
Monthly D211KLL $1160/VPC/Month

Parts for Linux on Z

License type Part Number Cost

Subscription (CTL) D268BLL $934/VPC/Month
Perpetual D20ZILL $28000/VPC
Monthly D211LLL $1160/VPC/Month

© 2021 IBM Corporation 4

Selling/Licensing CP4I | Trade-up from Existing Software
• Existing perpetual integration software can have perpetual entitlement traded-up
to CP4I perpetual entitlement

License type Part Number When to offer trade-up?

Perpetual D20ZFLL • Offer trade-up to coincide with S&S renewal
• Suggest combining trade-up with buying net
Parts for Linux on Z
new additional capacity
License type Part Number • Consider whether to offer trade up to
Perpetual D20ZKLL subscription entitlement (CTL) –
read more here
• Trade-up process run through Project Office
• https://w3.ibm.com/w3publisher/flexofferings/trade-up
• Email Cloud Trade-Up Project Office tradeup@us.ibm.com
• Why Trade up to Cloud Pak for Integration
• Unique Value of CP4I vs individual products
© 2021 IBM Corporation 5
Cloud Pak for Integration Reserved (was Limited Edition)
Full version of CP4I without the RedHat OpenShift entitlements

Why Reserved?
Many customers want to bring their own
RedHat OpenShift licenses because:

They have an Enterprise OpenShift

Agreement with RedHat

They are bringing their CP4I licenses to

be deployed on an AWS managed
instance that includes OpenShift (ROSA)
or on Azure (ARO)

Customer is still required to deploy

on RedHat OpenShift

Customer can not revert to a CP4I

license that includes OpenShift

6
© 2021 IBM Corporation
CP4I Limited Edition approval process

• Once you confirm with the customer that they will be bringing their own RH OCP licenses:

• Obtain approval on the use of the Reserved part and discount % required from your GEO Leader
• Please include confirmation of how the customer will be supplying RH OCP licenses and that
they understand the part does not include RH OCP entitlements

• GEO Leader will submit approval to WW Sales (Mike McGee) who will get approval from:
• Labros Kisouras - WW Sales VP
• Leif Davidsen – Cloud Pak for Integration Product Manager

• You can then submit the SQO with the approvals attached

7
© 2021 IBM Corporation
Cloud Pak for Integration | Value-Add Components
• Cloud Pak for Integration provides value-add components
• Platform Navigator
• User interface to access the features of the Cloud Pak for Integration
• Automation Assets (was Asset Repository)
• Store, manage and share integration assets, using them across the capabilities.
• Operations Dashboard
• Cross-component transaction tracing

• Operations Dashboard features are limited within standard CP4I use

• Trace data can’t be exported outside the Operations Dashboard
• Data covers a maximum of 2 hours, or 1 million spans of operations
• Data can’t be collected from products deployed outside CP4I
• Restrictions can be lifted by purchasing License type Part Number an
add-on part Perpetual D25XKLL
Subscription D27ZXLL
Cloud Pak for Integration Operations Dashboard Add-on:
Monthly D25XILL
8 © 2021 IBM Corporation
Licensing Guidance for Operations Dashboard Add-on Part (1)
 If all features in CP4I will benefit from Operations Dashboard function, then the same number of
VPCs of the Operations Dashboard add-on part should be purchased
– If the customer has 200 VPCs of CP4I, and is using different capabilities (i.e. MQ, ACE, APIC) and is
using the Operations Dashboard with all of them, then the customer should buy 200 VPCs of
Operations Dashboard add-on part to use OD unrestricted with all of them
 If only wanting to use Operations Dashboard unrestricted with one capability of CP4I, as part of
a larger CP4I deployment, then the customer can buy only the Operations Dashboard add-on
part to reflect the proportion of the capacity being used by the capability
– If the customer has 200 VPCs of CP4I, with 50 VPCs of this entitlement used by API Connect and
Operations Dashboard is only used with API Connect then only 50 VPCs of Operations Dashboard
add-on part need to be purchased
 Deployment of Operations Dashboard components is free with CP4I entitlement. It is just the
change to unrestricted operation that is chargeable
– Adding the OD Agents as ‘side cars’ to components like App Connect will not increase the chargeable
size of the App Connect container but these side cars will increase the OpenShift used
– No additional OpenShift entitlement is needed if Operations Dashboard runs unrestricted © 2021 IBM Corporation 9
CP4I add-on: Confluent Platform for IBM Cloud Pak for
Integration (https://ibm.biz/sellconfluent )
 Confluent Platform is an add-on to CP4I, therefore Examples of Confluent Parts – see latest announcement for more
customer MUST have entitlement to CP4I when Part No. Part Metric List Price
these parts are sold (12 month - CTL)

Application

Lead with
D04C9ZX Confluent Platform Node with KStreams $13,000
Instance
 Confluent Platform add-on is available ONLY as
Application
Subscription (formerly CTL), with a minimum 12 D04CBZX Confluent Platform Node with KStreams non-prod
Instance
$6,500

month term
Application
D04C5ZX Confluent Platform Node $10,000
 A deployment is licensed by the number of

Fallback
Instance

component instances deployed (not VPC), and D04C7ZX Confluent Platform Node non-prod
Application
Instance
$5,000
the number of connector types used (sold in packs
of 5).
 How to price a Confluent Platform Deployment Part No. Part Metric List Price
(12 month - CTL)

1) Determine the numbers of nodes required

D04CDZX Confluent Platform connector pack (5) Application $25,000
2) Determine how many types of systems the client
D04CFZX Confluent Platform connector pack (5) non-prod
wants to connect to Application $12,500

Buying Confluent Platform as an add-on to CP4I does not provide any entitlement to OpenShift, and Confluent can’t be
deployed on the CP4I OpenShift restricted entitlement
© 2021 IBM Corporation 12
 Production Ratios

License Ratios for CP4I Capability Product VPC to

CP4I License
Ratio
App Connect Enterprise 1:3
 Customers buy CP4I VPCs which work like entitlement tokens
API Connect 1:1
– They ‘spend’ those VPCs when they deploy the capabilities according to the ratios
DataPower 1:1
on the right 
– e.g., 6 VPCs CP4I allow you to deploy 2 VPCs (cores) of App Connect for MQ base 4:1
production MQ Advanced 2:1
– Non-production ratios are half the production ratios Event Endpoint Mgmt 1:1
– e.g., 6 VPCs CP4I allow you to deploy 4 VPCs (cores) of App Connect for non- Aspera HSTS 1Gbps 1:4
production
 Customers have full license flexibility once they have entitlements to CP4I
– No need to tell IBM they are changing how they use their CP4I entitlements Non-Production Ratios
between the different capabilities Capability Product VPC to
CP4I License
– If they don’t exceed total capacity concurrently, they can mix, match and change Ratio
as much as they like
App Connect Enterprise 2:3
 Standalone deployment or inside CP4I API Connect 2: 1
– Customers can continue to deploy the product capabilities as separate products DataPower 2:1
outside CP4I using the same ratios if not ready to use containers MQ base 8:1
 RPA and Process Mining are also included in product ratio tables MQ Advanced 4:1
Event Endpoint Mgmt 2:1
– Mostly customers for these components will buy them as part of Cloud Pak for
Business Automation Aspera HSTS 1Gbps 1:2
13

© 2021 IBM Corporation

 Production Ratios

License Ratios for CP4I and Trade-ups Capability Product VPC to

CP4I License
Ratio
 CP4I VPCs entitlement from trade-ups works the same as App Connect Enterprise 1:3
entitlement from buying new CP4I VPCs API Connect 1:1
– A customer has 1400 PVUs of App Connect Enterprise, and 2100 DataPower 1:1
MQ base 4:1
PVUs of MQ Advanced
– 1400 PVUs ACE divided by 70 (PVU to VPC ratio) times 3 (license MQ Advanced 2:1
Event Endpoint Mgmt 1:1
ratio) = 60 CP4I VPCs
– 2100 PVUs of MQ Advanced divided by 70 (PVU ratio) divided by 2 Aspera HSTS 1Gbps 1:4
(license ratio) = 15 CP4I VPCs
– 75 CP4I VPCs total
Non-Production Ratios
 The customer can then use those 75 VPCs of CP4I on any of the Capability Product VPC to
CP4I License
products and change at any time. Ratio
– Must continue to apply the license ratio App Connect Enterprise 2:3
– Can deploy as containers within CP4I or standalone outside CP4I API Connect 2: 1
DataPower 2:1
either as containers or in VMs
MQ base 8:1
– VPC entitlement will be tracked using ILMT if deployed in VMs (on
MQ Advanced 4:1
premises or in cloud) Event Endpoint Mgmt 2:1
– Container deployments will be tracked using License Service
Aspera HSTS 1Gbps 1:2
– Deployment at non-production ratios can lead to a trade-up being
financially beneficial as prior licenses were all ‘production’ © 2021 IBM Corporation 14
Aspera High Speed Transfer Server ratios
 Since the 2020.2.1 release, IBM has updated the ratios and usage terms for Aspera High
Speed Transfer Server
 Aspera delivers file and data at high speed using available bandwidth
– The new ratios and terms specify the bandwidth available for the entitlement
 When deploying Aspera HSTS in a container in CP4I, additional entitlement enables the use
of a higher bandwidth entitlement
– For a production deployment 4 VPCs of CP4I entitles the use of 1 Gigabit per second
– For non-production deployments 2 VPCs of CP4I entitles the use of 1 Gigabit per second etc.
– The Aspera HSTS must be deployed in a container deployed in the OpenShift environment supporting
CP4I
• The customer must have sufficient OpenShift entitlement for the Aspera HSTS container deployment

 For deployments of Aspera HSTS outside CP4I containers, the ratio remains the same, fixed
at 1 Gigabit per second
– 4 VPCs of CP4I entitle deployment of Aspera HSTS ‘standalone’ at a bandwidth speed of 1 Gigabit per
second for production use
– 2 VPCs of CP4I are for 1 Gigabit per second for non-production use
 Customers can buy Aspera Enterprise 10Gbps as an add-on to CP4I © 2021 IBM Corporation 15
Event Endpoint Management deployment and pricing options
 Event Endpoint Management uses the AsyncAPI protocol to access Kafka stream histories
using API calls
 Initially available as part of API Connect in CP4I only, it is now separately deployable and with
a separate ratio in CP4I (1:1 for prod use)
 From 2021.4.1 release customers can either buy CP4I VPCs and use the ratio, or can buy
the API Calls add-on with each AsyncAPI call counted as an API Call using the same metric

CP4I VPCs Event

Endpoint AsyncAPI
Purchase options Mgmt

API Calls add- Kafka deployment

Function (Event Streams or other
on
Kafka) © 2021 IBM Corporation 16
CP4I API Calls add-on – How does the model works
Buying CP4I VPCs and deploying API Connect can be expensive
for small deployments or very large deployments Monthly

Customers might not feel that there is a relationship between the Min Units Max Units
Tier (per 100k) (per 100k)
cost and the value
1 50 500
• Buying the API Calls part allows the customer to buy a measure
2 501 1,500
of workload 3 1,501 3,000
• Customer buys at any level of API Calls across the model
4 3,001 5,000
• Customer buys an amount of calls that can be used across 5 5,001 12,000
multiple deployments (prod and non-prod) and across hybrid / 6 12,001 50,000
multi—cloud deployments 7 50,001 100,000
• The more API Calls purchased, the less expensive they are per 8 100,001 175,000
call. 9 175,001 275,000
10 275,001 -
Sold on a subscription model in units of 100k API Calls. Minimum of https://supportcontent.ibm.com/support/pages/table-vue-033
50 units per month, 5M API Calls per month, with a term of 12
months or greater.
• The number of calls is per month, not variable averaged across
the year
17
© 2021 IBM Corporation
Cloud Pak for Integration API Calls Add-on part Overview
Parts are under CP4I PID 5737-I89
• Aligns to our lead with GTM motion of leading with the Cloud Pak for Integration

Subscription (formerly CTL). Monthly

• Aligns to our shift to Subscription as preferred sales model

Price Metric: RVU (100,000 Monthly API Calls per Resource) – Graduated pricing
• Aligns to market relevant metric, removes friction from PVU/VPC and removes fear of growth

Eligibility: ELA = yes; IULA = no; ESA/ASL = by manual process.

• Consistency with other Subscription parts

Includes entitlement to OpenShift: Scales with volume of API Calls.

• Consistency with Cloud Pak for Integration. Deploy on OpenShift without separate entitlement.
• In some cases, additional OpenShift cores would require separate purchase from Red Hat or can use CP4I OCP
entitlements.
Deployment options: Consistent with Cloud Pak for Integration
• Aligned with Cloud Pak strategy supporting OpenShift and other environments where API Connect runs
18
© 2021 IBM Corporation
Red Hat OpenShift entitlement in CP4I – 3:1 ratio
 How does a customer get OpenShift
– CP4I entitlement created in IBM entitlement systems drives an update across to Red Hat who then update
their entitlement systems – RH will email the RH account owner at the customer with details
 Who supports OpenShift if provided through CP4I entitlement?
– PMRs on OpenShift are handled initially by IBM who work with Red Hat if needed
 How much OpenShift does CP4I entitlement provide
– CP4I provides 3:1 ratio entitlement for OpenShift cores (and RHEL) for each CP4I VPC entitlement
– Entitlement in Red Hat provisioning system should show up as restricted entitlement from CP4I, and only
CP4I components can be deployed on these OpenShift cores under this restricted entitlement
– All chargeable components plus Common Services and other free components like Asset Repo must have
entitled OpenShift cores to deploy on – they must be included when sizing the deployment
– Some CP4I add-ons include their own OCP entitlement – this is the same CP4I restricted entitlement and
can be used in a deployment along with CP4I OpenShift entitlement
 Additional OpenShift entitlement needed
– In certain deployment scenarios with many different small clusters or large MQ deployments, or large non-
prod deployments, there might be a need for additional OpenShift entitlement
– Customers can get additional OpenShift entitlement either from buying additional Cloud Pak for Integration
entitlement or directly from Red Hat. © 2021 IBM Corporation 19
Deploying CP4I on OpenShift – Storage Options
 Traditionally the choice of storage has been up to the customer
– Choices have been between local native file storage, or SAN, or NAS
– Products have typically either been neutral to these storage options or have developed to support or
exploit the different types.
 Container deployments are at a different lifecycle in storage options
– ‘Cloud-native’ storage that supports container deployments is typically required
– Fewer options in market today that support this storage model “software-defined storage’
 Customers deploying into containers are no longer able to make storage decisions separate
from the deployment choice
 Customers need to be made aware of this storage requirement and include budget to pay for
their chosen storage option. See limited entitlement to Storage Suite (next chart)
 Storage choices currently are available from Red Hat, IBM and Portworx
– See the File Systems and Storage section of this link
– https://www.ibm.com/docs/en/cloud-paks/cp-integration/2021.3?topic=requirements-storage

© 2021 IBM Corporation 20

Limited entitlement to IBM Storage Suite
for IBM Cloud Paks
IBM Storage Suite for IBM Cloud Paks

 IBM Storage Suite for IBM Cloud Paks offers a range of software-defined storage options ideal for use in
Kubernetes deployments

 Cloud Pak for Integration now includes limited entitlement to Storage Suite for Cloud Paks
 Entitlement is limited to 12TB for Red Hat OpenShift Data Foundation Advanced, and 12 TB in total for the
other included storage options (Spectrum Scale, Spectrum Discover, Spectrum Virtualize for Public Cloud)
 Entitlement to 4TB of Spectrum Protect Plus is included in the 2021.2.1 release onwards
 Entitlement ends after 36 months (36 months after first purchase of CP4I)
 Only one entitlement per customer – additional purchases of CP4I do not provide additional entitlement
 Does not include entitlement to IBM Cloud Object Storage or Red Hat Ceph Storage
 IBM handles Level 1 and Level 2 support for all storage included
 Additional entitlement to IBM Storage Suite for IBM Cloud Paks can be purchased to add capacity or to use
beyond 36 months
 Red Hat OpenShift Data Foundation Advanced would be deployed in infrastructure nodes (no need for separate
OpenShift entitlement)
IBM Integration / © 2020 IBM Corporation
© 2021 IBM Corporation
Consuming CP4I and OpenShift entitlements
Consumes CP4I entitlement (uses ratios – Doesn’t consume CP4I entitlement
prod and non-prod)

Consumes MQ Queue Managers Cloud Pak Common Services (bedrock)

OpenShift App Connect Server CP4I Asset Repo, Platform Navigator,
entitlement Aspera HSTS Operations Dashboard
API Connect Optional
DataPower Virtual Server App Connect components (Designer build-
HA deployments of above capabilities time, Dashboard, connectors)
MQ components (MFT Agent, IPT, Explorer)

Doesn’t Deployments of integration components Init containers

consume outside of CP4I OpenShift as Standalone Master nodes, Controller nodes and
OpenShift deployments Infrastructure nodes (that only run OpenShift
entitlement functions)
‘cold’ DR deployments

© 2021 IBM Corporation 22

 Examples are for illustration
only and should not be used
OpenShift entitlement and deployment example as actual suggested
deployment examples
Customer buys 50 VPC of CP4I for MQ, ACE, API Connect, Asset Repo, Prod cluster 1
Operations Dashboard - Gets entitlement to 150 VPC of OpenShift
50 VPCs of CP4I allocated as follows
API Connect MQ Adv 2
2 prod clusters, 1 non-prod cluster 12 VPC / 12
App Connect 6
VPC / 4
VPC / 2 cores Foundation
Prod cluster 1 cores cores
Services 13
12 cores API Connect prod (12 VPC CP4I) Operations cores
Platform
2 VPC ACE prod (6 VPC CP4I) Dashboard Nav 0.25
4 VPC MQ Adv prod (2 VPC CP4I) 7 cores cores
Prod cluster 2
12 VPCs API Connect prod (12 VPC CP4I) Prod cluster 2
2 VPC ACE prod (6 VPC CP4I)
4 VPC MQ Adv prod (2 VPC CP4I) API Connect
App Connect 6
MQ Adv 2
12 VPC / 12 VPC / 4
Non-prod cluster VPC / 2 cores
Foundation
cores cores
12 VPCs API Connect non-prod (6 VPC CP4I) Services 13
2 VPC ACE non-prod (3 VPC CP4I) Operations Platform cores
Dashboard Nav 0.25
4 VPC MQ Adv non-prod (1 VPC CP4I) 7 cores cores
54 cores of chargeable components deployed with 50 VPCs of CP4I
Non-prod cluster
Non-chargeable components deployed on OpenShift cores
13 cores of Foundation Services in each cluster (39 cores total)
MQ Adv 1
7 cores for Operations Dashboard in each cluster (21 cores total) API Connect 6 App Connect 3
VPC / 4
VPC / 12 cores VPC / 2 cores
0.7 cores for Asset Repo in non-prod cluster (0.7 cores total) cores Foundation
Services
0.25 cores for Platform Navigator in each cluster (0.75 cores total) Platform 13 cores
Operations Asset
Total additional deployed OpenShift 61.5 cores Dashboard Repo 0.7 Nav 0.25
7 cores cores cores
OpenShift cores used: 115.5 cores
Recommended OpenShift deployment buffer 10-15%: 12-18 cores
© 2021 IBM Corporation 23
The 150 OpenShift cores entitlement would be sufficient
Sizing Deployments of CP4I – Important Reminders
 CP4I VPCs are used according to the license ratios to deploy any/all of the chargable
integration capabilities as desired (but only measured when deployed)
– Deploy in CP4I containers or standalone
– Subject to the same capacity restrictions – max deployment at any time equal to the number of VPCs of
CP4I.
• Number of CP4I VPCs must always be converted using the license ratio based on the number of product cores of
integration capabilities.

 Not all integration capabilities must be installed or deployed – can be any 1 or any mix.
– Valid examples include each individual product but might also include options such as:
1. API Connect and App Connect
2. MQ, DataPower and App Connect
3. MQ
4. MQ, App Connect, API Connect
 Note that both MQ and MQ Advanced are possible to deploy with CP4I entitlement
– Either standalone or as part of CP4I deployment
– Since the 2020.4.1 release, customers deploying MQ base in CP4I can deploy MQ Advanced containers
and ensure that the correct license tracking is performed to only report MQ base use.
© 2021 IBM Corporation 24
License Counting and License Service
 ILMT and VPCs – Customers migrating to CP4I entitlement move to VPC entitlement
– ILMT must be used for customers deploying VPC entitled products if deploying in VMs (i.e. not in containers)
 Deploying in containers
– License Service reports on core count of containers where any of CP4I components deployed
– Produces deployment report for customers to report sub-capacity container deployments
– Customers must sign new PPA amendment for container licensing
– Review Slack channel #container-licensing-faq
– External container licensing FAQ
– Option to push License Service reports to ‘IBM Software Central’ – subject to customer agreement
 Availability of the License Service
– License Service can run on any Kubernetes environment to provide metering and reporting, not just
OpenShift
– It only can be used to count and report on deployments of Containers and licensed using VPC metrics. It can
measure container deployments running outside of OpenShift as well
 Container Licensing or ILMT
– Deploying containers in Kubernetes means you must license either with the License Service or license the
full-capacity of the deployed systems – no use of ILMT for containers with sub-capacity is supported
© 2021 IBM Corporation 25
Small and Minimum sizes for CP4I Deployment
 Documentation and this guide give minimum sizes for deployments – what happens if a
customer deploys in smaller deployments?
– The minimum sizes given are minimum recommendations
– It will be possible to deploy and run smaller containers, but behaviours may not be optimal
 Licensing for small deployments
– Buying license entitlement is only supported in whole VPCs
• CP4I VPCs not related to processor core VPCs – CP4I VPCs are tokens using the ratios to convert to component VPCs
– Customers must not exceed their CP4I entitlements as they deploy any of the capabilities in total
– If a customer is only planning to deploy a single VPC (core) of MQ, then they must have at least 1 VPC of
CP4I
• They can’t buy a fraction of a CP4I core – the minimum they can buy is 1 VPC of CP4I – which gives them 2 VPCs of MQ
Advanced or 4 VPCs of MQ base – or even 8 VPCs of MQ base (non-prod) – they have to buy at least 1 CP4I VPC, even
if they just want 1 core of MQ base non-prod
– License aggregation to whole numbers takes place per cluster (per product)
• Components aggregate separately, i.e. MQ base prod will aggregate, then MQ base non-prod etc. within the cluster for a
single whole number count of CP4I VPCs for the cluster once all components have aggregated
– If deploying using CP4I VPCs but not in containers, then aggregation is per local site (PPA site)
• For example, if deploying 2 cores of MQ standalone that is 0.5 of CP4I VPC. Another deployment of 2 cores of MQ
standalone on the same customer site would then be added to a total of 1 VPC. If only CP4I deployment total on that site
was 0.5 VPC, the count for that site would be rounded up to 1 VPC
© 2021 IBM Corporation 26
Considerations for Sizing CP4I deployments
 Frequent Sales request for
Small/Medium/Large deployments
– Likely to mean different things to different
products
 Small=getting started for production only
– Initial deployment – likely lowest
recommended deployment for a production
environment
– Unlikely to handle larger workloads
– Unlikely to offer recommended approaches
for HA/DR
– Won’t include development/test
environments
 Medium =production and more
– Includes production environment to handle
lower end of workloads
– Includes HA/DR environments
– Includes development/test environments
 Large =high volume production and
more
– Includes production environment to handle
medium to upper end of workloads
– Includes HA/DR environments
– Includes development/test environments

• Note that actual customer deployment requirements will differ depending on workload or
deployment needs
• Please consult the sizing guide on Seismic and your local tech specialist
© 2021 IBM Corporation 27
Minimum deployment sizes for each chargeable product in CP4I
(except RPA/Process Mining) per Documentation
Aspera HSTS
API Connect App Connect 1Gbps

Cores VPC of CP4I Cores VPC of CP4I Cores* VPC of CP4I

7 7 (prod) 1 3 (prod) 4 4 (prod)
7 4 (non-prod) 1 2 (non-prod) 4 2 (non-prod)
Aspera ratio for CP4I VPCs not
related to deployed cores – VPC
count determines bandwidth use

DataPower MQ Advanced Event Streams

Cores VPC of CP4I Cores VPC of CP4I Cores VPC of CP4I
1 1 (prod) 1 1 (prod) 2.4 3 (prod)
1 1 (non-prod) 1 1 (non-prod) 2.4 2 (non-prod)

Use this link to access the documentation with the most recent deployment minimum needs
https://www.ibm.com/docs/en/cloud-paks/cp-integration/2021.3?topic=requirements-co
mpute-resources-development-environments

CP4I VPCs gives you 2x entitlement for non-prod deployments in all products © 2021 IBM Corporation 28
Minimum deployment sizes for each non-chargeable component in CP4I
(per Knowledge Center)

Operations Platform Nav

Asset Repo
Dashboard

Cores Cores Cores

7 0.7 1.7
Foundation Services

Cores Operations
App Connect
Dashboard
7.2 Designer
Agent

Figures for Foundation Cores Cores

Services will be increased if
deployed in HA 0.5 1
configurations. License
Service not included in the Operations Dashboard Agents will App Connect flows created in Designer deploy
above number. be deployed as non-chargeable additional chargeable containers with the Designer
container in the Program pod flow alongside App Connect container in pod (these
increase App Connect charging)
Use this link to access the documentation with the most recent deployment minimum needs
https://www.ibm.com/docs/en/cloud-paks/cp-integration/2021.3?topic=requirements-co
mpute-resources-development-environments
© 2021 IBM Corporation 29