Upgrading the resources of the combined Content Deployer
The combined Content Deployer is a single microservice that both receives and processes incoming content.
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. (If you are running the service on a different default HTTP port than the default, add a
server.portparameter and set it to your custom port number.)
- 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 to a safe location.
- Delete all files and subfolders from the microservice location or, if you are upgrading from SDL Web 8.5 and your microservice ran as a web application, from the web application location.
- On your SDL Tridion Sites 9.5 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 folllowing:
- 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 to your microservice.