Skip to Main Content

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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace App Connect
Created by Guest
Created on Jun 11, 2012

TCPIP Node - Add Flexible Configuration Alternatives

DNS round robin
Currently message broker does not do a new DNS lookup per connection created. This type of configuration is required ideally a function directly to the node to do this in a more straight forward way (like possibly having a list of addresses to use on the configurable service)

Idea priority High
RFE ID 23349
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Aug 13, 2021

    Idea / RFE Review. Apologies for the length of time this RFE has been held in Uncommitted Candidate / Future Consideration status. Business prioritization has not yet led us to implement this requirement, and unfortunately there has also only been a single vote for this idea despite it being open since 2012. Given this, unfortunately on this occasion we will not be pursuing this suggestion further. For those who are interested in this use case, you could use Compute node ESQL/JCN/Map in a node prior to the TCPClientOutput to do the "round-robinning" and set up the LocalEnvironment tree which can be used to dynamically control the host and port used by the TCPClientOutput.

  • Guest
    Oct 7, 2015

    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

  • Guest
    Oct 24, 2012

    Thank you for the update. Is there a way to know when this investigation is complete and the enhancement might be included?

  • Guest
    Aug 28, 2012

    Thanks for raising this requirement. The TCP/IP nodes do allow you to specify multiple IP addresses that the broker will use (see the "AlternativeAddresses" TCPIPClient configurable service property), but the connection algorithm is based solely on availability: if the first address is not available then the second is used, and so on. So I think a neat extension to this support would be to specify an alternative connection algorithm on the configurable service, such as round robin like you suggest. We'll investigate adding this in a follow-on release or fixpack.