IBM Sterling Ideas
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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you, 1. Post an idea 2. Upvote ideas that matter most to you 3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Experience operating a B2B Advanced Communications/ IBM MQ / Sterling Business Integrator ebms AS4 gateway has shown that there are many ways in which outbound messages can fail. Relatively few of these are covered by the Retry policy mechanism built into B2BAC.
There examples not covered by Retry are -
HTTP 500 connection error
Socket time out error
Connection forcibly closed by remote host
The attachment shows just show of 40,000 messages over the last 12 months that have required expensive manual user intervention and reprocessing to simply send the message again. In most cases these were simply the receiving partner being busy or temporarily unavailable or an unstable network connection. Our 5 years of experience operating this software. If we extrapolate the cost out over the last 5 years - the inefficiency and cost and reputational impact is significant.
From an operational perspective there is no difference between a message that was not able to delivered due to a B2BAC destination being marked as unavailable and in retry mode as opposed to one of the 3 failure types indicated above. A message failure is a message failure regardless of the mechanism by which it failed.
This request comes of the back of a PMR which recently advised us that the 3 scenarios identified above are NOT covered by the Retry Policy functionality. Consequently, we require a feature built in B2BAC where it recognises outbound failure (including the cases above) and will attempt to redeliver those messages again automatically. This would reduce considerable manual overhead and expense associated with supporting messaging through this product.
|What is your industry?||Financial Markets|
How will this idea be used?
This functionality will be used to reduce operational support costs, automate replays and get humans back to actioning important deliverables for our business colleagues
Do not place IBM confidential, company confidential, or personal information into any field.