This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
As of today as per the latest documentation available, CP4I is partially supported on Power systems. Refer: https://www.ibm.com/docs/en/cloud-paks/cp-integration/2022.4?topic=requirements-operating-environment. So namely there is no support for Aspera and APIConnect on Power systems. However this is an issue for customers who are on older versions of our integration platform like WebSphere Service Bus or IIB on Power but would want to migrate to the newer version of CP4I. I have a customer as of today who wants to migrate but the issue is that CP4I does not support API Connect which is a business requirement for them and the customer is having all their systems on Power 7 & Power 9. This could be the issue with many such Power customers who need integration platform as part of their enterprise business. So if we have the full compatibility of CP4I on Power systems inclusive of APIConnect, Aspera etc as it is with x86, then our CP4I migration story will be much simpler and efficient.
Do not place IBM confidential, company confidential, or personal information into any field.