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.
Sunsuper operates an ebms AS4 gateway which interacts with the Australian Taxation Office and the Superannuation Transaction Network (STN). As part of being a participant in STN, Sunsuper has become a member of the Gateway Network Governance Body (GNGB) which governs the STN. A MoU binds Sunsuper to the Service Standards for the STN. Part of this requires STN gateways to abide by Binding Implmentation Practice (BIP) notes.
The GNGB has ratified BIP Note 17 - ebms Header Validation - a copy is attached.
Sunsuper raised PMR 17979,999,616 - and received this response from IBM L3 support indicating that IBM B2BAC is not compliant with BIP Note 17
From: email@example.com [mailto:firstname.lastname@example.org]
Sent: Friday, 6 April 2018 4:37 PM
To: Stephen Milburn
Subject: PMR 17979,999,616
Good Day! Please find the response from L3 on this query:
B2b Advanced Communications is NOT complaint to the specification https://ecurep.mainz.de.ibm.com/rest/download/17979,999,616/2018-03-13/17979.999.616.BIP-Note-17-ebMS-Header-Validation.pdf completely . There are few elements which are validated because it was used during exchange profile look up, visibility events processing or some other requirements for protocols and these includes the elements like MessageInfo, PartyInfo and CollaborationInfo. The whole incoming xml schema validation of xml against schema (ebms-header-3_0-200704.xsd) is not supported which means the elements like MessageProperties and PayloadInfo are not validated against xsd, Also, please note that b2bAC does not support xlinks.
Hope this answers your query . Please feel free to let me know if you have any queries.
Based on the advice from IBM, this RFE is being raised to formally request this enhancement to be considered. If IBM choose to not proceed with this enhancement in a reasonable timeframe, under the partnership with Sunsuper/Precision, IBM should be prepared to provide evidence about a) any delay; b) application or implementation mitigations that are fully supported and tested so relevant discussions can be held with the Gateway Network Governance Body (GNGB)
|What is your industry?||Non-Industry Specific|
How will this idea be used?
See the attached BIP Note 17 for further detail
Do not place IBM confidential, company confidential, or personal information into any field.