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 Aug 14, 2025

Enhance APPBEAN/DATABEAN Automation Scripting to allow classes from maximouiweb.war

IBM has enhanced automation scripting in 9.1. You now have the ability to extend Application Beans (APPBEAN) and Data Beans (DATABEAN) (i.e. enable system property mxe.script.allowbeanscript).  I discovered a class loader limitation while creating one of these scripts. In my script I imported psdi.webclient.system.runtime.WebClientRuntime class.  This class exists as part of the maximouiweb.war file.  The script executed as designed.  It wasn't until I scaled/restarted the maximo-all pod that I ran into the class loader issue below: 

[script] BMXAA7836E - The script did not compile. ImportError: No module named runtime in <script> at line number 7

Only way currently around this issue would be to resave the automation script after scaling/restarting the maximo-all pod or rewriting the script to not include classes which exist in the maximouiweb.war file.
 

My argument to enhance automation scripting to allow classes which exist in maximouiweb.war is the following:

Before automation scripting existed I would extend bean classes through java customizations and this required access to classes which exist in maximouiweb.war. Now that automation scripting allows bean scripting I don't see how it's any different. I'm guessing as more and more  customers start to utilize APPBEAN DATABEAN scripting it could prove to be a significant limitation.

Idea priority Low
Needed By Quarter