Upgrading from version 3.3.x to 3.4.16
Please completely read these instructions BEFORE beginning your upgrade process.
Backup
SQL Database Users
Using the appropriate utility for your RDBMS, create a backup of your SQL Database.
Instructions for Default Windows Installations
If you used the Connect Daily downloader, then you should follow these steps to upgrade. If you are using a different engine, or OS, then skip to the "Generic Application Server Instructions".
- Stop the Connect Daily service.
- Run the Connect Daily Downloader and install the new version of Connect Daily. This will leave the old version intact.
- Stop the Connect Daily service.
- Copy any customized header/footer html files, as well as any modified CSS files from the old cdaily-x.x.x directory to the cdaily-3.4.16 directory.
- Start the Connect Daily Service.
- Database scripts will automatically be run. You do not have to do anything for Database Updates.
Generic Application Service Upgrade Steps
- Stop your application server.
- Backup your cdaily-3.4.16/WEB-INF/configuration.properties file.
- Backup any custom EMail templates or caption translation files you have created.
- Remove the existing calendar application directory.
- Extract the zip or WAR file containing Connect Daily into the appropriate directory for your application server.
- Copy the configuration.properties file you saved in step 2 to the WEB-INF directory. If you are using MS Access, copy the calendar.mdb file you saved prior to beginning into the WEB-INF\SQL\Access directory.
- Follow the instructions in the Database Updates section below.
- If you copied your database JDBC driver JARs into the WEB-INF/lib directory, recopy them to the WEB-INF/lib.
- If you are using your own translated caption files, refer to the Installation Guide and User manual for instructions on how to ensure you have all captions in your file.
- Restart your application server.
Database Updates
SQL Database Users
- Write down your current program version.
- BACKUP YOUR DATABASE BEFORE PERFORMING THESE STEPS
- JNDI USERS:
Edit your configuration.properties file. For the upgrade script to run, you must create a configuration.properties file that uses a standard JDBC Connect String. This is because the upgrade script will not have access to JNDI variables when it runs. For information on editing configuration.properties, refer to configuration.properties. - Run the db upgrade scripts in the WEB-INF/sql directory. If your current version <
Your Version < 3.1.x - run310.bat or .sh
Your Version < 3.2.x - run320.bat or .sh
Your Version < 3.3.x - run330.bat or .sh
Your Version < 3.4.x - run340.bat or .sh
You must run each required script in order.