Resolution: Won't Fix
"...start with the name of the database schema..."
- What is when the database schema change, for migration, for upgrade, for different customers ?!
- Should this not be a symbolic name like the alias in tnsnames.ora ?!
- Maybe only the DBA/Admin knows which database schema is used.
- What is with proxy user schema's (database user only with DML access)
We use the codename of the project for the database connection name without any pre- or postfix.
codename := sapp
So the main database connection is: sapp
Is any module of the solution different database connection, so the name is the module: contact
So we end up with two database connection pools in wls with the names:
Only the WLS Admin / DBA knows which database schema is used.
Different customers will be served on different wls managed servers.
But with the same convention, so it is very easy to clone the env.
Only the WLS Admin / DBA knows which database schema is used !
with king regards,