Cisco Cisco Customer Voice Portal Downloads Mode D'Emploi
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)
50
found in the VoiceXML Server
admin
folder to prompt the VoiceXML Server to remove all
applications from memory whose folders have been deleted. 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. The VoiceXML 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.
applications so that any new callers visiting them while they are being removed will hear the
suspended application audio. The VoiceXML 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 default loggers included with the VoiceXML
Server open log files located within the application’s
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 default loggers included with the VoiceXML
Server open 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. This may work on Windows
if no loggers are used or the only loggers used are those that do not rely on files stored in the
if no loggers are used or the only loggers used are those that do not rely on files stored in the
logs
folder.
The second method for removing an application from the VoiceXML Server addresses these
issues. The first step would be to run the script
issues. The first step would be to run the script
releaseApp.bat
on Windows or
releaseApp.sh
on Unix in the application’s
admin
folder. This prompts the VoiceXML 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
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
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
script.
Updating Common Classes
When performing an application update using the
updateApp
or
updateAllApps
scripts, all the
data and Java classes related to an application will be reloaded. Java classes placed in the
common
folder of the VoiceXML Server are not included in this update. Should changes be made to
classes in the
classes in the
common
folder, Windows users should run the script named
updateCommonClasses.bat
and Unix users should run the script named
updateCommonClasses.sh
found in the VoiceXML Server
admin
folder of the VoiceXML
Server should be run.
There are a few items to note about this script:
The update affects all applications that use classes in the
common
folder, so running this script
could affect applications that have not changed. Therefore, take precaution when running this
script.
script.
The update affects all classes in the
common
folder, whether they were changed or not. This
is usually not a issue unless those classes contain information in them that reloading would
reset (such as static variables).
reset (such as static variables).