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.
Idea Review. Thank you for taking the time to raise this enhancement request, although on this occasion we do not intend to take this suggestion forward. We explain the reason for this decision, and also as a reference point for other readers passing through, in the response below ...
ACEv12 UDPs can be defined on a message flow, and then accessed at runtime (for example within an ESQL compute node). It is possible to use the WebUI (or use the public admin REST API on which the Web UI is based) to update an existing UDP value. If you do this, then the message flow does not need to be redeployed or updated but the next invocation of the flow will find the flow access the new value. If you then restart an integration server, by default the value of the UDP will be returned to its initial value. This behaviour is deliberate. If users would prefer for a dynamic override to remain in force after a restart this behaviour is also possible by editting the server.conf.yaml using the following property:
UserVariables:udp-persist-global-overrides: trueThe idea mentions the importance of enabling the override of the value using the WebUI without needing to redeploy the bar files ... this much is already available in ACE as mentioned above ... However there is a subtlety in the further wording of the idea which mentions the specific circumstance of a UDP which has also been promoted and renamed. The promotion of a UDP from a subflow to a parent flow, is a technique used in older forms of the product (eg IIBv10 is mentioned) to utilize a single UDP value across more than one subflow. The new style ACE Global UDPs are available to separate subflows without needing to go through promotion. Sooo ... to achieve the use case we recommend changing the subflows to use a new global UDP (which can be altered in the Web UI and persisted across restarts) as opposed to continuing with the somewhat cumbersome approach of property promotion.