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.
Idea / RFE Review. Apologies for the length of time this idea has been in the status of Uncommitted Candidate / Future Consideration. At such stage that this is prioritized from the business standpoint, the likely model we would follow is to give separate ids (for each server) membership of mqbrkrs. One consideration which would need to be overcome would be to make sure that each server has access to the UDS file in order for interprocess communication (between dataflowengine.exe and bipbroker.exe) to not be interrupted by the new model. We will continue to monitor the suggestion and currently maintain the status at Future Consideration.
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
Completely agreed, and we would like to implement this on the distributed OS platforms. The engineering work required does vary from OS to OS, so to help with the prioritization, if anyone else needs this one please use this RFE to state the platform you require it, as a couple of folks have done already.
Yes, this would resolve the issue whereby any flow deployed in any execution group can access any queue, because the broker id has mqm authority.
Different execution groups should be limited to being able to access their own set of queues, based on group membership of a userid.
This is a must have for distributed Windows, Linux, Unix (verses Z/os) please prioritize !
Thanking you in advance.
Please make sure you extend the functionality from zOS to distributed.
See DaveZiegler's comment
Thanks
This is an important requirement for us as a financial institution as well, we would prefer *not* to have one all-powerful broker instance connecting to multiple databases. It would be much nicer to be able to configure db access at the server level.