Integration
Hide about this portal
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.
An ACE REST API is deliberately designed to have one parent flow (which relates to a specific HTTP URL fragment and uses a specific integration server wide port) with an associated subflow per REST API operation defined within the Open API / Swagger document defining the REST API. Alternatively if you'd like to, you could utilize separate HTTP Input nodes within one or more message flows (which can be assigned their own separate pool of additional instances). The wording of this request suggests that within the subflow, there is a desire to use asynchronous nodes to then invoke other endpoints (from within the exposed REST API). The input portion of such an asynchronous call (eg the MQInput node after the MQOutput node) can have its own thread pool of additional instances applied, so on the face of it this use case is already achievable.