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.
While using ITX 10.0.3 and running from the Launcher within a container, I am using the Amazon S3 Blob Storage adapter to GET a file and am able to successfully read the object and write it locally. However, the adapter command string and/or input card options do not provide a means to delete the BLOB after a successful read/pull. HCL recently provided me with an updated JAR file (m4s3.jar) so we could use the S3 adapter against our own on-prem S3-based Object Store without needing to provide a REGION, and this updated JAR file is working fine. The Azure Blob Storage Adapter currently provides a READ MODE setting to allow the blob to be deleted after being read. We need to have this same capability with the AWS S3 Adapter. Please advise.
|What is your industry?||Healthcare|
How will this idea be used?
We will use this functionality to integrate out batch processing running in containers with batch file flows.
Do not place IBM confidential, company confidential, or personal information into any field.