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.
I see this as a critical requirement for a couple of IBM / ACE customers.
Further there should be no difference if we run the integration server in a "independent" or within a note.
Thus it would be great if this could be implemented soon.
RFE Review. Since ACEv11.0.0.7 we now allow the specification of a remote default queue manager in the server.conf.yaml file to be used to support the persistence requirements of the EDA nodes when deployed in an independent integration server running in containers. We have not yet prioritized the testing required to support this same architectural approach for node-owned servers, so for this reason we will maintain the status of this RFE as Uncommitted Candidate for now, whilst noting that if running in containers the capability (iii) is already delivered.
Thank you for raising this RFE. IIB still retains a need for a local MQ queue manager for some of our processing. Specifically:
i) In order to provide two-phase XA coordination of transactions ,the coordinating queue manager must be local
ii) For Multi-instance HA support
iii) For the Event Driven Architecture nodes (Aggregation, Collector, Tinmeout, Sequencing)
iv) To underpin the communications between individual integration servers and the node-wide HTTP listener.
Whilst long term one could imagine architectural changes which remove all 4 of these uses, changes in (iii) and (iv) are likely to be a nearer term focus for the product.
To help keep RFEs specific, we will use this RFE to track item (iii) for the EDA nodes as this appears to be the primary use case discussed.
Status of the RFE is updated to Uncommitted Candidate.