Cisco Cisco Unified Customer Voice Portal 11.0(1) User Guide
C
HAPTER
3:
A
DMINISTRATION
C
ISCO
CVP
V
OICE
XML
User Guide
Administrator Functions
Server provides several mechanisms to perform maintenance while minimizing any detrimental
effects on callers. These functions are designed to allow an administrator to make both small and
large changes to one or more applications while Server is still handling callers. They are divided
into two categories: those that affect a specific application and those that affect all applications
running on Server.
effects on callers. These functions are designed to allow an administrator to make both small and
large changes to one or more applications while Server is still handling callers. They are divided
into two categories: those that affect a specific application and those that affect all applications
running on Server.
The user performs these administrative functions by running batch files (.bat) on Windows. The
scripts used for individual application administration are located in the
scripts used for individual application administration are located in the
admin
directory of each
application. The scripts used for global administrator functions are found in the
admin
directory
of Server.
Each administrator function updates a log file specifically used to track administrator activities.
This file exists for audit purposes. The administrator can use the log to determine when certain
actions took place or how long certain conditions existed.
This file exists for audit purposes. The administrator can use the log to determine when certain
actions took place or how long certain conditions existed.
Security
Security is an important concern when it comes to administration functions that can affect one or
all voice applications. There are several precautions Cisco CVP VoiceXML 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 a
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
all voice applications. There are several precautions Cisco CVP VoiceXML 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 a
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, Server will only accept commands from the local machine, so even scripts stored on
one machine cannot issue commands to an instance of the Server running on another machine.
These two precautions ensure that only authorized administrators can access these functions.
one machine cannot issue commands to an instance of the 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 run 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 run by automated systems like cron jobs.
©2000 - 2005 Audium Corporation. All Rights Reserved. 1/14/05
49