Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Categories Integration
Created by Guest
Created on Mar 12, 2021

Support Alternate Storage Locations for Message Tracking

Message tracking has existed for a while to support tracking SOAP based requests. In newer versions options were provided for tracking REST based requests. For troubleshooting API requests, this data can be extremely useful in determining what was provided to Maximo to explain why records were changed in the manner they were changed.

But enabling this, especially with high volume scenarios, has a negative performance impact and puts an additional load on the database server which impacts all users. And to minimize storage requirements, this data has to be purged by executing deletes. These deletes can cause blocking on the database which further impacts the performance.

With the new support for Kafka for JMS queues or Elasticsearch for logging, we'd like to be able to configure the message tracking to utilize one of these as a destination instead of the database. Both Elasticsearch and Kafka are designed for high throughput scenarios and have concepts that allow you to define a retention period that is enforced automatically.

Idea priority Medium