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 4, 2012

Add toolkit validation to soap and mapping flows to reduce runtime errors.

When working with SOAP request nodes (with associated wsdl) and corresponding SOAP response nodes and mapping nodes in the toolkit, I wired them together incorrectly and got runtime errors.

When I eventually got to the bottom of the errors; I felt that the tooling had enough information in the nodes and wsdl metadata and the mapping node to identify many of my errors at development time.
For example:
1) if a node output is an a particular domain and the subsequent node cannot handle that domain then the tooling should show that and hint as to how to quick fix it.
2) we found we needed to do a SOAP extract after every SOAP request. The flow should have been flagged as invalid if the required extract node was not there or incorrectly configured.

I feel that it should have been possible to validate the flows at development time rather than getting errors at runtime.

I suggest having different levels of this validation, ranging from only validate at deploy time, through to validating every flow save.

My understanding is that this requirement will also cover type propagation, where wsdl metadata and mapping information can be used to identify invalid flows.

Idea priority High
RFE ID 29206
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Feb 2, 2022

    Idea / RFE Review. The product has evolved significantly since this idea was initially raised, and whilst it is true that the untyped nature of the logical message assembly can sometimes lead to situations where validation can only be effectively reported post-deployment, there are many other aspects where the product now correctly highlights these kind of problems earlier (eg the function now available for helping generate map inputs and outputs based upon the GDM node's position in a flow), and it is also worth noting that the second example presented relating to the need for SOAP Extract no longer applies.


    Unfortunately there has not been further interest noted since our last update in September 2020. Given this, and the priority outlook we outlined at that time, on this occasion we have decided not to carry this idea further forward.


  • Guest
    Sep 15, 2020

    RFE Review. Apologies for the length of time this RFE has been in the status of Under Consideration. We agree with the sentiment of the enhancement request that where possible the Toolkit should provide guidance to the user as early as possible and if there is sufficient metadata at the Toolkit's disposal to discern the use case being attempted, guide the user along their path to avoid making accidental mistakes in flow configuration. This approach has been behind some of the enhancements introduced for REST API use cases in the interim period since this RFE was initially raised - for example, knowledge of the subflow operation context of the REST API helps users prepopulate the source for a graphical data map in the current latest release. We note the solitary vote received for this RFE over a long time period, and also that it is unlikely that this kind of enhancement relating to web services, will be prioritized above enhanced support for REST APIs. Given this it is unlikely to see movement on this RFE in the short term, but we are updating its status to Uncommitted Candidate and will continue to monitor for signs of popularity.

  • 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