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).
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:
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 updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
the idea of stopping the whole container will not work for us as we will have several ace apps deployed on to same IR and we would like to stop and start specific app even if they are running on multiple replicas and we don't mind even if we have to manually go and stop/start these apps on each replicas.
Idea Review. Thank you for taking the time to raise this enhancement request. Unfortunately on this occasion we do not intend to take this idea further forward. When moving ACE to containers we deliberately chose an abstraction model where we don't show differences or provide separate configuration between the integration server replicas that are running within the platform. It is for this reason that we deliberately do not offer operations which would need to be separately and statefully applied to each of the replicas. The standard model we would like our users to follow here is for the container to be stopped and then started again. There is a manual workaround whereby a user could directly send specific K8S administration requests in to one of the currently running replicas but this is not something we would wish to encourage by offering an option to do this directly in the dashboard UI.
Hi Chetan,
Thanks for coming back on this - we're going to move it to the App Connect Ideas so that they can review appropriately. You'll notice I've changed the status from 'under review' to 'submitted' - that's so it will show up in the correct place in their reviews.
Hi,
Thanks for the reply and editing replicas to 0 in dashboard is a reasonable option as an alternate to stop/start application directly as we do in ACE GUI but the downside is it would stop all the apps in that IR where in we wanted a specific app to be in stopped state.
Its not a major issue of course we can keep such apps in separate IR's and handle but again we should consider about license usage and all to have individual app in IR's.
We have use cases like we want a specific app to be stopped for specific amount of time because of many reasons like we don't want to read the MQ messages at that time or we should wait for some other process to be completed first before we process new messages etc...
This is a nice to have feature if it takes lot of effort to fix that's fine we can look at the alternative.
/Chetan
Thanks for raising this - we don't currently have the ability to stop a flow, but we do have the capability of dropping the server/runtime replica count to 0 so that the ACE flows stop processsing. You can do this from the dashboard with the 'edit' button to edit the ACE CR for that server/runtime.
Have you looked a this option - are there use cases you have that this would not work for? Please let us know.
(Tile on one of our servers showing zero replicas below)