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
Simplified Disaster Recovery procedure for API Connect on CP4I on Openshift
Since 2019, we have been running API Connect on CP4I on Openshift on Azure Cloud. The disaster recovery procedure for recovering particularly (of importance to us) the Management server and Developer Portal (see below) for API Connect is very exhaustive comprising of several steps. In comparison the disaster recovery procedure for API Connect v5.0 running on Vmware as an Appliance was must straightforward and simpler. This makes it difficult for us to substantiate to the business as to why we are running API Connect on containers on the Cloud if we cant do things we already did when we had API Connect on Vmware in the Datacenter. Is it possible to therefore simplify the procedure by trying to incorporate the steps outlined into a script or even better make it part of the API Connect Operator Catalog?
Do not place IBM confidential, company confidential, or personal information into any field.