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

All ideas

Showing 2543

MQ appliance: provide REST endpoint for managing local users and groups

While MQ objects can already be configured and created via the REST API, certain functionality is not available and still requires command line access. Examples for these functionalities are management of local MQ users and groups. (e.g. cli equiv...
over 1 year ago in MQ, MQ Advanced & MQ Appliance 1 Not under consideration

Utility to consume msgs off the SYSTEM.DDELAY.LOCAL.QUEUE and deliver to the destination Qs ignoring the delay

Provide an utility that can be used to process the msgs on the SYSTEM.DDELAY.LOCAL.QUEUE ignoring the delay and send the msgs to the destination queues in the event that delayed msg processor is unable to handle the volume of msgs on SYSTEM.DDELAY...
over 5 years ago in MQ, MQ Advanced & MQ Appliance 2 Is a defect

Optimized database connection management

Currently WMB ODBC connections are limited in the sense that all database transactions by default are contained within the scope of the message flow transaction boundary. ESQL Compute nodes have a 'Transaction' property which can be set to Automat...
about 11 years ago in App Connect 3 Future consideration

Have Front side Handler for ICON (Resume Tpipe support)

Customer would like to have DataPower support for resume Tpipe. Have Front side Handler for ICON (Resume Tpipe support)
over 5 years ago in DataPower Gateway 0 Future consideration

HSTS (S3 Metadata): Need for a feature that will allow the original metadata (example in the description) into the object with metadata at the destination Neptune2.0. The metadata was pointed to in Neptune1.0.

I.e., there is a need for implementing in a generic way for the S3 API to preserve S3 metadata for S3 to S3 transfers, reading and writing any headers that start with ‘x-amz-meta-’ for any transferred objects. Example metadata for some of the file...
over 1 year ago in Aspera Ideas 0 Future consideration

Onboarding of LDAP Users to Common Services User Registry on CP4I

The client migrated the APIC from v5 to v10. Previously, the user access APIC directly via the LDAP user registry. And we set correct permission in APIC for about 200+ users. Now, after migrating to APIC v10, accessing the APIC, it will redirect t...
over 1 year ago in API Connect 0 Future consideration

Reccyle JMS connections and sessions after a period of inactivity

Problem description:We have JMSOutput nodes configured using Tibco EMS as the JMS provider. After a period of inactivity, a new transaction is triggered that writes to the JMS Output node and IIB attempts to use a session that is closed, so it is ...
over 8 years ago in App Connect 4 Not under consideration

TS004045968 : DPOD appliance logs to export third party external systems(SIEM, Splunk etc)

Hi Team, We are using DPOD version 1.0.10.1 and need to send DPOD appliance logs to external servers such as either SIEM or Splunk etc ? & how to do it ? This is to capture appliance(CLI) audit, access log etc to monitor by Governance team for...
about 4 years ago in DataPower Operations Dashboard 1 Not under consideration

Command line tool to kill active debug sessions

We would like to have a command line tool to kill active debug sessions. This tool we can than inject into our CD CI Pipeline so that sessions can be killed before a deploy starts. We notice that on ACE the broker will become instable when deployi...
almost 3 years ago in App Connect 1 Future consideration

rpm packages for IIB9.x for deployment in RedHat based systems

With the adoption of puppet and chef in enterprises, having rpm packages for IIB9 installation/uninstallation will be great help. It will enable installation/uninstallation/upgrade managed by a package manager like yum inside puppet module/chef re...
over 9 years ago in App Connect 4 Not under consideration

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.