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.
Unfortunately there has not been further interest noted since our last update in October 2020. Whilst the web services angle to the framing of this use case does not help us prioritise right now, we note that the heart of this issue is really to do with the Toolkit programming model's approach whereby each node in the flow is responsible for the structure of the message assembly which is emitted to the next node in the flow. This gives tremendous power, but can also make things tricky for new users to remember it is their responsibility to decide which parts of the tree should be preserved as you move from one node to the next. This important design point was differently addressed in the Designer programming model, where the output context trees from each node in the flow are treated as immuteable. As the Toolkit and Designer programming models come closer together in future, we may end up supporting an option of having immuteable trees (or an area of the tree which is immuteable) in Toolkit flows, but this won't be sponsored through a web service specific RFE, so on this occasion we will not be carrying this idea forward.
RFE Review. This area remains of interest to us, and despite not being an immediate business priority, it is an idea we will continue to monitor for popularity. Status updated to Uncommitted Candidate.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Connectivity and Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
Good requirement thanks for raising. Service composition style use cases are very important for IIB, and we're looking at a number of improvements that will simplify how the product allows you visualise and manage the data (and other service information) as it flows from endpoint to endpoint. Cheers.