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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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 raising this — and for pointing to APAR IT47069 as context. The need to exclude specific domains from proxy routing is a well-understood pattern in Linux environments via
NO_PROXY, and we agree it is a reasonable capability gap to address in ACE.We are marking this as accepted for future consideration.
It would be great that this setting could be enabled via server.conf.yaml or specific configuration on CP4I. This to be able to perform those changes without touch the flows or nodes
Has this had any up take? I am currently attempting to configure OTEL in IBM ACE, which requires proxy to NewRelic from within the corporate network, but setting HTTP_PROXY environment variable so that it is used by OTEL is now causing previously working processes to fail cause they are being directed to the proxy, and there is no way of explicitly configurating HTTP and SOAP request nodes to not use a proxy.