For Tridion Sites 9.5, how to capture a Deployer transaction?

- Customer is experiencing issues related to the Deployer, such as high CPU utilization on the broker database server when publishing.
- SDL Support has requested a Deployer transaction zip file so that Support may try to reproduce the issue on a test server.

- In the Deployer deployer-conf.xml file add attribute LegacyTransport with value true as in below example

<Deployer xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Version="9.5"
          xsi:noNamespaceSchemaLocation="schemas/deployer-conf.xsd" LegacyTransport="true">

- In same config file, uncomment the Cleanup property and verify the value is false as in below example

<Property Name="Cleanup" Value="false"/>

- Restart Deployer and testing publishing.  The publishing transactions will be saved to the Deployer folder specified in the deployer-conf.xml file.

<BinaryStorage Id="PackageStorage" Adapter="FileSystem">
        <Property Name="Path" Value="FILE_SYSTEM_LOCATION"/>
    </BinaryStorage>

- Send zip file(s) to SDL Support if requested.
- Revert configuration changes and restart Deployer again, when it is no longer necessary to capture publish transactions.  Publishing trace files from past publishing activities can also be removed.

Also see KB article How to configure the SDL Web 8.x/SDL Tridion Sites 9.x Deployer for manual deployments