Pipeline Log Files
When pipeline logging is enabled, pipeline log files are stored in the pipeline/logfiles subdirectory. A log file is created for every user and pipeline pair, so every user has a log file for every pipeline they run. If a user runs a pipeline more than once, their previous log file is written over by the new log file.
You can use the information contained in the pipeline log files to see what dictionary values are read and written by the components that are run in the pipeline, and what the error level for each component is, which is useful in debugging.
Use the following procedure to enable pipeline logging on your site.
- It is recommended that you only use pipeline logging in development mode. You can enable pipeline logging while in production mode; however, logging the pipelines in production mode will decrease the performance for your site.
- The Direct Mailer pipeline does not support generating a pipeline log file.
To enable pipeline logging
Open the global_siteconfig_lib.asp page.
In the InitSitePipelines function, find these lines of code and replace False with True (if in production mode, the first line is MSCSEnv = PRODUCTION):
If MSCSEnv = DEVELOPMENT Then dictPipeline.LoggingEnabled = False dictPipeline.LogsCycled = False
Open Windows Explorer and browse to the log files subdirectory.
On the File menu, click Properties.
On the Security tab click Add.
In the Select Users, Computers, or Groups dialog box, type the name of the anonymous user account in the lower box. For example, if your server name is computer1, type computer1\iusr_computer1 and then click OK.
On the Log Files Properties dialog box, set the permission level to Full Control for the anonymous account by checking the Allow box in the Full Control row of the Permissions box, and then click OK.
To test the logging feature, make sure your site is the environment in which pipeline logging was enabled in Step 1. To change the environment, open the global.asa file and set MSCSEnv to the correct environment.
A pipeline log file is now created for each user that runs a pipeline, for each pipeline in your site. If a user runs a pipeline more than once, the previous log file will be written over.