Configuring a temporary location for incoming content for the Content Deployer

Decide where you want to store incoming content temporarily: on the file system or in a Redis database. Then configure your choice in the Content Deployer configuration file.

About this task

As part of performing this task, you are required to resolve one or more placeholders in the configuration file. You can resolve placeholders to actual values by:
  • defining system environment variables before running the installation script
  • defining Java properties before running the installation script
  • passing the properties and their values when you run the installation script

Procedure

  1. Go to the configuration location of your Content Deployer microservice.
  2. Open the file deployer-conf.xml for editing.
  3. If you want to store incoming content on the file system, there is no need to modify the file. Instead, ensure that the binaryPath placeholder (enclosed in ${ and } delimiters) in the uncommented BinaryStorage section resolves to the absolute path to a folder on the server on which the Content Deployer is installed, which must be a writable and accessible file system location.
  4. Alternatively, if you want to store incoming content in a Redis database (from which the Content Deployer removes it after successfully completing the publish transaction), put the existing BinaryStorage section in comments, and uncomment the BinaryStorage section with its Adapter attribute set to the value RedisBlobStorage. This section contains a number of named properties, some as placeholders (enclosed in ${ and } delimiters), others as hardcoded values. Set the values of the various named properties as follows:
    PropertyDescription
    HostSet this to the host name of your Redis database server by resolving storageHost to that host name.
    PortSet this to the port number of your Redis database server by resolving storagePort to that port number.
    PasswordSet this to the password required to access the Redis database by entering the hardcoded password, encrypted, directly in the file.
    TimeoutSet this to the time period, in milliseconds, after which the Content Deployer considers the Redis database to be offline, by entering the period directly in the file.
  5. Save and close deployer-conf.xml.