Upgrade Process Overview

Overview and procedural information involved in upgrading Document Generation Services.

This section explains how to upgrade specific components used within Document Generation Services (DGS).

Note: This section is intended for those users who have previously installed DGS. Note also that this upgrade procedure assumes you have installed RabbitMQ and ERLang during the initial installation; no upgrade is necessary at this time. If you need to reinstall RabbitMQ and ERLang, see the following section in the installation guide: Installing and Configuring RabbitMQ Services

Overview

Users should perform the following steps to successfully upgrade DGS and specific components:

Before You Begin

Before beginning the upgrade process, uninstall the following components:
  • STSv3
  • Document Generation Services
    Note: It is recommended that you stop WildFly prior to uninstalling Document Generation Services for a cleaner installation; you will need to reboot the Windows server to complete the uninstallation.
  • EZ Config Packages and Packets
  • RabbitMQ
  • ERLang
  • Uninstall the following components:
  • Run the RunExclusionAdding.ps1 script to exclude eSignature functionality from packages and documents by adding an empty esignature.xml file at the root organization. WIth this exclusion list, users can enable esignature capability for a unique set of documents. This script is located in the Scripts folder on the release media.
    Note: This script should only be run on the DGSManagement machine where the ExpereRepository folder is located using Powershell 4.0.
  • Previously, Expere created hashes of the content items during runtime in order to determine how and when items would be retrieved from the cache. With this update, all of the content items are pre-hashed so that Expere does not need to do it at runtime.
  • If you are working with existing deployed libraries, running this process is required to alleviate any errors when calling DGS API’s.
    1. Locate the Resources folder on the release media, copy the ManifestCreator.zip file containing the ManifestCreator.exe.config and ManifestCreator.exe files to the machine where the repository(ies) exist.
    2. Set the location of the file system repository in the ManifestCreator.exe.config by specifying the content repository path for the RootFolder setting.
    3. Run the ManifestCreator.exe file

Related Links

Access the following links for more information: