Contenta server upgrade pre-installation activities
Procedure
- Read the Release Notes to determine if, and how, a release may affect your site before you upgrade your Contenta software.
Release Notes are the most up-to-date source of information. They provide release-specific information and are updated with current information for each maintenance and patch release that modifies or enhances the software on your system.
- Read the SDL Contenta Server Platform Requirements document to verify that you meet the system hardware and software requirements for the release.
If the supported versions and patch levels are not installed, you must upgrade them before doing the Contenta software upgrade.
- Back up your database and systems before upgrading.
SDL recommends that you back up your database and systems before you upgrade the Contenta software. Perform the backup in single-user mode—that is, when the Contenta database is not in use.
- Back up your database and systems before upgrading.
- Stop or kill the following Contenta processes if they are running:
Process Procedure PcmPortalPcmPortalNote: Take note of thePcmPortalPID (process number).kill -9 <PID_num>Note: Where <PID_num> is thePcmPortalPID (noted above)../rlm cd /opt/XyEnterprise/SDL_License ./rlmdown RLM -qNote: This Reprise License Manager process will be running if you are upgrading from Contenta 4.2 or higher. - Copy and save all Contenta-related custom files—files that you have modified or customized for your site.
For example, if you have modified or customized any of the following files, make a copy of them and move the copy to a directory location that is not under the $XYV_PDM_ROOT directory before you upgrade:
- $XYV_PDM_ROOT/clients/clientapi/orb/config/pcmcfg
- $XYV_PDM_ROOT/encaps/di/digui.cfg
- $XYV_PDM_ROOT/setup/pdm_setup.sql
Copy and save the $XYV_PDM_ROOT/setup/pdm_setup.sql file to preserve your database storage customizations. This file is overwritten when you upgrade your system—it is not copied to the $XYV_PDM_ROOT/distr directory but instead, it is placed directly in the $XYV_PDM_ROOT/setup directory, thereby overwriting the current one in the directory.
The upgrade writes new versions of the files that can be, and may have been, customized to the
$XYV_PDM_ROOT/distrdirectory. After the upgrade, you must reconcile the differences between any new versions of the customizable files and your custom versions of the same files. After you have accounted for differences and modified your custom files, copy them to the appropriate directory. - Upgrading to Contenta 5.5 requires a new license file. See Requesting the Contenta License File. Be sure to request the
PCMWEBtoken in the license file.
Results
Only after you have completed all the previous steps are you ready to upgrade the Contenta Server software and your Contenta database(s). See the Upgrading Contenta Server topic for a description of the upgrade procedure for your Contenta server.
After upgrading the Contenta Server and database(s), upgrade the Contenta Client workstations. See Upgrading Contenta Clients on Windows for the Contenta client upgrade procedure.
- Oracle database
If you plan to use dbimport.pl to create your database instance, before importing the Oracle .dmp file, the Oracle database administrator must setdeferred_segment_creation=falseto ensure that any empty tables in the.dmpfile are imported. - Requesting the Contenta license file
The license manager may require that you obtain a new license file from SDL. - Required upgrade information
Certain environment variables must be set in the pdm.cshrc and pdm.cshrc.ora files to properly upgrade and configure the Contenta server. Obtain the following information before beginning the Contenta Server upgrade.