I've always used the same DSN specs for my development and deployment
datasources, but I'm looking for flexibility so I would like to ask
the list about best practices for this.
Here's what I'm thinking of doing for my database actions:
1. establish variables (in a persistent scope) to define the TYPE
(eg. ODBC), DSN, DB, USER, PASSWORD. These would be initialized at
application startup.
2. use these variables in all Action Properties :: Deployment Logon
window (ie., uncheck 'Same as development'). I notice that witango
studio encrypts the UserInfo stanza of the DataSource within the xml,
but this seems to be properly handled at execution time. Is there
anything else I should do in witango?
Regarding database security, I've been using both host and user
access control within mySQL (ie, the client must be from an
acceptable IP address, such as localhost, and the username and
password are then specific to a particular database). And of course
the firewall blocks port 3306 (mysql) except from known acceptable
addresses. Is there anything else that people do?
Are there any tricks that people use in managing access to their
databases?
thx.
Bill
William M. Conlon, P.E., Ph.D.
To the Point
345 California Avenue Suite 2
Palo Alto, CA 94306
vox: 650.327.2175 (direct)
fax: 650.329.8335
mobile: 650.906.9929
e-mail: mailto:[EMAIL PROTECTED]
web: http://www.tothept.com
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
