Руководство Пользователя для Cisco Cisco Customer Voice Portal 8.0(1)
C
HAPTER
5:
VXML Server
C
ONFIGURATION
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
CVP
VXML
S
ERVER
AND
C
ISCO
U
NIFIED
C
ALL
S
TUDIO
121
long, potentially causing memory issues. It is therefore highly recommended to keep the
default value of 30 seconds or to test the system should this value be changed.
default value of 30 seconds or to test the system should this value be changed.
•
convert_old_apps
– This tag defines whether to convert applications deployed from a version
of Call Studio that VXML Server detects is old (possible values are
true
and
false
). By
setting this configuration option to
true
, a deployed application can be copied to the
applications
directory of VXML Server without requiring the application to be re-
deployed from the latest version of Call Studio. Note that for new application settings, the
converter will choose default values. Also note that this converter is limited to converting the
XML files that define an application with regards to Call Studio and VXML Server and will
not convert any other files or Java classes for the application. By default this configuration
option is on.
converter will choose default values. Also note that this converter is limited to converting the
XML files that define an application with regards to Call Studio and VXML Server and will
not convert any other files or Java classes for the application. By default this configuration
option is on.
•
logger
– This tag acts as the parent tag for three additional tags having to do with loggers.
The first two tags,
<minimum_thread_pool_size>
and
<maximum_thread_pool_size>
define the minimum and maximum size of the thread pool that is used for handling logger
threads. The minimum thread pool size value can be any positive integer and the maximum
thread pool size value can be any positive number as long as it is greater than the minimum
thread pool size value. Note that if the maximum number of logger threads are used, VXML
Server will queue the logger events to be used when a thread becomes available so the data
will not be lost. Since these values affect thread usage, it is highly recommended that any
deviation from the default values (1 minimum / 500 maximum) be fully tested for any
complications. For example, if the maximum is set to a low value and the system encounters
high load, VXML Server could encounter a situation where the queued logger events
accumulate faster than the logger threads can handle them, leading to a scenario where the
application server runs out of memory. On the other hand, if the maximum value were set
too high and the system encounters high load the system on which VXML Server runs could
run out of threads to allocate, which could cause many other problems with the application
server as well as the operating system itself. Of all the VXML Server configuration options,
these two have the highest potential for causing major problems if misused.
The third child tag,
threads. The minimum thread pool size value can be any positive integer and the maximum
thread pool size value can be any positive number as long as it is greater than the minimum
thread pool size value. Note that if the maximum number of logger threads are used, VXML
Server will queue the logger events to be used when a thread becomes available so the data
will not be lost. Since these values affect thread usage, it is highly recommended that any
deviation from the default values (1 minimum / 500 maximum) be fully tested for any
complications. For example, if the maximum is set to a low value and the system encounters
high load, VXML Server could encounter a situation where the queued logger events
accumulate faster than the logger threads can handle them, leading to a scenario where the
application server runs out of memory. On the other hand, if the maximum value were set
too high and the system encounters high load the system on which VXML Server runs could
run out of threads to allocate, which could cause many other problems with the application
server as well as the operating system itself. Of all the VXML Server configuration options,
these two have the highest potential for causing major problems if misused.
The third child tag,
<keep_alive_time>
defines the amount of time in seconds that a thread
should be idle for before it is removed from the thread pool. This allows for the thread pool
size to shrink over time as logger volume decreases. This value allows for optimum thread
pool size based on the call volume. The default value is 30 seconds. It is recommended not to
change greatly from the default as too high a number will keep unnecessary resources around
and too low a number will reduce efficiency and defeat the purpose of using a thread pool
completely. Refer to Chapter 5: VXML Server Logging for more on logging.
size to shrink over time as logger volume decreases. This value allows for optimum thread
pool size based on the call volume. The default value is 30 seconds. It is recommended not to
change greatly from the default as too high a number will keep unnecessary resources around
and too low a number will reduce efficiency and defeat the purpose of using a thread pool
completely. Refer to Chapter 5: VXML Server Logging for more on logging.
•
debugger
– This tag defines the RMI registry port for the Call Studio debugger. This
configuration option is used only by VXML Server implementations used by Call Studio for
debugging purposes and should not be used in a production environment. The default is 8099
and the value can be any positive integer.
debugging purposes and should not be used in a production environment. The default is 8099
and the value can be any positive integer.
•
global_loggers
– This tag defines the global loggers to use within VXML Server.
Administrators can add additional global loggers as well as change or remove the loggers