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 Future consideration
Created by Guest
Created on Oct 7, 2025

Improve MAS9 deployment process to allow deploying java customizations with minimal or no downtime

Today in 7.6 we deploy java customizations without taking a full outage via a process we call dynamic deployment. This is a homegrown process where essentially, we have 2 data centers and we take Maximo down in 1 data center and deploy the change there and bring it back up. While the first set is down, the load balancer redirects traffic to the second data center where the jvms stay up serving users until the instances in the first data center come back up at which point the second set of jvms goes down to have the new changes applied. This process minimizes impacts to just transactions happening on the system when it goes down, by doing this during off hours as well there's virtually no loss of data. New requests go to the jvms that are still up so integrations continue to function.


With the move to MAS9 this process no longer works so it's a big step backwards for us in terms of deployment impacts. We'd like something like this to be developed so that downtime can be minimized when doing deployment of changes that don't need a full outage like a database config.

Idea priority High