Integration
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:
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 ideasibm@us.ibm.com for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
Additional, prevent the need to restart the IntNode after an IntServer is added and security is used.
RFE Review. Thank you for taking the time to raise this RFE and apologies it has been in submitted status for a while. The behaviour described is a consequence of the new capabilities provided by independent integration servers which are an architecturally new construct provided with ACEv11 in order to make the product genuinely container native in its approach. This has cause it to be desirable to push some product configurations down to integration server level of the hierarchy. Potentially the product could in future be enhanced to provide utility commands making a desired "inheritance" relationship expressable ... but unfortunately this is unlikely to be an urgent priority given that the declarative style of server.conf.yaml files mean that it is relatively easy to work within the product's current constraints (using copy/paste / scripting etc) rapidly even with estates with large numbers of servers. Status of the RFE is updated to Uncommitted Candidate.