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.

Status Future consideration
Workspace WebSphere Liberty
Created by Guest
Created on Mar 8, 2021

Option to pass parameters to BELLS feature

The use of bells-1.0 makes it easy to develop and deploy a liberty extension, but often it is very wanted to be able to configure the module.

Currently the only way is to share environment variables, but the normal Liberty way is to put properties into the module from server.xml.

In our use, the configurasjon of datasource name is more convenient to pass as shown below. Normally the datasource configuration also is in server.xml.




datasourceName="jdbc/datasourceJPA"
/>



It could be even more convenient to use liberty variables, so the same variable is used to configure the datasource and the bell module as well:





datasourceName="${datasource}"
/>



Use Case
N/A
RFE ID 149114
RFE URL
RFE Product WebSphere Application Server
Idea Priority Medium