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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
The current implementation of the JSR-352 (Java Batch) in WebSphere Liberty Profile requires to have both a connection to the JobRepository and to the business data for chunk processing. As a consequence the system always needs a global transactio...
View et Adapted bootstrap.properties into AdminCenter
It would be very interesting to see and be able to modify the bootstrap.properties file of the server liberty from AdminCenter.Currently, the server.xml is displayed in AdminCenter with the variables in the bootstrap.properties file. It would be i...
Priority of tokens are configurable when mixed authentication are enabled
When Liberty is configured to accept both LTPA tokens and JWT tokens, Liberty uses JWT tokens by default. LTPA token is ignored by the server. We would like to open this requirement that allow administrator set which SSO token is used for server a...
Please consider support of the IBM JDK and Liberty Profile on Beaglebone Black. Headless support will suffice, but utility libraries to access the hardware would be nice (already using purejavacomm a.o.)
Liberty Act Spec with destinationRef using reference to App context variable
Trying to set an MDB with an activation specification that references a JMS Destination Definition that is set in the application does not work. The issue appears to be the server.xml configuration is trying to do the lookup before the application...
Do not place IBM confidential, company confidential, or personal information into any field.