Skip to Main Content
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 Not under consideration
Workspace WebSphere Liberty
Created by Guest
Created on Apr 5, 2022

Liberty z/OS -J2EE end-user(the WAS principal) to DB2 (setDB2ClientUser)

Liberty z/OS applications require audit and logging in DB2. We need to know who made the changes in the database records.

The idea is to pass to the DB2 the J2EE end-user(the WAS principal) and put it on the setDB2ClientUser for the DB2 connection.


Our question is:

Could we use it of having it included in the application similar in principle as https://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/twlp_mig_wscallhelper.html ) ?



From IBM Case come the answer bellow:

I have promptly received following answer: Liberty doesn't expose either WSCallHelper nor datastore helpers as API. The ability to set client info on a JDBC connection has been available since java 1.6, so this can be used in a portable fashion without using any Db2-specific APIs. Using the setClientInfo(...) API to set the client info prior to using a connection you've obtained, you can achieve the same result in your application."


But the applications use JPA with one JPA entity manager. It will be required that all the applications should add the call to the API in their code.


Idea priority High
  • Admin
    Graham Charters
    May 13, 2022

    Thank you for the suggestion. The requirement does have merit, but looking at it with respect to our total backlog of requests we do not see sufficient interest in this enhancement to merit delivery any time in the foreseeable future. Given the unlikelihood that we would deliver this, we are declining the request rather than leaving it in an uncommitted state for an extended period of time. If you would like to discuss this decision further, please contact Graham Charters <charters@uk.ibm.com>.