Installing the Content Deployer endpoint
The Content Deployer endpoint is a core Content Delivery Role that must be installed in order for SDL Web to work.
- Copying resources for the Content Deployer endpoint
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. - Configuring the Content Deployer endpoint
Configure where incoming packages should be retrieved from, and a number of queuing and sizing parameters. - Installing the Content Deployer endpoint 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. - Registering the Content Deployer microservice as a Capability
If you already used theauto-registerswitch to register this Server Role as a Capability when you installed it as a standalone microservice, you can skip this task. If you did not, you can make this microservice discoverable through the Discovery Endpoint by hand by adding it as a Capability to the Discovery Service's Storage Layer configuration file and update the Capability registry by rerunning the Discovery Service registration tool.