Installing the combined Content Deployer
If you install the Content Deployer feature on a single machine, you can install it as a single microservice called the combined Content Deployer. If you want to (be able to) scale out the feature, install the Content Deployer endpoint and Content Deployer worker separately instead.
- Copying resources for the combined Content Deployer
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. - Configuring Content Data Store access for your Content Delivery Role
Roles use the Storage Layer to access the Content Data Store, where all content is stored. To configure content storage in one or more databases, addStorageelements to the file. - Installing a license for your Content Delivery Role
Your Role will not function without a valid license file. - Configuring the combined Content Deployer
Configure where incoming packages should be retrieved from, and a number of queueing and sizing parameters. Also configure the State Store database, if necessary. - Installing the combined Content Deployer as a standalone microservice
Run the appropriate microservice installation PowerShell or Unix script to install and run the standalone microservice. - Securing the microservice with SSL
You may wish to secure your microservice using Secure Socket Layer (SSL), so that an HTTPS connection is required to interact with the service. If you do, you require a certificate signed and issued by a Certificate Authority (CA), a private key, and a keystore containing both of these. You then configure the keystore in the application.properties file of your microservice. You can reuse the same certificate, key and keystore for multiple microservices, so long as they are all running on the same machine. This section assumes that you have no certificate, key or keystore yet. If you do, you can skip the topics that do not apply. - Connecting to an HTTPS-secured Discovery Service
If you secured your Discovery Service with HTTPS, you imported your certificate into a keystore which you passed to the Discovery Service. To connect to the Discovery Service, import the same certificate into your local Java keystore.