Configuring Contenta Client
Complete the configuration tasks before you execute the newly installed Contenta Explorer software.
About this task
After you install SDL Contenta, you must complete the installation by either modifying your site’s existing files, or moving or renaming the upgrade-delivered files to the appropriate folders.
Procedure
- Compare Contenta_home\encaps\di\custom\utils.pm to the upgrade-delivered file Contenta_home\encaps\di\utils.pm.
- Edit the Contenta_home\encaps\di\custom\utils.pm file, if necessary, to include changes delivered by the upgrade.
- Delete or rename Contenta_home\encaps\di\utils.pm.
- Compare the Contenta_home\encaps\di\custom\CustomCallbacks.pm file to the upgrade-delivered file Contenta_home\encaps\di\CustomCallbacks.pm.
- Edit the Contenta_home\encaps\di\custom\CustomCallbacks.pm file if necessary to include changes delivered by the upgrade.
- Delete or rename Contenta_home\encaps\di\CustomCallbacks.pm.
- If upgrading from pre-Contenta 5.3 and you will be using the EnableDefaultUserName AppData setting to prevent the default username from being displayed in the Contenta Explorer (and Contenta Web) login screen. Remove two keys from the Windows registry:
HKEY_CURRENT_USER/Software/XyEnterprise/Content@/Settings/Startup/Username
HKEY_LOCAL_MACHINE/Software/XyEnterprise/Content@/Settings/Startup/Username
For information on how to implement this optional security feature, see the Application preferences in AppData topic in the Installing or Upgrading SDL Contenta Web for Windows and UNIX Systems section of this documentation.
- If your site uses Microsoft SQL Server, set the MSSQL_HOME system environment variable on the client machine to the full path to the MS SQL Server installation, such as C:\Program Files (x86)\Microsoft SQL Server\Client SDK\ODBC4.
Important: This environment variable is used to resolve SQLCMD.EXE pathing and must be set before running the database maintenance scripts on the client machine.
- Core SDL Contenta only (sites not using SDL Contenta S1000D).
- Rename the Contenta_home\encaps\di\digui.cfg file to save any customization or changes made before generating the file in the next step.
- In the Contenta Explorer application, execute Dynamic Import to generate a new digui.cfg file.
Note: When you execute Dynamic Import the first time, and before completing this step, the tool displays the message A distribution config has been found.... Click OK to continue.
- Compare the newly generated Contenta_home\encaps\di\digui.cfg file to your site’s previous (custom) digui.cfg file—this is the one that you renamed (above).
If necessary, edit your site’s custom file to include any updates included in the delivered Contenta_home\encaps\di\digui.cfg file and rename it to digui.cfg.
- Verify that paths and applications for viewxml and viewsgml tools are correct for your site and configuration.
- After you install and configure Contenta Client, see the SDL Contenta Editor tools user section of the Contenta documentation for additional information about configuring and using the editor software.
Note: If you install or upgrade Arbortext Editor, FrameMaker, or XMetaL software on a Contenta client after upgrading Contenta software, you will need to (re)configure the editor to work with Contenta. See the SDL Installing Contenta Client on Windows topic in this documentation for instructions. The Installing Third-Party Editor Software topic includes a section Configuring Editor Software that is Installed after Contenta is Installed.Note: Before you import data with Dynamic Import for use with Arbortext Editor, you must check the AppData value that is set in Contenta_home/Encaps/di/digui.cfg. See the Using Contenta Editor Tools section of this documentation for a description of this change.
- Testing the SDL Contenta Software
After completing both the Contenta Server and Contenta Client upgrades, follow these steps to ensure your installation is working properly.