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.


Add a new idea Subscribe
Status Submitted
Workspace WebSphere Liberty
Created by Guest
Created on Aug 28, 2024

RELATED IDEAS

Provide support for MQ Classes for JMS in Liberty

RFE to provide support for MQ Classes for JMS in Liberty:

Migrating Applications from tWAS that use MQ Classes for JMS or MQ Classes for Java to another J2EE environment not supported for Liberty, but is supported for any other J2EE environment.

As per the documentation here https://www.ibm.com/support/pages/node/727251 Liberty is the only J2EE environment that support is not provided for MQ Classes for Java and the MQ allclient.jar.

This support limitation, for Liberty only, also includes support of the MQ Classes for JMS.

Migrating applications that utilise MQ Classes for JMS from tWAS to Liberty would involve (at a minimum):

  1. Rewriting applications to use the J2EE JMS APIs (javax.jms)

  2. Moving configuration of client-side access to MQ resources from the application into Liberty Application Server configuration.

  3. This would include translating from programmatically setting something like WMQ_TARGET_CLIENT to a property in server config like targetClientId. It is unclear if there are mappings for every configurable property currently in use and whether defaults remain the same across the different APIs.

  4. Switching from non-J2EE MQ resources in tWAS to J2EE (managed) resources in Liberty.

NOTE point 4 above is a significant risk to the migration project that could require a major refactoring of the application. Currently in tWAS, the MQ client-side resources are not managed by J2EE so, for example, do not interact with the JTA transaction context.

The current migration path to Liberty requires changing the MQ resources to J2EE managed resources that do interact with J2EE components such as the JTA transaction service.

Idea priority Urgent

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.