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 request has been held in the status of Uncommitted Candidate / Future Consideration. Since initially raised, it has been our long-term strategy to simplify and improve the portability of integration nodes and to be able to more easily configure integration nodes to have particular names, queue manager relationships and to clone them between systems. The mqsiextractcomponents command provides the "target-integration-node" parameter which can be used to provide a new integration node name when moving a node from an old version to the latest version of the product, or when porting the node from one platform to another. The relationship of the product with MQ has also evolved over the years - the defaultQueueManager with which a node is associated can be controlled in the node.conf.yaml file, and MQEndpoint policies can also be used to define the location of remote queue managers which can be accessed via client bindings. Given these evolutions (and similar comments recently made upon https://integration-development.ideas.ibm.com/ideas/APPC-I-83), we are updating the status of the idea to closed.
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