Cisco Cisco Unified Customer Voice Portal 10.0(1) Notas De La Versión
C
HAPTER
3:
A
DMINISTRATION
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
CVP
VXML
S
ERVER
AND
C
ISCO
U
NIFIED
C
ALL
S
TUDIO
70
o
External back-end systems such as web services and databases (including the user
management database).
management database).
o
Web servers hosting static content used by the application such as audio or grammar
files.
files.
When each of these resources become unavailable or change, all callers would be affected.
For small changes such as a revised audio file, this situation may be acceptable. For large-
scale changes that span multiple systems, this could cause problems such as callers who are
visiting an application when the update is made experiencing an error because a database is
down.
For small changes such as a revised audio file, this situation may be acceptable. For large-
scale changes that span multiple systems, this could cause problems such as callers who are
visiting an application when the update is made experiencing an error because a database is
down.
For large changes, the application should be suspended and the changes made once all callers
have left the system (see the following section on suspending applications). Once the
application is fully suspended, the administrator is free to make the changes and when done,
the application should be updated followed by resuming it from its suspended state. This
way, no caller will be in the system when the changes are made. The only disadvantage to
this approach is that it will make the application unavailable for a period of time as opposed
to a transparent change if the update feature alone is used. This may be a necessary tradeoff
considering the consequences.
have left the system (see the following section on suspending applications). Once the
application is fully suspended, the administrator is free to make the changes and when done,
the application should be updated followed by resuming it from its suspended state. This
way, no caller will be in the system when the changes are made. The only disadvantage to
this approach is that it will make the application unavailable for a period of time as opposed
to a transparent change if the update feature alone is used. This may be a necessary tradeoff
considering the consequences.
•
When the update occurs, the event created by VXML Server to send to any loggers that are
listening will reflect when the update function was executed, not when it completed.
listening will reflect when the update function was executed, not when it completed.
•
If an error occurs during the update process, e.g., due to an incorrectly configured XML file,
a description of the error is displayed and sent to any loggers listening to the appropriate
logger events and the update is cancelled.
a description of the error is displayed and sent to any loggers listening to the appropriate
logger events and the update is cancelled.
JMX Interface
To update an application using the JMX interface, use a JMX client connected to the server to
navigate to the
navigate to the
VoiceApplication/<APPNAME>/Command
MBean, where
APPNAME
is the name of
the application to update. The operations tab of this MBean will list a function named
“updateApplication”. Pressing this button will cause the application to be updated and the result
of the update will be displayed in a dialog box.
“updateApplication”. Pressing this button will cause the application to be updated and the result
of the update will be displayed in a dialog box.
The administrator should be aware that there is no confirmation when this function is called, the
update happens immediately once executed.
update happens immediately once executed.
Note that while the function returns immediately, the old application may still be active if there
were calls visiting the application at the time of the update. Only when all existing callers end
will the old application configuration be removed from memory. To determine when that occurs,
use the status function.
were calls visiting the application at the time of the update. Only when all existing callers end
will the old application configuration be removed from memory. To determine when that occurs,
use the status function.
To update all applications at once using the JMX interface, navigate to the
Global/Command
MBean and click on the function named “updateAllApps” in the operations tab. The results will
be displayed in a dialog box, listing each application updated. As with the application-specific
be displayed in a dialog box, listing each application updated. As with the application-specific