Cisco Cisco Customer Voice Portal 8.0(1) Release Note
C
HAPTER
5:
VXML Server
L
OGGING
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
CVP
VXML
S
ERVER
AND
C
ISCO
U
NIFIED
C
ALL
S
TUDIO
116
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.
The Administration History Logger does not utilize a configuration.
The Application Debug Logger
At times when debugging an application it would be advantageous to see information concerning
the HTTP requests made by the voice browser and the corresponding HTTP responses of VXML
Server. The Debug Logger creates a single file per call that contains all HTTP requests and
responses that occurred within that call session. The log files are named “debug_logYYYY-MM-
DD-HH-SESSIONID.txt” where YYYY is the year, MM is the month, DD is the day, and HH is
the hour (in 24-hour time) that the file is created and SESSIONID is the VXML Server session
ID (e.g. “debug_log2000-01-01-17-192.168.1.100.1024931901079.1.MyApp.txt”). The session
ID is included in the filename to ensure uniqueness of the files. The debug log contains:
the HTTP requests made by the voice browser and the corresponding HTTP responses of VXML
Server. The Debug Logger creates a single file per call that contains all HTTP requests and
responses that occurred within that call session. The log files are named “debug_logYYYY-MM-
DD-HH-SESSIONID.txt” where YYYY is the year, MM is the month, DD is the day, and HH is
the hour (in 24-hour time) that the file is created and SESSIONID is the VXML Server session
ID (e.g. “debug_log2000-01-01-17-192.168.1.100.1024931901079.1.MyApp.txt”). The session
ID is included in the filename to ensure uniqueness of the files. The debug log contains:
•
A timestamp of when each HTTP request was received from the voice browser as well as
when the response was sent back by VXML Server.
when the response was sent back by VXML Server.
•
All headers of the HTTP request.
•
All arguments passed with the HTTP request, whether they be set via GET or POST.
•
The entire VoiceXML page returned in the HTTP response.