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.
Thank you for taking the time to raise this enhancement request, which we agree would be a small but positive usability improvement for the product. As noted, HTTPRequest nodes have supported the concept of using a Proxy for a long time - and this property was provided directly in the message flow (or overridden in the BAR file using a deployment descriptor). More recent development has been done for the Discovery connectors, where the properties for the HTTP Proxy have been separated into a specific policy type (which is then referenced by the Discovery Connector policy). We could add a similar link from an HTTP Request policy to unify the design in this area of the product. For back compatability reasons we would not want to remove the HTTP Request node properties but we could define a precedence hierarchy to let both methods coexist in the product. When implementing we would most likely also want to apply a similar feature to the SOAPRequest, RESTRequest and Async Request node forms as well. Status of the idea is updated to Future Consideration.