Performing basic configuration tasks : Using Simple view : Configuring diagnostic logging : Configuring a diagnostic logging category
 
Configuring a diagnostic logging category
A configuration change in the default Simple view applies to all categories of logging. In the default Simple view, Category does not appear in Diagnostic logging.
Advanced view—Server Configuration Templates—Settings supports changing diagnostic logging for specific types of logs. If the administrator configures one logging type differently from the others in Advanced view, Category appears in Simple view, as shown in Figure 1‑11.
Figure 1‑11 Viewing a list of categories in Simple view
The Category list includes the following log types:
*General
*Factory
*Integration
*Caching
*Viewing
Table 1‑1 describes these categories, provides examples, and lists the log file names.
Table 1‑1 Diagnostic logging categories and log files
Category
Logged events
Log file
General
Logs Encyclopedia volume events:
*Validating login requests
*Creating Encyclopedia volume folders
*Adding files
*Managing e‑mail notification
Records other events that occur outside Factory, Integration, Caching, and Viewing service processes
encycsrvr11
Factory
Logs Factory service events:
*Running designs
*Generating queries
*Printing documents
facsrvr11
Integration
Logs Integration service events regarding information objects that use data from multiple data sources
intsrvr11
Caching
Logs Caching service events regarding information object cache
cachesrvr11
Viewing
Logs Caching service events:
*Viewing documents in DHTML format
*Converting documents to formats, such as Excel and PDF
*Handling requests to download files from an Encyclopedia volume
viewsrv11
How to configure diagnostic logging by category
1 In Diagnostic logging, in Category, choose a log category to configure. For example, choose General.
2 In Level, Directory, Size, and Number of log files, accept the default values or specify new values.
3 Choose Update logging.
4 If you change Directory, restart iHub.
Configuration Console writes setting changes to the acserverconfig.xml file in AC_DATA_HOME/config/iHub2. Table 1‑2 lists the property names that appear in Configuration Console with the corresponding parameter names in acserverconfig.xml, including default settings, ranges, and when the property change takes effect.
Table 1‑2 Diagnostic logging parameters 
Property name
Parameter name
Default
Range
Takes effect
Log level
LogLevel
8000
0 - 9000
Immediate
Log size
LogSize
10000 KB
 
Immediate
Number of log files
NumLogs
3
 
Immediate
For more information about diagnostic logging, see Chapter 3, “Using diagnostic, usage, and error logging.”