Home » Other » General » PL/SQL Store Application Configuration (Oracle 11g, Linux)
PL/SQL Store Application Configuration [message #619465] Tue, 22 July 2014 14:51 Go to next message
msashi
Messages: 3
Registered: July 2014
Location: United States
Junior Member
What is the best practice to store application configuration values. Like for example I have a PL/SQL package that posts XML over HTTP. For that I need to store the URL, authentication user name, password etc. Right now I have these hardcoded in the package header. I am looking at either setup a table or store it in a text file on the server and read using UTL_FILE. What do you guys suggest?

Thanks in advance.
Re: PL/SQL Store Application Configuration [message #619479 is a reply to message #619465] Tue, 22 July 2014 17:07 Go to previous messageGo to next message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
implement a lookup table
Re: PL/SQL Store Application Configuration [message #619586 is a reply to message #619479] Wed, 23 July 2014 10:56 Go to previous messageGo to next message
msashi
Messages: 3
Registered: July 2014
Location: United States
Junior Member
I thought about that. Here is my concern. We refresh the test database with production data every once in a while. I don't want these production URLs and passwords show up in test database and then somebody run the program in the test system and hit production URLS.
Re: PL/SQL Store Application Configuration [message #619590 is a reply to message #619586] Wed, 23 July 2014 12:03 Go to previous messageGo to next message
Michel Cadot
Messages: 68625
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

So change the urls after copying the database.

Re: PL/SQL Store Application Configuration [message #619607 is a reply to message #619590] Wed, 23 July 2014 13:07 Go to previous messageGo to next message
Lalit Kumar B
Messages: 3174
Registered: May 2013
Location: World Wide on the Web
Senior Member
Or, another way is SCRUBBING the test database to have different data than Production.
Re: PL/SQL Store Application Configuration [message #619641 is a reply to message #619586] Wed, 23 July 2014 16:46 Go to previous message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
msashi wrote on Wed, 23 July 2014 08:56
I thought about that. Here is my concern. We refresh the test database with production data every once in a while. I don't want these production URLs and passwords show up in test database and then somebody run the program in the test system and hit production URLS.



Data is static; unless & until somebody changes it.
Data is data; regardless of where it is stored.
So you'll have the same "threat", regardless of where this data resides.
With "intelligent" & idiot-proof networking, the DEV database can't ever get to Production DB Server.
Previous Topic: Object-relational mapping ORM - SQL only for DBA? New developers don't need SQL skills?
Next Topic: Oracle In-Memory Column Store
Goto Forum:
  


Current Time: Thu Mar 28 14:21:30 CDT 2024