Upgrading Contenta Server
To upgrade Contenta Server, run the installer and perform a number of verification tasks.
- Running the installer
Run the installer to upgrade Contenta Server. After your upgrade is complete, you must reboot your machine. - Upgrading Contenta client workstations and the Contenta database
Use the SDL Contenta Client Upgrade Guide for Windows to upgrade at least one Contenta client with Contenta Administration tools. Doing so ensures that you upgrade the existing Contenta database(s) and enables you to verify that Contenta has been upgraded successfully. - Preventing password expiration for Oracle databases
Oracle passwords expire by default. This can result in Contenta system failures due to the expiration of the sys, system and xyadmin passwords. - Verifying Oracle character set definitions
Run an SQL command and check the registry to very that the Oracle character set definitions are set correctly and consistently. - Verifying and updating paths in the PATH variable
In yourPATHenvironment variable, ensure that your path to Perl is located at the beginning of the list of paths. Also, remove any MKS paths from the variable, unless you want to use MKS with other programs. - Removing FlexLM
Only if you are upgrading from a Contenta version earlier than 4.2, remove the FlexLM software, registry entries, and license, unless you use FlexLM for XPP or other programs. - Changing the PcmPortal version
By default, the upgrade installs one version of PcmPortal (OCI or ODBC) as the default PcmPortal executable, based on the database type and version you selected, and the other version as a non-default executable. If you upgrade or change your database, rename the executables to change which PcmPortal is used. - Upgrading customized files
To prevent the upgrade from overwriting files you may have customized in the working directories, the installer places all new versions of customizable files in the distr subdirectory of your Contenta home directory. Merge these new files with your customized files.