Application Server Restricting DB Access [message #594625] |
Sat, 31 August 2013 05:58 |
|
Bobdemac
Messages: 1 Registered: August 2013 Location: U.K
|
Junior Member |
|
|
Hi, Im looking for some advice on Oracle App server.
I have recently joined a company that has an Oracle Forms App running against a 10g Database.
They have one application server, this is used for both Production and testing.
The default.env file is used for config of the production application but they have different .env files that they use for testing environments e.g. UAT.ENV.
When they are testing code at the app authentication screen they can enter which database they connect to production, dev, UAT etc regardless of whether they are running production code or test code e.g. UAT.
Obviously this is not a good situation.
Is there anything that can be done to restrict which databases can be connected to as part of the application server configuration for a given env e.g. UAT.ENV can only connect to UAT DB and DEFAULT.ENV can only connect to production DB.
|
|
|