Documentation Center

Capturing transport packages for analysis

By default, the Content Deployer is configured to clean up incoming transport packages after a certain period of time. When studying a publish problem, it can prove useful to disable this cleanup in order to be able to capture and study these packages.

Procedure

  1. In the configuration location of your Content Deployer microservice, open deployer-conf.xml for editing.
  2. In the Workers section, find the line that reads <Property Name="Cleanup" Value="true"/>. By default, the line is located in a commented-out section described as "Optional configuration properties."
  3. Make sure that the line is uncommented, and change true to false.
  4. Save and close deployer-conf.xml.
  5. Restart Content Deployer.
  6. Perform publish actions that you are experiencing problems with.
  7. Go to the location where your transport packages are stored. Content Deployer stores transport packages in a subfolder of your Content Deployer microservice root location called BINPATH/Binaries/, where BINPATH is one of the following:
    • By default, BINPATH resolves to the string ${binaryPath}.
    • If you have set a binaryPath environment variable, BINPATH resolves to the value you set.
    • The Content Deployer file deployer-conf.xml contains a BinaryStorage element with its Id attribute set to PackageStorage, which has a Property subelement for a named property called Path. If you have edited the Value attribute of that property element, BINPATH resolves to that value.
  8. In this location, find the transport packages, which take the form of ZIP files.
  9. Copy the transport packages to another location as needed, unzip them and study their contents.
  10. After you have completed your analysis, edit deployer-conf.xml again, this time setting false back to true and place the line back within the comment delimiters.