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.
It would definitely be really good to have the feature already delivered on MQ for z/OS in 9.1.3 also on distributed Linux
This function has been delivered on MQ for z/OS in 9.1.3. For more details see: https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.pro.doc/q132850_.htm#q132850___amsprot
Providing this option would allow a shop to rollout AMS across interconnected qmgrs spanning multiple platforms vs. a big bang approach.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Integration
Product - IBM MQ
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Connectivity and Integration
Product - IBM MQ
The general use case here is that of establishing a policy enforcement point at the network perimeter. i.e. "I have AMS on my local QMgr and my local MCA encrypts inbound messages and decrypts outbound messages."
Although this is valid another use case is "I have AMS on my local QMgr and my the remote MCA on my business partner's QMgr which does *not* have AMS encrypts messages on their way to me and decrypts messages it receives from me."
In the second use case we get authenticity, integrity, and privacy where less than a full AMS implementation is required. For hub-and-spoke, clearing-house type operations, this second model is essential. Examples include central banks, claims settlement, ACH, SWIFT, postal services, retail, etc.
Current AMS implementations support encryption at the qmgr end of a SVRCONN channel. Extending this to other channel-types is a reasonable requirement for a future update to AMS.