Cisco Cisco Customer Voice Portal Downloads 릴리스 노트
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
75
Removing Applications
VXML Server exposes two administrative functions to handle the removal of application(s) from
memory at runtime. Determining which function to use will depend on the operating system and
whether the application being removed is actively handling calls.
memory at runtime. Determining which function to use will depend on the operating system and
whether the application being removed is actively handling calls.
The first method involves executing the release application function of the application to be
removed. This prompts VXML Server to first suspend the application then remove it from
memory when all the active callers at the time the function was executed, have naturally ended
their sessions. It suspends the application first to prevent new callers from entering the
application. Once all active callers are done visiting the application the folder of the application
can be deleted (or moved) from the VXML Server
removed. This prompts VXML Server to first suspend the application then remove it from
memory when all the active callers at the time the function was executed, have naturally ended
their sessions. It suspends the application first to prevent new callers from entering the
application. Once all active callers are done visiting the application the folder of the application
can be deleted (or moved) from the VXML Server
applications
folder. This function affects
only a single application so if multiple applications are to be removed using this method, the
administrator would have to execute this function for each application.
administrator would have to execute this function for each application.
Note that on the Microsoft Windows operating system, a user attempting to delete an application
folder after the releaseApp function is called may be prevented from doing so by the operating
system if the application references Java application archive (JAR) files placed within the
folder after the releaseApp function is called may be prevented from doing so by the operating
system if the application references Java application archive (JAR) files placed within the
java/application/lib
or
java/util/lib
directories. This is due to the system keeping an
open file handle for JAR files that will not be released until a garbage collection event occurs. As
a result, the administrator will have to wait until the garbage collector activates before being able
to delete the directory. The time to wait will be determined by how often garbage collection is
run. A rule of thumb is that a high load system or one with a small amount of memory will
encounter garbage collection often, a low volume system or one with a large amount of memory
will take longer.
a result, the administrator will have to wait until the garbage collector activates before being able
to delete the directory. The time to wait will be determined by how often garbage collection is
run. A rule of thumb is that a high load system or one with a small amount of memory will
encounter garbage collection often, a low volume system or one with a large amount of memory
will take longer.
The second method supports the ability to delete multiple applications at once. This time one
must first delete (or move) the folders holding the desired applications to be deleted. After
which, the flush all old applications function is executed and VXML Server will suspend then
remove from memory all the applications that it no longer finds in the
must first delete (or move) the folders holding the desired applications to be deleted. After
which, the flush all old applications function is executed and VXML Server will suspend then
remove from memory all the applications that it no longer finds in the
applications
folder. As
with the other method, the application is not removed from memory until all callers have ended
their visits.
their visits.
There are certain issues with the second method:
•
If an application relies on files found within its folder at runtime, there may be problems with
existing callers reaching a point where these files are needed and they will not be found.
existing callers reaching a point where these files are needed and they will not be found.
•
This process may not work on Microsoft Windows since Windows will not allow the deletion
of a folder when resources within it are open. For example, the application loggers may have
open log files located within the application’s
of a folder when resources within it are open. For example, the application loggers may have
open log files located within the application’s
logs
folder. This may work if no loggers are
used or the only loggers used are those that do not manage files stored in the
logs
folder.