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
- In the configuration location of your Content Deployer microservice, open
deployer-conf.xmlfor editing. - In the
Workerssection, 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." - Make sure that the line is uncommented, and change
truetofalse. - Save and close deployer-conf.xml.
- Restart Content Deployer.
- Perform publish actions that you are experiencing problems with.
- 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
binaryPathenvironment variable, BINPATH resolves to the value you set. - The Content Deployer file deployer-conf.xml contains a
BinaryStorageelement with itsIdattribute set toPackageStorage, which has aPropertysubelement for a named property calledPath. If you have edited theValueattribute of that property element, BINPATH resolves to that value.
- In this location, find the transport packages, which take the form of ZIP files.
- Copy the transport packages to another location as needed, unzip them and study their contents.
- After you have completed your analysis, edit deployer-conf.xml again, this time setting
falseback totrueand place the line back within the comment delimiters.