Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform 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).


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
Workspace WebSphere Liberty
Created by Guest
Created on Sep 22, 2025

wsAtomicTransaction always enabled in Liberty

tWAS allows the use of policy sets which the customer has used to control whether WS-AT is active for individual web service endpoints
Liberty does not have this function (policy sets)
Liberty enables/disables WS-AT based on the presence or absence of the feature
If enabled on a server, WS-AT is enabled for *ALL* web services contacted, so a global transaction will be sent regardless of the presence or absence of any AT assertion WS policy
The customer could explicitly suspend the global transaction when invoking a non-transactional web service but this code change would be unwieldy across all their apps
The customer wants new behaviour in Liberty to check for the relevant WS policy before propagating any global transaction
 

Idea priority Urgent
  • Guest
    Sep 23, 2025

    LIBERTY's behavior regarding the wsAT must be the same as traditional Websphere because it's unthinkable to require all external third-party providers to honor the wsAT headers. And we have countless external third-party providers.