Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace DataPower Gateway
Created by Guest
Created on Sep 28, 2018

WS-Proxy policy rule match based on namespaces

DataPower should be able to handle multiple WSDL (versions) potentially containing the same operations without the need of dedicated URIs for each service (version).

Unfortunately DataPower can't distinguish between two services being exposed under the same URL and always fires the first matching request rule regardless of the namespace. This is because the current implementation can only distinguish between to WSDLs within the same WS-Proxy based on IP and URI. It does not respect fragment identifiers based on target namespace and port name specified in the "Service Port Match Expression" of the "Local Rewrite Rules" of the related "WS-Proxy Endpoint Rewrite" object.

Idea priority High
RFE ID 125396
RFE Product IBM DataPower Gateways
  • Guest
    Jul 1, 2022

    I'm quite sad about the "Not under consideration" status for at least two reasons:

    1) Why are namespaces needed in the endpoint mapping when they are not used to differentiate between requests?

    2) The change wouldn't be breaking as it wouldn't change the current behaviour, as everybody already has to use dedicated URIs.

    I know that classical SOAP-based services are on the skids, but there are still a many customers using these old-fashioned web services.