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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Hi Ben,
Thanks for the time to respond to the idea.
First I totally agree that of course no business user is interested in a technical debug log.
However I speak about the "initial setup of the designer".
This is typically done by some technical guys who's responsible is also to verify/test the used connectors.
In this phase we (Expert Labs, customer etc.) often struggle as the connectors are not working as expected.
Then of course you need to start troubleshooting to understand why.
Key for the troubleshooting is to understand the (complete) communication between App Connect and any other third party system. And as written: typically you only have the chance to 'analyze this communication' on the App Connect site - as you do not have access to the other system or any other network component. '
Does this make sense for you?
Looking forward to your feedback / thoughts
Thank you for taking the time to raise this enhancement request. We want to maintain Designer's appeal to the persona of business technologists, as opposed to integration specialists, so we are naturally cautious when considering exposing incredibly detailed information such as that being suggested here. We don't feel the output in the style of a tcpdump is an appropriate external for that target user to be able to interpret. Better, would be for the product to pass back actionable advice to the user about why their "connection" has failed. With that in mind, for this suggestion to be actionable, could you perhaps advise the precise circumstances where the connection doesnt work and how an improved response message or log could be helpful. From the description, it sounds like the main thought here is around account entries in the Catalog when the app connection is first established (as opposed to at "runtime" once the flow has been authored and is actually deployed and running)? Given the above explanation we do not intend to take this suggestion forward, but we would be open to improvements in the wording or detail of specific messages for specific connectors if you have examples which led you to the thought of this idea.