Documentation Center

Upgrading the resouces of the Content Deployer worker

The Content Deployer worker is a microservice that processes content received by the endpoint.

Procedure

  1. If the server on which this microservice is installed is a Windows machine, uninstall the Windows service by doing the following:
    1. On the server, open a Powershell command prompt.
    2. Access the bin\ subfolder of the microservice root folder.
    3. Run the script called uninstallService.ps1. (If you are running the service on a different default HTTP port than the default, add a server.port parameter and set it to your custom port number.)
  2. On the server on which the Content Deployer endpoint microservice is installed, navigate to the configuration location of the microservice.
  3. Back up the contents of this folder to a safe location.
  4. Back up any custom microservice extensions you have created to a safe location.
  5. 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.
  6. On your SDL Tridion Sites 9.5 installation media, navigate to the folder Content Delivery\roles\.
  7. Depending on the type of Content Deployer upgrade you want to perform, navigate to one of the following:
    • The deployer\deployer-worker\ subfolder
    • The deployer\deployer-sites-worker\ subfolder
    • The deployer\deployer-dx-worker\ subfolder
  8. Navigate to the standalone\ subfolder.
  9. Copy the contents of the installation media folder, including subfolders, to your installed microservice location.
  10. If you are upgrading from SDL Web 8.5, delete the backed-up configuration file smarttarget_conf.xml, if present.
  11. Open the file deployer-conf.xml, which you just copied from the installation media, for editing.
  12. From your backed-up deployer-conf.xml file, copy over the State Store database connection information to this new file.
  13. Save and close deployer-conf.xml.
  14. If you are using the auto-register switch (true by default), make sure you have configured the Capability URL of the service before starting the service.
  15. 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.
  16. Save and close deployer-conf.xml.
  17. Restore any backed-up custom microservice extensions to your microservice.