Adding Experience Optimization to the Content Deployer

When you installed the Content Deployer, you had the option of loading an Add-on that included the Content Deployer extension for Experience Optimization. If you did so, you can skip this task. If you did not do so, say because you hadn't yet decided whether to use Experience Optimization or not, you can still make the change now.

Before you begin

Before starting this task, you must have already set up Content Deployer.

Procedure

  1. In the configuration location of your Content Deployer, open deployer-conf.xml for editing.
  2. Find the Pipelines section in this file and remove all Pipeline elements within it.
  3. On the installation media, go to \Content Delivery\roles\xo\add-ons\.
  4. Download the file xo-deployer-extension-assembly-VERSION-core.zip to a folder of your choosing, where VERSION is a string indicating the version and build number of the ZIP file at the time of release.
  5. If you want to override any part of the existing configuration, also download xo-deployer-extension-assembly-VERSION-config.json to the same folder, and open it for editing.
  6. Because the JSON configuration file overrides the existing configuration, first remove all JSON parameters that represent settings you do not wish to override.
    You now have JSON configuration file containing only those settings that you want to override.
  7. Now override any remaining parameters with your override values.
    For example, if the value of the cdenvironment environment variable on the machine on which the Content Deployer runs is not staging, replace the root-level string staging with your custom value.
  8. Save and close xo-deployer-extension-assembly-VERSION-config.json
  9. In Content Manager Explorer, select Add-ons from the slide-out navigation and from the Manager tab, upload the ZIP file you downloaded.
  10. If you have also copied and edited the JSON configuration file, add it to the Add-on as well.
  11. Restart your Content Deployer microservice.