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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive a notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
If you encounter any issues accessing the Ideas portal, please send email describing the issue to firstname.lastname@example.org for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
Data replication between 2 Analytics Subsystem clusters
In APIC V5 we have ACTIVE-ACTIVE setup for our DataPower(DP) servers (2 DP each DC, 4 in total) and 2 Management Servers (1 each DC) so in case 1, if whole DC goes down we are still able to record all the API events using other DC. All DataPower servers are in one cluster (DP Service) which allows to enforce Rate Limit.
Analytics data (API events) are widely used in Nordea for many business and operations reasons - multiple dashboards have been created in API Manager where API Providers are able to check different things - e.g. basic thing like total number of calls for specific API.
We've noticed few issues already when we started looking for migration to APIC V10, according to various IBM documentation and IBM meetings:
- one DataPower cluster enforces one Analytics Cluster associated.
- we can't span Analytics Cluster across 2 DC the same way that we can do for DataPower.
- If we have 2 Analytics Clusters then we can't ensure data synchronization between those then the data will be fragmentized on both sides.
Current API Connect V10 possibilities doesn't allow us to secure the same level of analytics data availability and accessibility as it was in V5:
- having 1 analytics cluster in single DC causes data loss if this particular DC goes down
- having 2 analytics cluster implies data fragmentation between those
Hence, it was concluded with IBM architect and engineers that we should request for ACTIVE-PASSIVE setup and data replication across clusters.
Such mechanism is already available for Management and Developer Portal subsystems documented here:
Do not place IBM confidential, company confidential, or personal information into any field.