Publishing Engine Programmer's Guide > PTC Arbortext Publishing > Arbortext Publishing Engine Server Composer > Debugging the Server Composer
  
Debugging the Server Composer
The source and target directories that the Server Composer creates are located in the transaction directory allocated by the Arbortext PE Request Manager when it processed the f=java request that ran the Server Composition Application.
To obtain the transaction directories, configure Arbortext Publishing Engine so that the transaction archive retains all transactions (explained in Configuration Guide for Arbortext Publishing Engine), then use the Arbortext Publishing Engine web page (explained in Monitoring and Reporting Using a Web Browser) to locate the transaction archive directory and the archive entry (zip archive) for the transaction. You can restore the zip archive to a temporary directory.
The Server Composition Application, Server Composer, and Server Composition Extensions all log their behavior using the same log4j mechanisms as other Arbortext PE Applications. To obtain the log information, set the level of logging you desire, as described in Configuration Guide for Arbortext Publishing Engine.