Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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

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,

  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 product management 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 notification 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.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Created by Guest
Created on Aug 5, 2019

To have separate timeout configuration for session expiration of interactive users sessions and back-end batch processes

Based on the recommendation for large metadata import - https://www-01.ibm.com/support/docview.wss?uid=swg21621492

Inactive Session timeout needs to be configured to longer timeout value (86400 seconds) as metadata import batch processes run for several hours. This also becomes applicable to user interactive sessions.
The customer has highlighted this as a concern  "Lack of proper session expiration" and requested for a way to configure the timeout for user inactive sessions to a shorter duration without impacting their backend batch processes.

Needed by Date Dec 31, 2019
  • Guest
    Aug 16, 2019

    The IIS timeouts are set long enough to make sure that the longest running (batch) sessions do not expire. however, this timeout also gets applied to user sessions which is not as per the banking security standards for OCBC.  Hence they requested for a mechanism to handle user sessions separately.

  • Guest
    Aug 14, 2019

    We could look whether or no the time out could be set longer or be set so that sessions do not expire but there is no way to differentiate between seesions