Upgrading the SDL Tridion 2013 SP1 HR1 Content Deployer
SDL Web 8.5 offers several upgrade paths for your Content Deployer Role, whether it's the "Content Deployer (HTTP or HTTPS)" Role or the "Content Deployer (other protocols)" Role of SDL Tridion 2013 SP1 HR1.
- Upgrade paths for the SDL Tridion 2013 SP1 HR1 Content Deployer Role
A reorganization of the Content Deployer feature means that you need to make some decisions about how to upgrade your existing Content Deployer setup. - Backing up resources from your SDL Tridion 2013 SP1 HR1 Content Deployer Role
Back up your configuration files and, if applicable, custom JAR files. - Uninstalling the Content Deployer (other protocols) running as a Windows service
To uninstall the Content Deployer (other protocols) Windows service, find and uninstall the corresponding Windows process. - Uninstalling the Content Deployer (other protocols) running as a Java process
If your Content Deployer (other protocols) runs as a Java process, uninstall it by hand. - Upgrading your SDL Tridion 2013 SP1 HR1 Content Deployer to a combined Content Deployer
To upgrade your Content Deployer to a combined Content Deployer, replace it with a standalone combined Content Deployer microservice. If you currently have a Content Deployer (HTTP or HTTPS) Role running as a Java/JSP Web application, you can also turn it into a Java/JSP Web application-based combined Content Deployer microservice, but such an upgrade is actively discouraged. - Upgrading your SDL Tridion 2013 SP1 HR1 Content Deployer to a separated Content Deployer endpoint and Content Deployer worker
To make your Content Deployer implementation scalable, separate the endpoint from the worker (processing engine) by putting each in a separate microservice. If you have your Content Deployer (HTTP or HTTPS) Role currently installed as a Java/JSP Web application, you can replace it with an endpoint running in the Web application (a deprecated setup); alternatively, you can also run it as a standalone microservice. The Content Deployer worker always runs as a standalone microservice. - Configuring the State Store database as part of an upgrade
The Content Deployer upgrade adds a section for the new State Store database to your Content Deployer configuration file, deployer-conf.xml. By default, the State Store is configured to reuse your Content Delivery Broker database. To give the State Store its own database (a recommended setup), reconfigure it in your deployer-conf.xml file(s).