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 updateson 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
SSH Key based authentication with LDAP is not supported in B2BI, and also with SEAS integration. Even though SEAS has SSH Key support with LDAP, SEAS integration APIs with B2BI does not have support for sending SSH Key.
During a sftp authenticati...
Enhance SWIFTNet7ClientResend business process to update previously failed filegateway deliveries
Currently SWIFTNet7ClientResend will be triggered via the SWIFT Adapter Scheduler to look at the SWNET_MSG table for failed PUT transfers to SWIFT. Upon detection of these types of failure the scheduler will trigger an execution of the SWIFTNet7Cl...
Update the EBICS HAC schema to comply with standard
the xml schema used in EBICS HAC is ISO20022 pain.002.001.05 when it should be pain.002.001.03 according to the 2.5 version of the standard. Even more, in version 3.0 is not updated to .05 and still remains .03 (need to be doubled checked though)
EBICS Server / Client support of xml structures without ds: prefixes
As of now EBICS Server and Client is not able to parse XML structures without ds prefixes in some places, so the parses explicitly needs those.
Where as the XML itself is valid against the XSD of the EBICS order types.
We need to have the EBI...
Do not place IBM confidential, company confidential, or personal information into any field.