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.
See this idea on ideas.ibm.com
Integration Applications are developed with the ACE toolkit, packaged as bar files and then deployed as Integration Server (IS) on the ACEonCloud (ACEoC) service. The IS can contain multiple message flows but the ACEoC service does not provide an interface to stop/start a single flow within the IS. So, we need an enhancement in the ACEoC service to get such an interface (the interface could be in the GUI, or some REST API or CLI).
Idea priority | High |
RFE ID | 147059 |
RFE URL | |
RFE Product | IBM App Connect Enterprise (formerly IBM Integration Bus) |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Thank you for taking the time to raise this RFE. This enhancement would represent quite a big architectural change to the way the service works - currently there is no need for individual deployed flow states to be stored outside of a running container, or kept in-sync between multiple container replicas. Given this implementation cost, it is unlikely that this enhancement will be urgently prioritized, but as ever we are keen to explore the use case further to better understand its importance to our users ... We will continue to monitor the RFE for support and comments, and in particular we are keen to understand whether it would be sufficient to have the start/stop state of the application changeable and in a non-persisted fashion (ie if the container were to restart for any reason, then the state of the application would return to the setting in the BAR file). Status of the RFE is updated to Uncommitted Candidate.