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.
Idea / RFE Review. Apologies for the length of time this suggestion has been in the status of Uncommitted Candidate / Future Consideration, during which time the product has evolved considerably. Noting that this particular suggestion for enhancement was initially raised in 2012, since that time the product architecture has improved considerably in regard to the querying of the status of individual flows or groups of flows through the administration REST API. Message flows can be grouped into applications, services or REST APIs, whose status can be queried with a simple REST call. These APIs are likely to be sufficient for a load balancer to query on in order to determine flow availability. That said, it is also true that the admin REST API doesn't currently have a *single* URL for querying all the HTTP URL fragments on which the HTTPListener resource manager is currently listening on. This specific aspect is already the subject of another idea (https://integration-development.ideas.aha.io/ideas/APPC-I-258) which you or other subscribers may wish to vote on. Noting this alternative in the system, and the REST API enhancements mentioned above, we are updating the status of this idea to delivered.
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
Thanks for the update - I understand what you need now; good requirement.
I am aware there is a new REST API in Broker 8. We are still running Broker 7 and will not migrate before 2014. We have a need for a single REST resource telling us that every single http-input-node and soap-input-node is up and listening.
We noticed there is a time shift between the event the execution group being in status "started" and the situation every single http/soap-input node being up and listening.
A load balancer is running http probes to verify the status of the http based services. Instead of probing each single http-input-node we need one endpoint providing us a summary.
Maybe one can request the http listener somehow. As a workaround we deploy a simple "alive" flow with a http input node. As soon as this flow answers 3 times in a row we feel save to assume all siblings are ready as well.
Interesting requirement, thanks for raising. Broker already exposes an administrative REST interface that can be used to query the state of message flows, though we would like to improve it so that it can provide more detailed information (e.g. related to its specific resource utilisation). It would be interesting to understand exactly what kind of information you'd like to see from such a health monitoring call -basic started/stopped status, throughput information or something else?