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 Future consideration
Workspace App Connect
Created by Guest
Created on Aug 23, 2022

Smart Connector for IBM Sterling Connect:Direct in containerized ACE

Banco de Credito del Peru (aka BCP) is a big customer and have hundreds of Message Flows running on IIB V9 that do operations with files and transfers them to other servers using CA XCOM. They need to get out of Backlevel and want to migrate from IIB to ACE running in containers on OCP, and replace CA XCOM with IBM Sterling Connect:Direct. However, the problem they face is that ACE running in Containers doesn't have an integration with IBM Sterling Connect:Direct. BCP knows that there are CDInput and CDOutput nodes in ACE running traditionally in virtual machines using a local Connect:Direct server, but their strategy is to get out of virtual machines.
Idea priority Urgent
  • Admin
    Ben Thompson
    Sep 14, 2022

    Idea / RFE Review. Thank you for taking the time to raise this suggestion, which we agree would improve the product's capabilities in containers as it would enable users to more easily independently scale the ACE product from dependent MQ queue managers. In implementing this, we would likely take a similar approach to product externals as other cases where we have relaxed the underpinning relationship with MQ - we would make the remote default queue manager applicable when choosing the queue manager (via MQ client connection) used by the Connect:Direct message flow nodes. Status of the idea is updated to Future Consideration (please note that this is a statement of intent but unfortunately does not imply a guaranteed timeline for implementation).