Cisco Cisco Unified Customer Voice Portal 10.0(1) User Guide
C
HAPTER
5:
C
ALL
S
ERVICES
L
OGGING
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
C
ALL
S
ERVICES
,
U
NIVERSAL
E
DITION
AND
U
NIFIED
C
ALL
S
TUDIO
99
executing administration script (see Chapter 3: Administration for more on administering Call
Services).
Services).
The administration log file names begin with “admin_historyYYYY-MM-DD.txt” where
YYYY, MM, and DD are the year, month, and day when the administration log was first created.
By default, the log folder for is named “GlobalAdminLogger” (though the name is set in the
YYYY, MM, and DD are the year, month, and day when the administration log was first created.
By default, the log folder for is named “GlobalAdminLogger” (though the name is set in the
global_config.xml
file and can be changed by the administrator). Administration history log
files are rotated daily. Note that if no administration activity occurred on a particular day, no
administration history log will be created.
administration history log will be created.
The file contains three columns: the time, what script was run, and its result, separated by
commas. The result is usually “success” and if not, contains the description of the error
encountered. The possible values of the result are:
commas. The result is usually “success” and if not, contains the description of the error
encountered. The possible values of the result are:
•
server_start
- Listed when the Call Services web application archive initializes. This would
occur if the Java application server on which Call Services is installed starts up or the
administrator of the application server explicitly started up the Call Services web application
archive.
administrator of the application server explicitly started up the Call Services web application
archive.
•
server_stop
- Listed when the Call Services web application archive is stopped. This would
occur if the Java application server on which Call Services is installed shuts down or the
administrator of the application server explicitly stops the Call Services web application
archive.
administrator of the application server explicitly stops the Call Services 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
passed to the logger it in the order in which they occurred in the call. Some application loggers