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 Future consideration
Workspace App Connect
Created by Guest
Created on Jul 7, 2014

Add retry mechanism for EMAIL node

We continue to see intermittent network connectivity issue between the broker and SMTP Relay servers at our site. In order to mitigate the issue we have implemented the broker code to retry when there is a connectivity issue. But it would be nice if we had a retry mechanism functionality added with in the EMAIL Node itself

Idea priority Medium
RFE ID 55764
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Jul 30, 2021

    Idea / RFE Review. Apologies for the length of time this idea has been in the status of Uncommitted Candidate / Future Consideration. Although we have not yet managed to prioritise this feature, and despite the solitary vote it has received, we absolutely still see value in this request. Given the EmailInput node externals for retry we have strong precedent in this area of functionality and ideally we'd like to make the input and output variants of these transport nodes equivalent to one another. We will continue to monitor this idea for popularity. Status is maintained as Future Consideration.

  • Guest
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

  • Guest
    Aug 4, 2014

    Thanks for raising this requirement. It's actually quite a tricky problem to solve, because during an outage the problem would be transferred upstream to the broker, as all the processing threads in the broker would now be hanging waiting for the SMTP server to become available again, which will prevent additional processing from the input sources.
    For certain classes of error I can certainly see that a retry mechanism would be beneficial however, and would complement the existing retry techniques that WMB/IIB has - check out the record and replay facilities if you haven't already.