-
Notifications
You must be signed in to change notification settings - Fork 3
Configuration
Rob van Oostenrijk edited this page May 15, 2014
·
1 revision
The following configuration options are available in the TcmDebugger.config (app.config).
<TcmDebugger>
<database name="database-name" server="database-server" username="database-user" password="database-password" />
<logging level="Verbose" includeTridionClasses="true" />
<templating schemaCache="" enableImpersonation="false" impersonationIdentity="domain\username" />
<cms url="http://remote-tridion-host/" localPort="9090" previewDirectory="C:\temp" />
<debugging enableBreakpoint="true">
<debugAssembly name="Company.Templating.MyAssembly" />
<debugAssembly name="Company.Templating.AnotherAssembly" />
</debugging>
</TcmDebugger>
<tridionConfigSections>
<sections>
<clear />
<add filePath="config\Tridion.ContentManager.config" />
</sections>
</tridionConfigSections>
Database contains the configuration for the TcmDebugger to connect to the Tridion content manager database. It is advisable to create a read-only user for this purpose, so that actions of the TcmDebugger do not modify any data in the Tridion content manager database.
- database
- name: Contentmanager database name
- server: Contentmanager database server
- username: Contentmanager database user
- password: Contentmanager database password
- logging
- level: One of Verbose, Information, Error, Critical
- includeTridionClasses: Switch to include internal logging from Tridion classes (as Verbose)
- templating
- schemaCache: Relative directory (to the application executable) to the parent directory containing the Tridion schema xsd's (schema folder)
- enableImpersonation: Dynamically add the current process user identity as a valid Tridion impersonation user.
- impersonationIdentity - User identity in the form of
<domain>\<user>to impersonate. This is useful when debugging Tridion authentication related errors, i.e. running a template under a custom Tridion user identity when debugging.
- cms
- url: Absolute URL to the Tridion Content Manager to which the configured database belongs, i.e. http://cms.domain/
- previewDirectory: Local folder to output binaries generated during templating
- localPort: The local network port for both the Preview server and the Compound Template Webservice to listen on.
- debugging
- enableBreakpoint: Switch to cause TcmDebugger to pause the processing when all the configured debug assemblies have been loaded, but before they are executed. This is the optimal moment to attach a debugger and start the debug session.
- debugAssembly: One or more assemblies to load in memory before template execution to allow debugging.
A Tridion.ContentManager.config is also included to configure the templating engine behavior. It is possible to configure additional mediators, logging, impersonation users in this configuration as per the Tridion documentation.