This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Our content stores (currently DB2) are growing through more and bigger outputs from reports although we have a rigid housekeeping. But in any case, we are limited to a certain content store size. And database storage is very expensive. File externalization is not an option. We also cannot enable new features like data sets for our customers because this would further increase content store size.
The idea is to externalize outputs from reports and datasets to a (cheap) S3 cloud storage where size and amout of data almost doesn't matter.
Another advantage of this idea is the easy reuse of output files, for example in a use case where Cognos results should be exported in csv format. For this it would be beneficial when there is a (configurable) metadata file in S3 for each output file.
The connection between Cognos and the S3 must be a strong connection and the output must be further downloadable and accessible via Cognos. The user or the SDK/REST API application should not notice that there is a S3 instead of a DB2 database in the background.
The current implementation of S3 cloud storage has some disadvantages and the connection is not strong. It's more like a "fire-and-forget" approach and files with the same name will be overwritten which is a no-go for content store externalization.
Do not place IBM confidential, company confidential, or personal information into any field.