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.
Idea / RFE Review. Apologies for the length of time this idea has been in the status of Uncommitted Candidate / Future Consideration. Although initially raised before policies were introduced into the product architecture at v11, the conceptual suggestion is still relevant to ACE ... As noted, it is currently possible that a TCPClientOutput node's host and port can be replaced with the name of a policy in a policy project to dynamically specify where the TCPClientOutput node connects to, but unfortunately the LocalEnvironment overrides only allow host and port to be overridden rather than a policy name. This still sounds a valid future requirement and whilst we have not yet managed to prioritize a business case for this feature, we will maintain its status as Future Consideration for now.
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. Completely understand the need here - as you say, having to configure multiple output nodes when you are connecting dynamically to SSL-based servers is not ideal. This would be a relatively simple feature to implement, and will look to do so with the next raft of TCP/IP enhancements in a follow-on release or fixpack.