Currently my database connection on my development box and my production box is the same. All is fine.
I need to deploy a QA site on the same production box (same database server).
Question:
When I get ready to deploy all of my applications to the QA site, do I have to use the Tools>Express Edit tool to rename the db connection in all of the applications to a different db Connection than used on the Production site?
Ed
No, just deploy your application. Then when you startup your deployed application the first time a window will popup reqesting you to logon to your admin panel to change your admin password and (next) to setup your connection data.
Thanks Albert,
The issue came up when I deployed my QA site in a subfolder of my Production site. The ‘Production Environment’ form was run for the QA site. I used a MySQL connection with the same name as the connection in my Development and in the Production environment. However, I did change the database to point to the QA database.
In my mind the Production and QA sites were now using their own separate database, but the Production site started placing data in the QA database.
I then began to think that a database connection is not isolated to the parent folder of the deployment, but instead common the the database and all application deployments on the same server.
In the windows world this would be like an ODBC connection can be used by any application.
My Production and QA environments are on a Linux machine, so I’m not familiar with where data connections are maintained. If indeed, the database connections created are shared between all scripcase applications on a single computing environment, then it seems that I need to change the database connection in development before I deploy to QA so I can keep the database operations in their correct database.
Does this make since? Any thoughts or knowledge of the production database connections scope would be great to hear.
Ed
I just remembered another ‘unexpected’ behavior when I used the ‘Production Environment’ configuration form.
I accessed the Production Environment configuration form from QA URL and set the database to the QA database, then I accessed the Production Environment configuration form from my Production URL and saw that the production database was now pointing to the qa database.
So I just saw the message that the data connection is cached so be sure to close the browser when making changes. This could be the root of my issues. I will test some more and report.
Ed
I installed simple PlugIn for Firefox that does the CACHE clean up. In some cases it helps. You can also try to use my BAT sctipr (see other post) to cleanup your emp folder. Those are probably 2 steps you always want to take when running into problems