IBM Sterling
This portal is to open public enhancement requests for IBM Sterling products and services. 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.
Dear Siva,
The RFE highlights a valid observability and troubleshooting gap in IBM Sterling B2B Integration SaaS. When transactions fail before inflight sender, inflight receiver, or message type are captured—or when these are not configured in the basic TX map—customers are left with only JMS metadata (sender ID, receiver ID, message type) as identifiers. The absence of Data Extract APIs that allow searching by these JMS parameters makes it difficult to trace, diagnose, and support failed messages, particularly in production incidents.
Providing an API that supports search using JMS sender ID, JMS receiver ID, and JMS message type would significantly improve supportability, reduce investigation time, and address real‑world failure scenarios where higher‑level business identifiers are unavailable.
To properly scope and assess this request, the PM should seek clarification on the following:
Use‑case scope
Is this API primarily intended for support/troubleshooting, or will customers use it for automation and reporting as well?
Expected data coverage
Should the API return results for both inflight and persisted transactions, or only failures?
What time range / retention window is expected for searches using JMS parameters?
Result uniqueness
Do the JMS sender/receiver/message type combinations uniquely identify a transaction, or should the API support returning multiple matches?
Response expectations
What attributes are expected in the API response (payload, metadata, status, timestamps, routing details)?
Is pagination or result‑size limiting required?
Security and access
Should access to JMS‑based searches be restricted to admin/support roles only?
These clarifications will help ensure the API is designed to meet operational needs without unintended performance or security impacts.
Manoj Panda
Senior Product Manager
IBM Sterling