Cloud Platform

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

ADD A NEW IDEA

FILTER BY CATEGORY

WebSphere traditional

Showing 116 of 1688

Include re-try and timeout with Activation Spec listener status in the WAS Console

In the WAS Console, when we look at the Activation Spec listener status, instead of just showing 'green' or 'red', it should have functionality where we're able to see the re-tries with the connection the IBM QMGR. Multiple App teams with RBC will...
6 days ago in WebSphere traditional 0 Submitted

Allow Application Install for .ear Files Greater Than 1 gb

The 1 gb limit on deploying an ear file in WebSphere is causing us to have to use Configuration Manager to deploy any changes to the application and increasing downtime.
11 days ago in WebSphere traditional 0 Submitted

Support Java 2 Security to restrict application acceess to local resoures

This a CAT-I finding for DoD STIG: Below is their reasoning:Rule Title: The WebSphere Application Server Java 2 security must be enabled.Discussion: Java 2 security provides a policy-based fine grained access control mechanism that increases ove...
12 days ago in WebSphere traditional 1 Submitted

The Useable WebSphere Auditing Functions Are Required by the Department of Defense

The current WAS Auditing function does provide readily useable logs to even track down simple events such as starting/stopping an application server via the WAS Admin Console. I would like to see such functionality added to the NDM audit logs.I a...
about 1 month ago in WebSphere traditional 1 Submitted

Prevent Application Redistribution

This is what the client company is requesting. I'm using WebSphere's application binary configuration. Redistribution occurs when changing application options. We want to control or eliminate this.
2 months ago in WebSphere traditional 1 Not under consideration

WebSockets support for IIS.

I have a updated version of a application that now parts of uses WebSockets. IIS supports WebSockets but not the ISAPI Plugin. I am told that Apache would support this but I dont think this is a option for me. If you bypass IIS and go directly...
3 months ago in WebSphere traditional 1 Not under consideration

Add support for com.ibm.mq.cfg.jmqi.useMQCSPauthentication in WAS 8.5.5.X

Currently the MQ RAR packaged with WAS 8.5.5.X is too old to support com.ibm.mq.cfg.jmqi.useMQCSPauthentication. This means that for anyone who is unable to move to WAS 9 any MQ connection is required to use far less secure passwords.
4 months ago in WebSphere traditional 1 Not under consideration

Enhance JAX-RS 2.0 client implementation to make it use WAS SSLSetting defined in the cell automatically

See also CASE TS005178606.
4 months ago in WebSphere traditional 0 Future consideration

Allow encryption algorithm to be AES-256 in GCM mode for JAX-WS and JAX-RPC security runtime.

We have recently upgraded to AES-256 in CBC mode on JAX-WS and JAX-RPC security runtime for our application servers, however we are required by our cryptography standards to move to the preferred GCM mode before the end of 2021.This option does no...
4 months ago in WebSphere traditional 3 Future consideration

Create User for WAS Console That can see only Applications tab After login

create user for application team to enable them to deploy their application only, after this newly created user logins cant see or interact with any tabs within WAS console except Applications tab only.All WAS console tabs become invisible to this...
4 months ago in WebSphere traditional 1 Not under consideration