Post-upgrade tasks
Perform the following tasks to complete your Contenta Server software upgrade.
Procedure
- Log in as the root user.
- Check the $XYV_PDM_ROOT/distr/... directories to identify if new files have been delivered.
The Contenta installation delivers new versions of customizable files to the $XYV_PDM_ROOT/distr/ directories to preserve files, which you may have customized and which are located in the working directories. This ensures that custom files are not overwritten during the upgrade installation.
- Reconcile the differences between the newly delivered files and the custom files for your site. Either update the old, existing file, or if you have not customized the file, move the new file to its destination directory. In particular:
- Upgrades from Contenta 4.n: Be sure to compare the new pdm.cshrc file with the one in $XYV_PDM_ROOT/bin and reconcile differences then move the new file into $XYV_PDM_ROOT/bin.
- Verify that
LD_LIBRARY_PATHenvironment variables are defined to include the following.{$XYV_PDM_ROOT}/system
- It may be required that the
HOSTNAMEvariable be defined as a fully DNS-qualified host name if that is how it is specified for your network.Check the line in the pdm.cshrc file that defines the HOSTNAME variable. To do this, find the line that reads: setenv HOSTNAME hostname. Change hostname to the server name. For example, if the server name is phoenix.sdl then the line should read: setenv HOSTNAME phoenix.sdl.
- Verify that pdm.cshrc (Oracle systems) contains the following in the path variable: $XYV_PDM_ROOT/system.
- Compare the CustomCallbacks.pm and utils.pm files in the $XYV_PDM_ROOT/encaps/di/distr directory with the files in the $XYV_PDM_ROOT/encaps/di/custom directory. If the files differ, make appropriate changes (incorporate customizations in the files in the ...di/custom directory with changes in the delivered files in the ...di/distr directory) and save them to the $XYV_PDM_ROOT/encaps/di/custom directory.
If you did not customize the CustomCallbacks.pm and utils.pm files in a previous version of the software, copy the delivered CustomCallbacks.pm and utils.pm files in the ...di/distr directory to the ...di/custom directory.
- If the License Server resides on a different machine, uncomment the setenv line that sets the
sdlxysoft_LICENSEvariable in the pdm.cshrc file and specify the node-name of the license server.Important: If you want to spread search services over multiple servers, you can run the Contenta Server installer on each server and install only the ‘PCM Solr’ option. You then need to update the entries in unixuser.dat using fileregedit, which serves as a registry for Contenta Server and some Contenta tools on Linux. For more information on usage on fileregedit, see the SDL Contenta Administration User Guide.If the Contenta Server is configured for ODBC, then instead of a SID you must specify the ODBC DNS Name.
You do not have to install the License Manager.
- If using accented characters, see Defining Oracle Character Sets.
- Modify the S99contenta startup script as needed for your site and copy it to the startup directory. See Startup Scripts.
- Reboot.
Rebooting will automatically execute the S99contenta startup script if it is in place, and start the Reprise license manager if it is on the same machine.
- Confirm the success of the upgrade by following the steps in Verifying the Contenta Upgrade.