Upgrading Synchronize

The installation procedure will never modify or damage the contents of your existing database. In addition, it attempts to modify or replace as few files as possible that may have been previously changed by the Synchronize administrator. For example, the Synchronize client start-up script (bin/synchronize.sh) is almost never replaced and the resources directory is replaced (and the existing directory renamed to resources.old) only when absolutely necessary. As a result, you should not hesitate to extract and install new releases of Synchronize on top of existing ones, when such installation is warranted. In all cases, the directory containing the platform specific binaries (e.g., solaris, rs6000, etc.) for which you are installing will be renamed with a .old suffix and a new directory will be created for the new release.

The following are the basic steps you should take when upgrading Synchronize to a new version or when adding software for a new platform to an existing installation:

1. If you are updating a directory containing the server and database component, stop the Synchronize server operating on that database before beginning the update.
2. Extract the software from the media provided into your existing Synchronize directory. Newly extracted directories will have a .new suffix to distinguish them from your existing release.
3. Run the installation program just as when installing a new release.
4. Restart the Synchronize server if you stopped it in step 1.

After the upgrade is complete, the following files will have been added/updated in your hierarchy and represent the distributed versions of the files with the same name (minus the .dist suffix).

bin/synchronize.sh.dist
bin/synchrod.sh.dist
db/database/tztab.dist
db/database/client.opts.dist
db/database/macprefs.dist
db/database/server/server.opts.dist
db/database/server/router.opts.dist

The files listed above may be periodically updated by CrossWind with fixes or new configuration options.