Cisco Cisco Unified Customer Voice Portal 10.0(1) Guía Del Usuario
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
C
HAPTER
3:
A
DMINISTRATION
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
C
ALL
S
ERVICES
,
U
NIVERSAL
E
DITION
AND
U
NIFIED
C
ALL
S
TUDIO
80
global data and the result will appear in the dialog box. Be careful when using this function
as it could affect the performance of applications that rely on global data.
as it could affect the performance of applications that rely on global data.
•
getGlobalData
– This function allows the administrator to retrieve the value of a global data
variable. The function takes one input: the name of the global data variable to retrieve. Click
on the button to display a dialog box showing value of the global data.
on the button to display a dialog box showing value of the global data.
Application Data Access
To access application data using the JMX interface, navigate to the
VoiceApplication/<APPNAME>/Data
MBean, where
APPNAME
is the name of the application
whose application data is to be accessed. The Attributes tab lists all the application data variable
names in an attribute named “AllApplicationDataNames” (the value may need to be expanded in
order to see all the application data names). The Operations tab lists four functions that can be
executed by the administrator for application data:
names in an attribute named “AllApplicationDataNames” (the value may need to be expanded in
order to see all the application data names). The Operations tab lists four functions that can be
executed by the administrator for application data:
•
setApplicationData
– This function allows the administrator to create a new application data
variable. The function takes two inputs, the first being the name of the variable and the
second being the value. Click on the button to set the application data and the result will
appear in a dialog box. Note that if there is already application data with the same name it
will be overridden.
second being the value. Click on the button to set the application data and the result will
appear in a dialog box. Note that if there is already application data with the same name it
will be overridden.
•
removeApplicationData
– This function allows the administrator to delete a application data
variable. The function takes one input: the name of the application data variable to delete.
Click on the button to remove the application data and the result will appear in the dialog
box.
Click on the button to remove the application data and the result will appear in the dialog
box.
•
removeAllApplicationData
– This function allows the administrator to delete all application
data, whether it was created by the administrator or applications. Click on the button to
remove all application data and the result will appear in the dialog box. Be careful with this
function as it could affect the performance of the application.
remove all application data and the result will appear in the dialog box. Be careful with this
function as it could affect the performance of the application.
•
getApplicationData
– This function allows the administrator to retrieve the value of a
application data variable. The function takes one input: the name of the application data
variable to retrieve. Click on the button to display a dialog box with the value of the
application data.
variable to retrieve. Click on the button to display a dialog box with the value of the
application data.
Administrator Log Access
Call Services ships with various default loggers, including administration history loggers that
store a history of the administration activity taken such as when Call Services started up, when
an application was updated, the results of he suspension of Call Services, etc. These logs, which
are rotated daily, are useful to an administrator as an audit history of administrator activity. As a
convenience, the JMX interface exposes methods for the administrator to access the contents of
these logs instead of viewing the files in a text editor.
store a history of the administration activity taken such as when Call Services started up, when
an application was updated, the results of he suspension of Call Services, etc. These logs, which
are rotated daily, are useful to an administrator as an audit history of administrator activity. As a
convenience, the JMX interface exposes methods for the administrator to access the contents of
these logs instead of viewing the files in a text editor.