Installing the Content Deployer worker in an upgrade scenario
If you have chosen to upgrade to a setup in which the Content Deployer worker runs separately from the Content Deployer endpoint, install the worker separately, as a standalone microservice.
- Copying resources for the Content Deployer worker
Copy microservice resources to your target machine. - Setting a log location for your microservice
By default, Content Delivery microservices write their log files to a folder called c:/SDLWeb/log/. Set a proper location in the Logback configuration file for your microservice, logback.xml. - Installing a license for your Content Delivery Role
Your Role will not function without a valid license file. - Restoring backed-up resources from your SDL Web 8 Content Deployer microservice
Apply your previous customizations to the Content Deployer worker by restoring your backup. - Installing the Content Deployer worker as a standalone microservice
Run the appropriate microservice installation PowerShell or Unix script to install and run the 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). - Restoring backed-up resources from your existing Content Deployer (HTTP or HTTPS) or HTTP Upload role to the Content Deployer worker
Apply your customizations to the Content Deployer worker by restoring your backup. - Configuring a non-HTTP(S) transport protocol
As of SDL Web 8, any transport protocol other than HTTP or HTTPS is deprecated. Using a mix of legacy transport and HTTP(S) transport is discouraged. If you use a deprecated transport protocol, you can only publish to local file system or to binary storage, and you cannot use a Redis database for temporary storage. If, despite these drawbacks, you still wish to continue using a deprecated transport protocol, edit the Content Deployer configuration file, cd_deployer_conf.xml .