Log

1. CE

• Audit logging (os)	See Audit log for information about audit logging functionality.
  Trace logging (domain/site)	See Trace logging for information on using the trace logging feature.
  Storage consistency checker logging	See the Content Storage Consistency Checker Log topic to generate a log from the storage consistency checker tool.
  Perflog	-Dfilenet.perflog.interval=on -Dfilenet.perflog.logginglevel=2 -Dfilenet.perflog.dir=E:\ #Audit#-1        3  135             406             0  0             IndependentClassRetriver::getObject Here is what they mean #Audi#-1 - the data is collected in 1 minute interval (in perf log, there are also #Audi#-10 and #Audi#-60) 3 - Number of occurrences 135 - average duration in ms for each occurrence 406 - total time spend in ms for this particular statement 0 - not used 0 - not used IndependentClassRetriver::getObject - statement executed The IBM FileNet CPE performance log is written to by the Content Engine in 1, 10, 60 and 240 minute increments. The granularity can be controlled by specifying exactly which reporting increments you’d like published in the perflog_config.properties [1] file. Each interval is an average of all of the data points for the duration reported. For example, if a transaction is executed 100 times in a one minute interval, the performance log will report the average duration for the 100 executions for the one minute audit entry. Assuming a steady workload, the 10 minute audit interval would report the average of 1000 executions. The first column in the IBM FileNet CPE performance log is the audit interval. This is denoted by #Audit#-X, where X is 1, 10, 60 or 240. Each reported interval also includes a time stamp to clearly identify when the performance data was collected. The second column represents the number of executions for that performance counter during the audit interval. The third column represents the average duration of those executions and the fourth column is the total duration. The fifth and sixth columns are always zero and reserved for future needs. The final column is the actual performance counter being reported. Performance log format: [Audit Interval] [Execution Count] [Avg. Duration (ms)] [Total Duration (ms)] 0 0 [Performance Counter] [1] This file is located under the [application server profile]/FileNet/[server_name] directory.    # configuration file for the perflog utility # use.me=true will turn on to use this property file instead of the Java commond line args  use.me=true # perflog.interval=on or perflog.interval=1:10:60:240, turn on the perflog with 1 minute accumulation interval, followed by 10, 60, 240 minutes  perflog.interval=on # perflog.dir=< log file location>, default to the CE tracelog directory # perflog.dir=c:/temp # perflog.logginglevel=2:3:4:5:6:10:15:16, where 2->DB, 3->CE Query, 4->GCD 5->CBR query, 6->content 10->CPU time 15->ScheduledBackgroundTask 16->WorkerBackgroundTask  perflog.logginglevel=2:3:5:10 # perflog.dumpthreads=<times>:<interval> will dump threads stacks to a file, <times> with <interval> elapse time in between # perflog.dumpheap=true/false/withGC, for IBM Java 5 and Sun/JRockit JDK 6 only. If "true" will dump heap, if "withGC", will do a GC and then dump heap # perflog.verbosegc=true/false to turn on or off the verbose gc dynamically, could overwrite the commandline # perflog.checkinginterval=<> default 30 (seconds), how often to check for config file change New and Updated Configuration Parameters MaxWorkers – Default: 5 The default number of Queue Item worker threads has not changed from the previous release, but the maximum number of work threads that can be configured is virtually limitless from the previous limit of 100. This pre-existing parameter can be set via ACCE or directly as a generic JVM argument (com.filenet.engine.queueitem.MaxWorkers) MaxBatchSize – Default: 100 This pre-existing parameter controls the maximum batch size that the dispatcher will query the database for work. This parameter can be set via ACCE or directly as a generic JVM argument (com.filenet.engine.queueitem.MaxWorkerThreads). FloorTime – Default: 0 This new parameter controls the minimum amount of time the dispatcher is required to sleep before leasing more work from the database. Certain situations require minimizing the frequency that the dispatcher queries the database for work, such as when the Content Platform Engine is deployed in a large cluster with many instances. In such a configuration, dispatchers can block other dispatchers if they awaken too frequently. If the dispatcher is notified to awaken, a check will be made to determine if the dispatcher has been asleep for at least the configured floor time and if not, it will go back to sleep. This parameter can only be set through a generic JVM argument (com.filenet.engine.queueitem.FloorTime). DisableNotify – Default: False This new parameter will disable the dispatcher notification mechanism that is triggered each time a new work item is written to the QueueItem table. This can be beneficial in certain situations when concurrent high volume ingestion and processing is occurring. This parameter can only be set through a generic JVM argument (com.filenet.engine.queueitem.DisableNotify).

2. PE

• Audit logging	See the vwlog topic for information about audit logging.
  Event logging	See Process Engine reference event logging for information about using logging to track workflow activity. See the following Process Configuration Console help topics for more details about event logs: Managing event logs Event logging options in an isolated region
  System function logging	The system function logging topic in the Process Designer help provides information on setting up a process to write specific events to a log.
  Trace logging	See the vwtool topic for information about trace logging.
  Troubleshooting	For troubleshooting information, see the FileNet message log files topic. For troubleshooting specific to rules functionality, see Troubleshooting Rules Functionality.