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
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.
Do not place IBM confidential, company confidential, or personal information into any field.