The application has the ability to enable trace level logging via Global Settings on the Server. For more information on setting a trace level, refer to Configuring Global Settings.
Multiple logging types can be specified by adding the individual number to a cumulative value. For example, a value of 84 would result in Verbose logging of Publishing and Data Access components (16 + 64 + 4 = 84). The trace level value can be set to include any of the following:
|
Log Type
|
Value
|
|
User Interface
|
1
|
|
Glossary
|
2
|
|
Data Access
|
4
|
|
Security
|
8
|
|
Verbose
|
16
|
|
Vignette Collaboration Communication
|
32
|
|
Publishing
|
64
|
|
Notifications
|
128
|
|
Reporting
|
256
|
|
Content Verification
|
512
|
|
uPerform Monitoring Service
|
1024
|
|
uPerform Web Service Requests
|
2048
|
|
PENS/LMS Communication
|
4096
|
|
uPerform Web Service Response
|
8192
|
|
User Synchronization/LDAP
|
16384
|
|
Integration Webservice Incoming Solution Manger Requests
|
32768
|
|
Outgoing Solution Manager Requests
|
65536
|
|
uPerform Windows Service Controller
|
131072
|
|
Configuration Wizard
|
262144
|
Trace values can be changed dynamically when the server is running. The web service will automatically rebuild to include the logging values. When logging is enabled, the system will write web service information to the log file [Install Location]\Collaboration\uPerform\logs\ServerErrors.xml.
The Server also has the ability to enable application informational logging by setting debug options within the system. The dynamic properties web page has several debug options that can be enabled or disabled. To enable a certain application debug option, set its value to "true". To disable the debug option, set its value to "false". Application informational logging is written to [Install Location]\Collaboration\log\CollabConsole.txt. The application informational logging options are listed below:
- debug.CommandState
- debug.CommitServlet
- debug.SMTP
- debug.UsageAnalysis
- debug.docCommitServlet
- debug.docUploadTiming
- debug.gmServlet
- debug.gmServlet.printpath
- debug.kmapi.xml
- debug.ldap
- debug.properties
- debug.servlet
- debug.template
- debug.wsdlServlet
|
NOTE:
|
Use caution when granting access to the following log files as they may contain sensitive data:
[Install Location]\Collaboration\log\CollabConsole.txt
[Install Location]\Collaboration\log\localhost_access_log.[date].txt)
|
To view detailed log information in regard to the login process, change the log Level parameter in [Install Location]\Collaboration\conf\jaas.conf to "VERBOSE". The Vignette Collaboration service must be restarted after changing jaas.conf. The additional log messages are written to [Install Location]\Collaboration\log\CollabConsole.txt.