To update existing database schema for 4.2.0

As explained below, apply the appropriate version(s) of update.sql, and then update the user-salts.

Update.sql

If you are currently using demo data that you set up under Scheduler v3.1.1, and you want to continue using your current data, apply the following list of update.sql files:

  1. update.sql (3.2.0)

  2. update.sql (3.3.0)

  3. update.sql (3.5.0)

  4. update.sql (3.6.0)

  5. update.sql (3.7.2)

  6. update.sql (4.2.0)

To apply each update.sql, install all the distributed update.sql files to the folder /var/tmp/. Then run the following command for each update.sql in the order provided:

root@shell> mysql scheduler < /var/tmp/update.sql

root@shell> mysql scheduler < /var/tmp/update.sql

If you are updating from Scheduler v3.7.2 then apply only the latest (4.2.0) update.sql from the above list and then run the Update User Salt program below.

Update User Salt

Configure and run the standalone: updateUserSalt, to convert DB user salt fields to new MIME flavored salts

  • Erratum for its README: Adjust update-user-salt.properties to match the encryption properties from scheduler.properties and the DB Resource xml-stanza from context.xml

  • However, use a shorter version than does tomcat: 


To install demo data for use with Scheduler 4.2.0

Run the following SQL scripts:

demo-structure.sql

This file contains the basic database schema and table structure for the Scheduler application.  There is no data in this file and it must be used in conjunction with seed data in order to have a running application. The structure is based on Scheduler v4.1.0.

  • Install the distributed demo-structure.sql file to /var/tmp/demo-structure.sql

demo-seed.sql

This file contains all the static data required by the application (e.g dropdown options, list of users, states, countries, etc). 

Note: This is enough to start the application. Anything beyond this can be optional.

  • Install the distributed demo-seed.sql file to /var/tmp/demo-seed.sql

root@shell> mysql scheduler < /var/tmp/demo-data.sql
root@shell> mysql scheduler < /var/tmp/demo-seed.sql

demo-data.sql

This file contains a set of data for demonstration purposes. This includes demo templates, scheduled appointments, and more.  Upon running this script (along with the populate-fake-subjects executable, and update.sql that follow) you should have all the data that you need to evaluate the application.

Note: If demo-data.sql is executed it is necessary to run the populate-fake-subjects program.

  • Install the distributed demo-data.sql file to /var/tmp/demo-data.sql 

root@shell> mysql scheduler < /var/tmp/demo-data.sql

populate-fake-subjects

This program creates demo subjects data. README.txt in the program is out of date, please refer to the instructions below on how to run the program.

1. Adjust conf/fake-subjects.properties to match the encryption properties from scheduler.properties and the DB Resource xml-stanza from context.xml

2. For our 'demo data', the max-subject-id is 47

3. Then, to insert demo subjects run the following:

a. UNIX
chmod +x fakeSubjects.sh
./fakeSubjects.sh <max-subject-id>

b. Windows
fakeSubjects.cmd <max-subject-id>

update.sql

Finally, apply update.sql, and you will be all set.

To apply update.sql, install distributed update.sql file to the folder /var/tmp/update.sql. Then run the following command:

root@shell> mysql scheduler < /var/tmp/update.sql
  • No labels