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 Not under consideration
Workspace App Connect
Created by Guest
Created on Dec 17, 2024

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.

Idea priority Medium
  • Admin
    Ben Thompson
    Reply
    |
    Jan 27, 2025

    Thank you for taking the time to raise this enhancement request and also for the service case that was opened on this topic. Looking through the Service Case in this situation it appears there was no evidence of any kind of CD failure within the ACE message flow itself - the node successfully passed a command to execute the file transfer. If there is a subsequent failure within the CD agent/server communication then it would (currently) be required to investigate this through the CD logging. The CDOutput node could in theory be enhanced with a separate mehanism (potentially a separate thread running in the integration server) whose responsibility would be to separately asynchronously communicate with the CD Server to receive and report status updates on active transfers. Unfortunately, whilst it would be potentially technically possible to do something here, we do not currently anticipate bringing this kind of closer administrative tie between the two products (ACE and ConnectDirect).