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 Jun 22, 2017

Get HTTP response error codes for SOAPRequest node in structured message tree elements

At SOAPRequest node, services responses are propagated to "out", "fault" or "failure" terminals due to http response.

HTTP/1.1 200 to "out" terminal

HTTP/1.1 500 to "fault" terminal as SOAP response and populated X-Original-HTTP-Status-Code header.

HTTP/1.1 404 to "Failure" terminal as HTTP error response and information in populated in exception message where readability is not user friendly and acknowledgement of IIB service consumer is tricky

Getting HTTP response error codes for SOAPRequest node in structured message tree elements would be easier for user experience and development and troubleshooting issues

Idea priority Medium
RFE ID 106875
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Oct 19, 2020

    RFE Review. Thank you for taking the time to raise this RFE and apologies for the length of time it has been in Submitted status. With the product in its current form it is already possible to get access to the HTTP Status code returned by the SOAPRequest node, without further enhancement. The HTTPReply header carries this status if the invocation is successful and control passes through the out terminal when propagating to downstream nodes in the flow. Alternatively if the Failure terminal of the SOAPRequest node is used then there will be presented an ExceptionList describing the problem which the node encountered. For example this could include a BIP3691 which is a structured exception including the HTTP Status code of 404 Not Found. Having noted this, we still intend to place the status of this RFE into Uncommitted Candidate status as we acknowledge that the ExceptionList is not the easiest structure to navigate and developers would most likely find it easier to have the status code presented in a more easy to use fashion, for example in the LocalEnvironment.