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.
-
RestAPI support for Token Authentication rather than Basic Authentication
Looking for a future service availability to support Token Authentication, either with RestAPI or new one. As per my conversation with an IBM engineer on another troubleshooting call; support of Token Authentication by RestAPI is planned in future...
-
Fix the migration of envelopes from Sterling B2B Integrator and ITXA
When we export envelope from SI and import to ITXA, we are missing some configuration. Please see the word document attached. I am also attaching XML export file where you can find the UNH_DEFAULT_OUT envelope.
-
Add support for AES-256 encryption algorithm for data at rest in Global Mailobx
B2Bi already supports AES-256 encryption for data at rest, so global mailbox should offer the same level of encryption.
-
SSO and OAuth support for authenticating B2BAPI access
At minimum would need to able to use the SEAS SAML like tokens to allow authentication of APIUser for B2BAPI calls. Liberty Profile native supports both SAML /OAuth authentication and the current instance does authenticate with B2Bi so it should a...
-
Show more detail, on progress bar, when using IIM to upgrade B2Bi
Upgrading B2Bi v6.0 to v6.1 took almost two hours. For the majority of that time, IIM's progress bar sat at (about) 60%. It would be helpful to see what it's doing or even update the progress bar more frequently.
-
On the Code (List) Info form, put Text1 thru Text9 on their own lines and make the data fields much wider
Please put Text1 thru Text9 on their own lines and make the data entry field as wide, or wider, than the size of the Description data entry field.
-
SQS Client adapter to be extended for put
Currently the SQS adapter can only read from SQS. It should also be possible to put messages to SQS and to be able to use this service within BP
-
Enhance SAP Suite adapter to support Secure Network Communication (SNC)
Support JCO3 SNC parameters in SAP Suite Adapter in B2B Sterling Integrator. SNC secures the data communication paths between the SAP System components and B2B Sterling Integrator. It will add additional security feature for secured communication.
-
Global Mailbox's Cassandra and ZooKeeper's SLES support
Having the ability to install CAS and ZK on SLES, avoiding mixed environments on existing installations (SLES for B2Bi and RHEL for CAS/ZK)
-
Allow email address to use as user ID
We have requirement to use email address as the user ID in sterling integrator.
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
0
Future consideration