Step 9: Analyze the Changes for a Skip-Level Upgrade

You must analyze the changes made by the Waveset product upgrade.

As you iteratively upgrade your Development environment, you iteratively update the baseline for your Waveset application, including the following:

• Configuration objects

• JSP files

• Waveset product JARs

• Third-party JARs

Your baseline must also include SQL scripts to create or update database tables and a subset of update.xml to update repository objects that are not included in your baseline.

Each iteration that includes a sample database table upgrade script requires changes to your overall upgrade procedure. You can run the database table upgrade scripts in the correct order or concatenate the scripts, but you must modify each sample script appropriately for your environment.

You might find that it is more convenient, more efficient, and ultimately safer to write a single database table upgrade script that is cumulative. In other words, write a single script that combines all of the processing that would have been done by each of the individual database table upgrade scripts if you executed those scripts in the proper order.

Executing a single database upgrade script simplifies the upgrade procedure and gives you the opportunity of eliminating redundant processing, such as creating indexes for one version of Waveset and then later dropping and re-creating the same indexes for another version of Waveset.

You can also identify an appropriate subset of the Waveset update.xml in each iteration that is required to update objects in the Waveset repository that are not managed as part of the baseline. For a skip-level upgrade, you must ensure that this subset of the Waveset update.xml is cumulative.

If you are developing a skip-level upgrade, you must be sure to add any configuration objects that were changed by an updater to your Waveset baseline.

An updater is a program supplied with Waveset that updates configuration objects. The updater is invoked by an ImportCommand within update.xml or within a file that update.xml includes. An updater generally works only with the version of Waveset with which it was shipped. Because you are writing a “skip-level” upgrade, the updater probably will not work with the target version of Waveset. Adding any changed configuration object to your baseline is by far the safest approach.