Integration
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 updates on 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
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.
RFE Review. Thank you for taking the time to raise this enhancement request. When IBM Integration Bus was rearchitected to become App Connect Enterprise (v11, released on distributed platforms in 2018), significant changes were made to the deploy chain of the product to ensure that the runtime could independently store in memory a record of the deployed artifacts (and their properties) and then separately store settings such as monitoring and statistics. This evolution was done in order to meet usecases such as the one presented where users require "sticky settings" to be persisted across restarts. The architectural changes which facilitated this on ACE were widespread in scale across the product's architecture and came in combination with the new ACE policy artifacts which replace the prior concept of configurable services and can be deployed and overridden dynamically. This background explanation is made here to reinforce that we approve of the idea of the usecase, and also understand very well the scope of engineering which would be required to fulfil this request. Unfortunately, although this might on the face of it seem like a "small request just to persist some settings", the cost to implement the wider architectural changes which would be needed to support this are not so small ... The good news of course is that these changes have been made in ACE and the feature to exploit them is also there in ACE. The bad news is that there has not been sufficient business demand emerge for ACEv11 / ACEv12 to be ported to the zOS platform. Whilst there is clear demand for certain select new functions to be made available on the zOS platform, these features have not required the rearchitecture that comes with ACE. For this reason, whilst IBM does plan a future zOS IIB release, it is not likely to satisfy the request in this RFE.
Given the above explanation, unfortunately on this occasion we are updating the status of this request to Not Under Consideration.