Upgrade WorkZone Content Server
If you want to install WorkZone Content Server on a server where an earlier release of WorkZone Content Server is already installed, you must uninstall the earlier version before starting the installation of the new release. Earlier versions may contain customer specific adaptations, which have overwritten standard files.
When you have uninstalled the earlier release, check the following:
- The web server
- WorkZone Content Server components
- The database configuration and ODBC
- Windows registry containing WorkZone Content Server components, Oracle and ODBC.
Upgrade WorkZone Content Server
The procedure of upgrading a version of WorkZone Content Server is identical to the installation procedure described in About installing WorkZone Content Server and Configure WorkZone Content Server
Important: If you upgrade your WorkZone Content Server 2021.0 or WorkZone Content Server 2021.1 installation to WorkZone Content Server 2024.0, the meta data for the File, Record, Contact, and Address tables must be reindexed. Reindexing the meta data for the Document table is not necessary.
WorkZone Client configurations after upgrade
In some specific upgrade scenarios, you must perform additional upgrade tasks to ensure that WorkZone Client configurations work as expected after the upgrade. This applies to WorkZone 2022.3, 2023.0, and 2023.1. All other upgrade scenarios are not affected.
Upgrade to 2022.3 and 2023.0
Complete the following steps:
-
Save WorkZone Client configurations and create a back-up. For information about configurations, see About WorkZone Client configurations.
-
Upgrade WorkZone Content Server.
-
Run the script named
skey2guid.sql
on the server where WorkZone is installed. The script converts search_key to guid. See the readme for instructions on how to run the script. Contact WorkZone Support to get the script. -
Import configurations in to WorkZone Client.
If you have upgraded to 2022.3 and 2023.0
-
Run the
skey2guid.sql
script on the server where WorkZone is installed.
If you have changed configurations after the upgrade.
-
Save the configurations and make a backup.
-
Run the
skey2guid.sql
script on the server where WorkZone is installed. -
Run the
run_wz_configuration.bat
file that removes duplicate GUIDs. See the readme for instructions on how to run the script. Contact WorkZone Support to get the script.
Upgrade from 2022.3 and 2023.0 to 2023.1
The skey2guid.sql
script is part of the 2023.1 installation. You do not need to run it.
If you have changed configurations after the upgrade, you need to run the run_wz_configuration.bat
file that removes duplicate GUIDs. See the readme for instructions on how to run the script. Contact WorkZone Support to get the script.