Cisco Cisco Unified Customer Voice Portal 11.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
99
•
server_start
- Listed when the VXML Server web application archive initializes. This would
occur if the Java application server on which VXML Server is installed starts up or the
administrator of the application server explicitly started up the VXML Server web
application archive.
administrator of the application server explicitly started up the VXML Server web
application archive.
•
server_stop
- Listed when the VXML Server web application archive is stopped. This would
occur if the Java application server on which VXML Server is installed shuts down or the
administrator of the application server explicitly stops the VXML Server web application
archive.
administrator of the application server explicitly stops the VXML Server web application
archive.
•
deploy_all_new_apps
- Listed when the
deployAllNewApps
script is run.
•
flush_all_old_apps
- Listed when the
flushAllOldApps
script is run.
•
suspend_server
- Listed when the
suspendServer
script is run.
•
resume_server
- Listed when the
resumeServer
script is run.
•
update_common_classes
- Listed when the
updateCommonClasses
script is run.
Note that running the
status
script does not trigger an administration event and thus does not
update the history log.
Application Loggers
Application loggers are defined in the settings for that application. The application designer can
choose any number of application loggers they wish to listen to events for a particular
application, giving each instance a name. A logger may or may not require a configuration that
will allow the designer to customize how the logger performs. The configuration files must be
placed in the
choose any number of application loggers they wish to listen to events for a particular
application, giving each instance a name. A logger may or may not require a configuration that
will allow the designer to customize how the logger performs. The configuration files must be
placed in the
data/application
directory of the deployed application.
Unique to application loggers is the ability for one to specify that all logging events for a call be
passed to the logger it in the order in which they occurred in the call. Some application loggers
may even require this to be turned on as their functionality depends on the events arriving in
order. The application designer can choose to ensure this is the case even for application loggers
that do not explicitly require it to have logs appear orderly. There is some performance
degradation as a result of this so an application logger that does not require this should not
enable it.
passed to the logger it in the order in which they occurred in the call. Some application loggers
may even require this to be turned on as their functionality depends on the events arriving in
order. The application designer can choose to ensure this is the case even for application loggers
that do not explicitly require it to have logs appear orderly. There is some performance
degradation as a result of this so an application logger that does not require this should not
enable it.
VXML Server provides the
logs
folder of a particular application for log file storage should the
loggers require it. To keep each application logger instance’s logs separate, a subfolder with the
name of the instance is created and all logs created by the logger instance are stored there.
name of the instance is created and all logs created by the logger instance are stored there.
By default, VXML Server includes four loggers that provide various application-specific
information: an activity logger that records caller behavior, an application administration history
logger that records administration activities, an error logger that lists errors that occur within
calls to the application, and a debug logger that provides additional information useful when
information: an activity logger that records caller behavior, an application administration history
logger that records administration activities, an error logger that lists errors that occur within
calls to the application, and a debug logger that provides additional information useful when