Installing the Content Deployer
The Content Deployer takes care of receiving incoming content published from Content Manager, and processing and storing that content.
- Copying Content Deployer resources
To copy Content Deployer resources, depending on the type of installation you are performing, copy the contents of a folder to your target machine. - Configuring the Content Deployer
Perform a number of required configurations for your Content Deployer. - 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 Storage Layer configuration file. In this file, you can specify configuration strings as hardcoded values or as parameters. - Configuring the SSL keystore in the application properties of Content Deployer
If you want to secure the Content Deployer with SSL, and you have set up the prerequisites to do so, configure the application.properties file to use the keystore. - Installing the Content Deployer microservice
Run an installation script to install the Content Deployer microservice. - 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 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. - Uploading an Add-on to your Content Deployer for your situation
To complete the installation, set up your Content Deployer for the specific products and product features you are using or intending to use. To do this, you must add an Add-on to your Content Deployer. - Disabling the Content Delivery search feature in Content Deployer
By default, the Content Delivery search feature is an enabled feature, and RWS considers it a core product feature. But if you have decided not to use it, perhaps because you have a search feature of your own, you can skip the task of configuring the connection to Elasticsearch. This task describes which configuration steps to perform in Content Deployer in order to disable the search feature.
Related tasks