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.


ADD A NEW IDEA

Pinned ideas

View all
PINNED OpenAPI schema validation including headers
Currently to schema validate a REST based API in DataPower you have to extract the JSON schema from the OpenAPI file and then code manually code the individual header checks defined in the OpenAPI file Would be a vast improvement to be able to j...
Share feedback 1
PINNED Add a "Maximum persistent reuse" parameter for the backside of an MPGW or WSP
On an MPGW or a WSP, I want to be able to configure that the persistent backside connection should be closed after X amount of requests have been sent through that connection. I can already do this for the frontside by setting the "Maximum persist...
Share feedback 1

Ideas

Showing 1414 of 3341

Efficient streaming of very large API payloads with low memory usage

DataPower API Gateway provides streaming to handle very large payloads (Giga bytes). Currently streaming only improves latency, but does not limit memory consumption. We need efficient streaming of very large API payloads using limited buffers in ...
over 3 years ago in DataPower Gateway 4 Future consideration

MRM/Message Set to DFDL Converter/Wizard

Providing a MRM/Message Set to DFDL converter/wizard will provide a useful way to migrate from using the MRM and Message Sets to using all DFDL. This will also increase adoption of DFDL.
about 10 years ago in App Connect 2 Future consideration

Evaluate force-ip-preference Parameter for ALL DNS Lookups

DNS lookups for SQL Data Source hosts and system name associated with loopback references are ignoring the force-ip-preference parameters. When IPV4 is the preferred version, there is no reason to attempt hostname resolution via AAAA DNS query (wh...
11 months ago in DataPower Gateway 0 Future consideration

MFA Implementation for App Connect Professional Web Management Console

There is no current way to implement MFA access to the Web Management Console (we rely on username/password combinations). We are undergoing a security assessment and per IA-2(1) for privileged access and IA-2(2) for non-privileged users (see belo...
almost 2 years ago in App Connect 1 Not under consideration

IBM ILMT - In case of moving the VM, the PVU shows unexpected value due to ServiceNow computer_system_id filtering.

Problem:In case of moving the VM in between the ESX server, the PVU shows unexpected value on license_usage API and is causing ILMT integration with ServiceNow to be failing Using sample case: Machine: VM1 It's shown up on license_usage.txt/ licen...
almost 2 years ago in IBM License Metric Tool (ILMT) 1 Not under consideration

Throw exception from CDOutput node upon Connect Direct transfer failure

Having issue with CDOuput node where a target system is down or even when a hostname is incorrect in the netmap we are not getting the failure in ACE. We can see from the Connect Direct logs that it failed but ACE processes as if it was successful.
11 months ago in App Connect 1 Not under consideration

Azure Storage connector with SAS Token

Today, to access/put data to Azure Blob and File Storage, you must define a connection that specifies the storage account name and access key. But there is no possibility to configure a SAS Token in Azure connector.However, the use of SAS Token is...
11 months ago in webMethods Connectors and Adapters 0 Under review

Add MQ 9.4 support to the WebSphere MQ Adapter

As per pages 57 of "webMethods Adapters System Requirements" (https://docs.webmethods.io/on-premises/webmethods-adapters/11.1.0/pdf/webMethods_Adapters_System_Requirements.pdf), the WebSphere MQ Adapter 6.5 for webMethods Integration supports IBM ...
11 months ago in webMethods Connectors and Adapters 0 Planned for future release

Enable Parser / Validation Exceptions to populate SQLSTATE / SQLCODE for use in ESQL Handlers

ESQL exception handlers can filter on and access special registers SQLState, SQLCode, NativeError, NativeErrorText Some exceptions populate these such that the handler can filte / test / action some conditions (SQL exceptions, MQ, User Exceptions)...
about 11 years ago in App Connect 3 Future consideration

Create a feild to have tokens expire and notifications sent in advance that they will expire in 30 days.

Having a field for token expiration will allow the tool to track this in an automated fashion vs manually tracking. The token can have an expiration period chosen when requesting or regenerating it based on the security requirements for my company...
almost 2 years ago in IBM License Metric Tool (ILMT) 0 Planned for future release

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.