|
| Re: Pre and Post activities |
 |
Mon, 7 Apr 2008 15:36:27 -0700 |
There are no such hooks in ALDSP.
But you should be able to control the 'client id' for Oracle by defining a
Service Account for the JDBC Data Source. (in ALDSP 3.x only).
The (deprecated) SourceBindingProvider feature will let you 'switch' DataSource
names - and if you use your imagination, you could create a
SourceBindingProvider that (dynamically) creates Connection Pools an Data
Sources for specific users, then returns that data source name. You end up with
a Connection Pool and Data Source for every user - but it does work. (let me
know if you want to do this - I have such a SourceBindingProvider).
You can open a customer support case / enhancement request for this feature. Ask
them to link your case to
|
| Post Reply
|
|
|
|
|
|
|
|
|
|