Documentation Center

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 .

Procedure

  1. In any Content Delivery software component that has a Content Deployer configuration file, open that file, which is called cd_deployer_conf.xml until you start the microservice, for editing. (When you eventually start the microservice, it will rename it to deployer-conf.xml.)
  2. Add an attribute LegacyTransport to the root element, Deployer, and set it to true.
  3. Save and close cd_deployer_conf.xml.

Results

You can continue to publish using the deprecated transport protocol. Note that deployment occurs by putting packages into queue directories. After starting the microservice, you will be able to find the root path used for legacy transport in the new deployer-conf.xml file: inside the BinaryStorage element, the value of the Path property will be the root path.