we're in a 3 tier environment, using WebSphere and connection
pooling to a 390/v7 instance. some of our clients (claiming
Sarbanes/Oxley made em do it) don't like that the connections up
to the MF are on the same UserId from the connection pool
implementation.
i've found docs, but no examples or RedBook articles, of how to
use this other DB2DataSource. it's in db2jcc.jar, and i gather it's
the type-4 driver. there is a setDB2ClientUser method, which says
that this changes the userid on the connection, but not on the
jdbc connection; if that makes sense.
so, will any logging/auditing that pre-exists at the MF see this
UserId rather than the jdbc UserId used when creating pooled
connections? adding just one line of code to the server side would
sure be nice.
thanks,
robert
