Cisco Cisco Customer Voice Portal 8.0(1) Guia Do Utilizador

C

HAPTER 

3:

 

A

DMINISTRATION

 

 

V

OICE

XML

 

S

ERVER 

U

SER 

G

UIDE 

 

 

 

FOR 

C

ISCO 

U

NIFIED 

C

USTOMER 

V

OICE 

P

ORTAL 

R

ELEASE 

4.0(1) 

 

 

 

 

 

46

and creating a new call flow branch. They can involve simple configuration changes or may 
involve new or changed Java class files. These kinds of changes occur most frequently when the 
voice application is being developed, and less frequently on a live application. 

The update functionality acts gracefully in that any callers on the system at update time continue 
to experience the rest of the call as if the application had not been updated, while new callers 
experience the updated voice application. In this manner, there is no downtime when a change is 
needed for an application; the callers are handled as expected. 

The scripts for updating an application are found in the 

admin

 folder of the application to be 

updated. Windows users should use the script named 

updateApp.bat

 and Unix users should use 

the script named 

updateApp.sh

. It is possible to update all applications deployed on Unified 

CVP VoiceXML Server by running the script 

updateAllApps.bat

 for Windows and 

updateAllApps.sh

 for Unix, found in the 

admin

 folder of the VoiceXML Server. This script 

essentially runs the update script for each application deployed on Unified CVP VoiceXML 
Server. 

There are a few items to note when updating individual voice applications. 

    The script does not return to the command prompt until all pre-update callers are finished. 

Interrupting the countdown will not stop the update process, only the visual countdown. To 
see when the update affects all live callers, execute the status scripts for the system or the 
application. 

    The gracefulness of the update applies only to those resources controlled by  the VoiceXML 

Server. These include the application settings and call flow, element configurations, Unified 
CVP decision elements, and Java classes placed in the 

java / application

 directory of the 

application. The following changes are not managed by the VoiceXML Server and therefore 
will not be gracefully updated:  

o

  Java classes placed anywhere else (including the 

common

 folder),  

o

  XML content passed to the VoiceXML Server via the XML API. 

o

  The content of VoiceXML insert elements. 

o

  External back-end systems such as databases (including the user management 

database). 

o

  Web servers hosting static content used by the application such as audio or grammars. 

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 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,