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.
See this idea on ideas.ibm.com
Add the SPLPROT functionality to distributed MQ platforms. We need this feature for applying AMS policy for our external partners. This is a critical functionality. This is needed to compliy with PCI 4.0 regulations.
SPLPROT (Security Policy Protection) specifies how a server-to-server Message Channel Agent should deal with message protection when AMS is active and an applicable policy exists.
Idea priority | Urgent |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
This is the functionality that needs to be added to the distributed platforms
Server-to-server message channel interception example configurations
Last Updated: 2025-01-30
Server-to-server message channel interception requires configuration of channel definitions, as well as Advanced Message Security policies, to ensure that inbound and outbound messages can be correctly protected or unprotected. The configuration varies depending on whether the channel is inbound or outbound.
Inbound channel
The following example shows a typical configuration for an inbound channel of type receiver, and provides details of the AMS policy required to protect unprotected inbound messages:Figure 1. Inbound configurationThe example shows:
Queue manager
QMA
Channel
TO.QMA
Local queue
DESTQ
Use the following code:
Note: The policy described in the preceding text encrypts messages only; that is, AMS Confidentiality.
See setmqspl and the message security policy (CSQ0UTIL) for information on using setmqspl on z/OS®.
Outbound channel
The following example shows a typical configuration for an outbound channel of type sender. The example provides details of the AMS policies required to protect messages put to the remote queue, and to unprotect and send messages got from the transmission queue:Figure 2. Outbound configurationThe example shows a:
Queue manager
QMA
Channel
TO.BP
Local transmission queue
TO.BP.XMITQ
Remote queue
REMOTE.BPQ
use the following code:
Can you please provide a status on this request. This is very critical.
We need to have the SPLPROT functionality to distributed MQ platforms. If the distributed platform has AMS installed, we would like the SPLPROT functionality applied on the receiver channel. We would have a policy on the local queue. We need the messages encrypted when they are placed on the queue. We would also need this on the cluster receiver channels.
ASPOLICY: (Receiver, Requester) The MCA applies the security policy to the message, enforcing the protection defined by the AMS policy.