ADF BC: Choosing between two identical DB schemas on application startup

Question

Hi,
We want to provide users with capability to choose between two identical db schema.
Anu idea how to do this ?

Answer 1

Cvele wrote:
Thanks a lot ! My pleasure.
One question: datasource name entered by the user (on the login form) is a JDBCDataSource property value for the Application module Configuration (which connect trough JDBC DataSource), correct ?Yes.
If so, then, we still must define two different sets of App Module Configurations, one for each DB schema, correct ?No. I'm not suggesting that you implement your UI like the demo that I forwarded. It might not be appropriate for your user to type in the datasource name, but the same code would be required to make the datasource name change work. Rather than getting the datasource name from the HTTPRequest and setting on the session where the custom sesison cookie impl and env info provider access you, for your solution that datasource value might come from some other place that the end-user doesn't directly type in.
Otherwise:
1. we cannot have two different datasource names, correct ?The example I forwarded should allow you to enter different JNDI names, so those would be different datasources.
2. in case of one Configuration – what is a way to define (at deployment time) username/password for each of those two schemas ? Is this correct ?The username/password information is encapsulated inside the Java EE container when you define the datasource. The application doesn't know that information and doesn't have to provide it when you are using a JDBC datasource by JNDI name.
On the other hand, what confuses me, is a fact that you say:
“You wouldn't use different configurations” And really, you example attached to me have just one App module Configuration (datasource name = jdbc/scottDS), which connect through dataSource.
Wondering what a user can enter as datasource name, except jdbc/scottDS ?I forget whether in my example I configured another datasource, but the user could enter the name of any available JNDI name for the datasource on the Java EE container.
Again, I don't suggest necessarily that you let the end-user type it in, that was just how I built the demo since I quickly evolved it from the other dynamic credentials demo that accepted the username and password from the end-user.