Cisco Cisco Unified Customer Voice Portal 10.5(1) User Guide
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
59
admin
directory of VXML Server. The scripts used for individual application administration are
located in the
admin
directory of each application.
The provided scripts are primarily used to expose VXML Server functions to administrators such
as loading a new application, updating an existing application, suspending VXML Server, etc.
Some scripts provide information, such as the number of active simultaneous calls on the server.
This chapter describes in detail all available scripts and their functionality.
as loading a new application, updating an existing application, suspending VXML Server, etc.
Some scripts provide information, such as the number of active simultaneous calls on the server.
This chapter describes in detail all available scripts and their functionality.
Security is an important concern when it comes to administration functions that are access from
the command-line. There are several precautions Unified CVP sets up to allow only the
appropriate people access to these scripts. First, by providing scripts or batch files (as opposed to
through a graphical or web interface), the administrator must be logged into the machine in order
to access them. Therefore, accessing these programs is as secure as the remote login process
(such as SSH) and the permissions given to these scripts or the entire
the command-line. There are several precautions Unified CVP sets up to allow only the
appropriate people access to these scripts. First, by providing scripts or batch files (as opposed to
through a graphical or web interface), the administrator must be logged into the machine in order
to access them. Therefore, accessing these programs is as secure as the remote login process
(such as SSH) and the permissions given to these scripts or the entire
admin
folder. Secondly,
VXML Server will only accept commands from the local machine, so even scripts stored on one
machine cannot issue commands to an instance of VXML Server running on another machine.
These two precautions ensure that only authorized administrators can access these functions.
machine cannot issue commands to an instance of VXML Server running on another machine.
These two precautions ensure that only authorized administrators can access these functions.
Since the global administration scripts are stored in a different location from application scripts,
each directory can be assigned different permissions. That way an administrator can be given
access to the global administration scripts while still allowing the application scripts to be
accessed by voice application developers.
each directory can be assigned different permissions. That way an administrator can be given
access to the global administration scripts while still allowing the application scripts to be
accessed by voice application developers.
Finally, every administration script can be configured to ask for confirmation before the action is
taken, to prevent the accidental execution of the script. By default the confirmations are on. They
can be turned off by passing the command-line argument “noconfirm” to the script. This can be
useful if the administration scripts are executed by automated systems like cron jobs.
taken, to prevent the accidental execution of the script. By default the confirmations are on. They
can be turned off by passing the command-line argument “noconfirm” to the script. This can be
useful if the administration scripts are executed by automated systems like cron jobs.
While not as flexible as the JMX interface, administration scripts provide easy access to VXML
Server functions for both administrators and automated systems out of the box. The risk potential
is similar to that of the JXM interface although there is less overhead because JMX is not
enabled.
Server functions for both administrators and automated systems out of the box. The risk potential
is similar to that of the JXM interface although there is less overhead because JMX is not
enabled.
System Information Page
The system information page provides basic information about VXML Server including the
license information, the deployed gateway adapters and applications, the status of information on
the application server on which VXML Server is running, and some miscellaneous system and
Java information such as the version and memory usage. It does not provide the ability to
execute any functions, it is meant to be a quick way to check relevant information. It is also the
easiest of the three methods to obtain information because all that is needed is a web browser.
The system information page can be seen by pointing a web browser to the URL:
license information, the deployed gateway adapters and applications, the status of information on
the application server on which VXML Server is running, and some miscellaneous system and
Java information such as the version and memory usage. It does not provide the ability to
execute any functions, it is meant to be a quick way to check relevant information. It is also the
easiest of the three methods to obtain information because all that is needed is a web browser.
The system information page can be seen by pointing a web browser to the URL: