Upgrading the resources of the combined Content Deployer
Perform this task if you currently have a single, combined Content Deployer. If you are running two separate Content Deployer services (endpoint and worker), skip this task.
Procedure
- If the server on which this microservice is installed is a Windows machine, uninstall the Windows service by doing the following:
- On the server, open a Powershell command prompt.
- Access the bin\ subfolder of the microservice root folder.
- Run the script called uninstallService.ps1, with an environmental parameter
emscustomeridset to the customer ID you received from RWS Customer Support.
- On the server on which this microservice is installed, navigate to the configuration location of the microservice.
- Back up the contents of this folder to a safe location.
- Back up any custom microservice extensions you have created, along with their configuration files, to a safe location.
- If you have the Context Expression Extension to the Content Deployer installed, remove it. This extension is discontinued as from Tridion Sites 9.6.
- Delete all files and subfolders from the microservice location.
- On your Tridion Sites 9.6 installation media, navigate to the folder Content Delivery\roles\.
- Depending on the type of Content Deployer upgrade you want to perform, navigate to one of the following:
- The deployer\deployer-combined\ subfolder
- The deployer\deployer-sites-combined\ subfolder
- The deployer\deployer-dx-combined\ subfolder
- Navigate to the standalone\ subfolder.
- Copy the contents of the installation media folder, including subfolders, to your installed microservice location.
- If you are upgrading from SDL Web 8.5, delete the backed-up configuration file smarttarget_conf.xml, if present.
- Open the file deployer-conf.xml, which you just copied from the installation media, for editing.
- From your backed-up deployer-conf.xml file, copy over the State Store database connection information to this new file.
- Save and close deployer-conf.xml.
- If you are using the
auto-registerswitch (true by default), make sure you have configured the Capability URL of the service before starting the service. - For each of your remaining configuration files, do one of the following:
- If you have previously made changes to the file that you backed up, compare your backed-up version to the new version you just copied to the configuration location of the microservice, and merge your old file into the new file.
- Alternatively, if you have not changed your backed-up file, ignore it and use the new file instead.
- Save and close deployer-conf.xml.
- Restore any backed-up custom microservice extensions, along with their backed-up configuration files, to your microservice.