This document is meant to be a guide for migration and testing now that a snapshot of the RM databases has been captured and installed on mysql-node01, which has MySQL server 5.5.
Is it possible to make alternate cgi scripts which use as host mysql-node01 rather than glastDB? If so, we can test all functionality without any impact on production pages.
I think I found the location of the scripts which actually get called. It's highly protected, but copies of the files are available elsewhere for browsing. If I understand correctly, the production files also ultimately use the information in DBConf to connect, but it doesn't look too hard to make slightly-modified versions with different names which would use an alternate DBConf, pointing to mysql-node1 (and no doubt easier still for someone with experience with cgi scripts). We'd probably need help from unix-admin to install the modified scripts in the official location.
The CMT RM Perl scripts uses the MySQL client library indirectly via the Perl module PBI, and the MySQL driver DBD::mysql. On Linux everything we require is already installed and on rhel5 or rhel6 machines will be using MySQL 5.0 or newer client library. On Windows we're currently using a MySQL 4.1.22 client which at some point will need to be upgraded, but not urgently (should still work with the newer server).
~glastrm/mysql-proxy might be relevant.
Just a proposal; by no means the final word!
http://search.cpan.org/~capttofu/DBD-mysql-3.0002/lib/DBD/mysql.pm
The following are all mentioned in the crontab table and can be found in ~glast/infraCron:
batchSub.pl
cleanSessions.pl
createLastest.pl
logClean.pl
rmTodo.pl
workflow.pl
The same directory contains the script cron.pl