Overview: This is intended as a guide to the logging configuration files and output locations for each type. It will also include the process we use to turn up the logs.

Products and versions: 

Connect versions of ProjectWise Design Integration Server Connect Editions all services (Gateway, Caching, and PWDI (ProjectWise Design Integration))

How to "turn up" the logs

Copy the config xml file to the local desktop.  Make the required changes and copy the file back into the location from where the file was copied from. 
Search and replace the term ="WARN" with ="ALL"  This will change each section from a state where the logging captures events of the 'Warn' type category to record 'All' events for that category. 

It may be necessary to target individual sections to capture specific information.  This will also help in decreasing log file size. 
For example, you may need to only capture network sections in detail which means you would only turn up sections that include database such as the line below: where the phrase ="WARN" would be replaced with ="ALL":

<category name="pwise.network">           <priority value="warn"/></category>

How to "Turn down" the logs

How do I turn logging back down after I gather the logs?

You can either repeat the process by replacing all instances of ="ALL" with ="WARN" (or their default value), or you can make a copy of the original xml which will have the same name as the xml you originally copied out, but will have ".delivered" as the file extension, rename it to the original file and copy it back into the location where the config xml file is originally found. 

For example, for ProjectWise Explorer, the logging config file is named pwc.log.xml and the as delivered default file is named pwc.log.xml.delivered . The delivered file is a copy that is in the default layout and will return logging to turned down when renamed and copied into the original location.

Additional Notes:

1. Is the replace phrase verbose (exactly as listed in this article)?

Yes, it has been explicitly determined that replacing the exact phrase ="WARN" with ="ALL" only changes the value exactly where you want it to; if you are doing a "replace all" or a step-down case by case search. It will leave the documentation mentions of warn alone as it takes the exact phrasing into consideration when replacing any value. 

2. Why do you copy the config files to your desktop to work with them?

We have found that copying the config file to the desktop and making the changes there, allows to save the changes without having to open the editor in any admin mode. This also allows to copy the file to both the x86 program files as well as the 64-bit program files location if both are required as is the case with ProjectWise Explorer.

Logging Locations and Outputs

To configure logging for	Edit this file	Which outputs to
ProjectWise Design Integration Server, ProjectWise Caching Server and/or ProjectWise Gateway Service	%ProgramFiles%\Bentley\ProjectWise\bin\dmskrnl.log.xml	%Public%\Bentley\Logs\dmskrnl.log
ProjectWise User Synchronization Service	%ProgramFiles%\Bentley\ProjectWise\bin\usersync.log.xml	%LocalAppData%\Bentley\Logs\usersync.log
ProjectWise Administrator	%ProgramFiles(x86)%\Bentley\ProjectWise\bin\pwadmin.log.xml	%LocalAppData%\Bentley\Logs\pwadmin.log
ProjectWise Explorer	%ProgramFiles%\Bentley\ProjectWise\bin\pwc.log.xml and %ProgramFiles(x86)%\Bentley\ProjectWise\bin\pwc.log.xml	%LocalAppData%\Bentley\Logs\pwc.log
Integrated Bentley Products	%ProgramFiles%\Bentley\ProjectWise\bin\mcm.log.xml and %ProgramFiles(x86)%\Bentley\ProjectWise\bin\mcm.log.xml	%LocalAppData%\Bentley\Logs\mcm.log
Integrated AutoCAD & integrated Office	%ProgramFiles%\Bentley\ProjectWise\bin\odma.log.xml and %ProgramFiles(x86)%\Bentley\ProjectWise\bin\odma.log.xml	%LocalAppData%\Bentley\Logs\odma.log
ProjectWise Orchestration Framework Service, Bentley i-model Composition Server for PDF (Portable Document Format), or ProjectWise Design Integration Server's document processors	%ProgramFiles(x86)%\Bentley\ProjectWise\bin\OFAdmin\OrchFwrkLogging.config	%ProgramData%\Bentley\Logs\LoggingService.log