Cisco Cisco Unified Customer Voice Portal 11.0(1) User Guide
C
HAPTER
5:
V
OICE
XML
S
ERVER
L
OGGING
V
OICE
XML
S
ERVER
U
SER
G
UIDE
FOR
C
ISCO
U
NIFIED
C
USTOMER
V
OICE
P
ORTAL
R
ELEASE
4.0(1)
80
<format delimiter="***" remove_delimiter_from_content="false"
date_format="minimal" date_granularity="seconds" print_stack_traces="false"/>
</configuration>
</configuration>
This configuration has the following features:
The error logs will be delimited with the string “***” and will not attempt to remove that
string from the content. Note that the delimiter does not need to be limited to a single
character and can be a multi-character string. Usually, though, it is a single character to make
importing into spreadsheets and databases straightforward.
character and can be a multi-character string. Usually, though, it is a single character to make
importing into spreadsheets and databases straightforward.
Dates in the error logs will appear in the minimal format with seconds granularity. For
example: “15:45:02”
Java stack traces will not appear in the error logs. When a Java exception occurs, only the
error message itself will appear in the error log without the stack trace.
No file purging will take place. The administrator is responsible for maintaining the logs on
the system.
The Application Administration History Logger
Whenever an application-specific administration script is run, a log file is updated with
information on the script that was run. The administration log file names are in the form
“admin_historyYYYY-MM-DD.txt” where YYYY, MM, and DD are the year, month, and day
when the administration history log was first created and is rotated daily. The file contains three
columns: the time the script was run, what script was run, and its result. The result is usually
“success” and if not contains the description of the error encountered. The possible values are:
information on the script that was run. The administration log file names are in the form
“admin_historyYYYY-MM-DD.txt” where YYYY, MM, and DD are the year, month, and day
when the administration history log was first created and is rotated daily. The file contains three
columns: the time the script was run, what script was run, and its result. The result is usually
“success” and if not contains the description of the error encountered. The possible values are:
server_start
- Each application’s history log contains records of each time the application
server starts.
deploy_app
- Listed when the
deployApp
script is run.
suspend_app
- Listed when the
suspendApp
script is run.
resume_app
- Listed when the
resumeApp
script is run.
update_app
- Listed when the
updateApp
script is run.
release_app
- Listed when the
releaseApp
script is run.
update_common_classes
– Listed when the global
updateCommonClasses
script is run. The
reason this global admin event is logged by the Application Administration History Logger is
because elements that appear in the
because elements that appear in the
common
directory are reloaded by this command,
prompting those elements to reload their application-specific configurations.
Running the
status
script does not update the history log.