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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
RFE Review. As part of our standard process for reviewing RFEs we have recently discussed this RFE and wish to note that it remains of long term interest to us. It is regrettable that we have not yet managed to prioritize this requirement for immediate action, but we will continue to monitor for popularity and keep it in mind for future plans. Status is maintained as Uncommitted Candidate.
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
Thank you for raising this requirement. As alluded to in the description, we see distinct kinds of inbound traffic over HTTP coming in to IIB - SOAP HTTP and other non-SOAP formats (most typically but not exclusively, JSON formats driving RESTful implementations). As stated, we have currently chosen the expression of the 404 Not Found message as HTML as a preferred common denominator. Of the suggested options for enhancement, the forcing of a distinct listener for HTTP or SOAP services sounds rather restrictive. There will be users who wish to receive traffic to different URL fragments on the same port, some of which will be SOAP based and some not, and this approach would not satisfy this. Option 2 to change default behaviour would also break backward compatability for users preferring and relying upon the HTML format of fault reporting. Option 3 sounds the most promising - providing a configuration option to choose between different methods of error reporting. Such a choice could be made on the HTTPConnector object, and various levels of granularity possible - for example associating particular URL fragments with particular style of error report. In the short term, I understand you have already been in contact with L3 service on this topic and URI wildcards have been discussed. Status of this RFE is updated to Uncommitted Candidate.