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 Subscribe
Status Future consideration
Workspace App Connect
Created by Guest
Created on May 16, 2014

RELATED IDEAS

Access/Tracing Log for HTTP Listeners

It's sometimes hard to debug things like the SOAP input nodes when clients are behaving badly and the node is rejecting the request before it goes into the flow or to prove that somebody is or isn't reaching the server. For example, if a client leaves ?wsdl at the end of a URL when making a request that actually sends a SOAP message they might get back the WSDL instead of the intended SOAP reply, this doesn't register at the SOAP Input node or in the traces for HTTP listener. Another difficult one to debug is when an operation is not qualified with a namespace, broker sends a meaningful SOAP fault back but what would be nice is to capture what the client actually sent and highlight their error, you can do it with a sniffer but that's not always easy to setup in a secure environment.

Idea priority High
RFE ID 53657
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Reply
    |     Mar 20, 2023

    Thanks a lot for raising this idea! I support it as an improved and more easy way of trouble shooting directly within the IBM product is always appriciated.

  • Guest
    Reply
    |     Aug 5, 2020

    As part of our regular RFE review process, we note that this requirement is still on our radar. Enhancements were made to IIBv10 HTTP listener tracing using Tomcat Access Log capabilities, but the move with ACEv11 to a C-based library implementation means that this remains on our list of potential future enhancements. Status remains currently as Uncommitted Candidate.

  • Guest
    Reply
    |     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
    Reply
    |     Jun 10, 2014

    Thanks; we want to make it as easy as possible to debug solutions on IIB, and having better tracing for the HTTP listeners will help with this. Thanks for raising.

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.