Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.


Status Future consideration
Workspace DataPower Gateway
Created by Guest
Created on Feb 18, 2023

Add HTTP status code criteria to matching rule.

Often, there are tasks when we need to apply different response rules in MPGW based on HTTP status code.
For example:
1) When HTTP Response code = 200, the backend server returns JSON and it must be validated according to the json scheme.
2) When HTTP Response code = 204, there is no response body and no need to perform validation.

There is no possibility to create a matching rule for HTTP status code now. Such a refinement will greatly simplify the creation of MPGW rules.

Idea priority Urgent
1 MERGED

Matching rules should support a match against the response code

Merged
The Matching rules are a key functionality for process rule handling. As DataPower is nowadays widely used for non-SOAP/non-XML traffic as well, the match mechanism should support matches against the HTTP response code.
4 months ago in DataPower Gateway 0 Future consideration