Cisco Cisco Unified Customer Voice Portal 11.0(1) User Guide

HAPTER

DMINISTRATION

ISCO

CVP

OICE

XML

User Guide

order to load the application, the

deployApp.bat

script found in the

admin

folder of the new

application should be launched.

If multiple applications are created and need to be deployed together, the

deployAllNewApps.bat

script found in the

admin

directory of the Server will deploy all new

applications together. All existing voice applications are unaffected and calls can now be
received for all new applications.

Note that due to the fact that the Server automatically loads all available applications when the
Java application server is started up, there is no need to run an administration script when new
applications are deployed on the Server while the application server is not running.

Removing Applications

There are two separate methods for removing an application from the memory of CVP
VoiceXML Server while the Java application server is still running. Determining which method
to use will depend on the operating system and the circumstances behind the application
removal.

The first method involves two steps. The first is to delete (or move) the folder holding the
desired application from the Server

applications

folder. The second step involves launching

the

flushAllOldApps.bat

script found in the Server

admin

folder to prompt the Server to

remove all applications whose folders have been removed from memory. The script itself first
suspends the applications so that any new callers visiting them while they are being removed will
hear the suspended application audio. Server will also act gracefully for the removal: all callers
visiting the applications at the time they are being removed will continue to experience the
applications unchanged.

While this is the simplest method, it does pose some issues. The first is that if an application
relies on files found within its folder at call time, there may be problems with existing callers
reaching a point where these files are needed and they will not be found. The second issue is that
this process will not work on Windows since the Server opens log files located within the
application’s

logs

folder and the operating system will not allow the deletion of a folder when

resources within it are open.

The second method for removing an application from the Server addresses these issues. The first
step would be to run the

releaseApp.bat

script in the application’s

admin

folder. This prompts

the Server to first suspend the application then remove it from memory in the same way as the

flushAllOldApps

script does. At this point the application folder can be deleted (or moved). It

is important to do this only after the

releaseApp.bat

script has indicated that all existing callers

to the application have left. Being an application-specific script, it affects only a single
application, so if multiple applications are to be removed using this method, the administrator
would have to run this script for each application. Once this process is complete, there is no need
to use the

flushAllOldApps.bat

script.