This is an IBM Automation portal for Integration products. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Sharing the Slack conversation related to the idea for reference. ( Anamitra Bhattacharyya ( Maximo STSM), Matthew Leming (MQ STSM Chief Architect) & Vinod Cyriac( MQ Developer )) on 6th Oct 2026
Hi @Vinod Cyriac - thanks for picking this up - this I believe was something a make or break for Maximo - at the time when we were porting our customers to Liberty - probably 6 years back. So in absence of that - we did a workaround - albeit not a good one. So the use case is - Maximo - while it runs on JEE container - it in many cases does not use the JEE thread. For example we have a cron job framework that simply uses java sdk thread pool that executes a job - for example updating a workorder. Now that Workorder update generates many events (workorder being a deeply entrenched object in Maximo - an update there will generate many other DML - which will generate many events) - which say needs to go to SAP or Oracle Fusion or some other application - JMS queue store and forward. But we need to make sure all these messages are written in one transaction. That is where we have been using the WAS ND jms session transaction for 20 years I would say (and a bunch of our customers are still in WAS ND - havent moved to the new Maximo with Liberty). JMS JTA was not available for a java thread - and JMS Session tx was the only way to do this. In absence of that - we hacked up a solution to check if the JMS server and the queue were accessible to the maximo runtime code and then proceed to autocommit (as there was not session tx). Its a degraded way to do this - compared to what we did in WAS ND. I would say 2000 + customers would love to have the session transaction back - if you can add it.
Many customers provide their own MQ - others use the Liberty built in JMS and some use both.
Customers anywhere between 3000 to 4000 - with 2000 is active contact
Sharing the Slack conversation related to the idea for reference. ( Daniel Matthews (Liberty ) , Vinod Cyriac ( MQ Developer ) on 7th Oct 2026)
Vinod Cyriac ( MQ Developer ) :7th Oct 2026
Good morning Dan
We are currently reviewing and discussing this idea. Support for JMS Transacted Sessions for MQ RA (WAS Liberty):
https://bigblue.aha.io/ideas/ideas/MESNS-I-174.
It would be very helpful if you could share:
The number of customers ( and name if have) who have expressed interest in this capability.
And how this requirement is relevant today.
This information will help us assess the demand and take the idea forward for discussion in the board meeting.
Thank you.
Daniel Matthews (Liberty ) : 7th Oct 2026
I don't have any accurate numbers. JPMC, KAISER, HANG SENG BANK, FIL INVESTMENT MANAGEMENT (and BELL CANADA via Maximo) all had issues when migrating from tWAS to Liberty. JMPC was quite a big issue for some time, but they wanted other function available in tWAS (like accessing the MQ Java classes IIRC). In general it's customers migrating from tWAS where we get cases in for this (because tWAS does support JMS transacted sessions despite being a J2EE App Server). I've talked about some of the issues with migrating from tWAS to Liberty for JMS users before with Macdara Butler (Liberty Product Manager) - he's been looking for ways to provide value-add in WebSphere Liberty (vs Open Liberty) as well anything that provides a better migration story (to retain migrating customers on Liberty rather than a competitor) and it strikes me that this, along with MQ support for usage of the MQ classes in general (as tolerated in tWAS or any other J2EE server - apart from Liberty) might be something Mac is interested in - which may help with any Liberty dev resource requirements.
Vinod Cyriac ( MQ Developer ) :7th Oct 2026
To summarize, you are looking for two features, which both having dependency with Liberty team.
Support for loading the MQ classes for Java API in Liberty.
Support for local transactions within Liberty. ( Maximo STSM also recommended this one)
We hope to deliver a solution to this in a future MQ update