Cisco Cisco Unified Customer Voice Portal 10.0(1) Guía Del Usuario
C
HAPTER
3:
A
DMINISTRATION
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
C
ALL
S
ERVICES
,
U
NIVERSAL
E
DITION
AND
U
NIFIED
C
ALL
S
TUDIO
59
It is also possible for a developer to create their own custom MBeans for exposing functions or
information that will then be viewed by a JMX-compatible client alongside the MBeans exposed
by Call Services. See the Programming Guide for Cisco Unified Call Services, Universal Edition
and Unified Call Studio for more on creating custom MBeans.
information that will then be viewed by a JMX-compatible client alongside the MBeans exposed
by Call Services. See the Programming Guide for Cisco Unified Call Services, Universal Edition
and Unified Call Studio for more on creating custom MBeans.
Most JVMs do not start up with JMX enabled by default and require a parameter to be passed to
the JVM to turn it on (for example, Sun Microsystems JVMs require the parameter -
the JVM to turn it on (for example, Sun Microsystems JVMs require the parameter -
Dcom.sun.management.jmxremote
). Any change to the JVM parameters must be implemented
prior to the Java application server is started.
Once Call Services is started, a JMX client can then be launched and configured to point to the
machine on which Call Services runs, whether it be on the same machine or a remote one. Once
connected, the client provides a graphical interface for displaying the information and functions.
The client will be able to display information about the JVM itself and typically the Java
application server will publish its own set of MBeans. Call Services information will be
displayed where the MBeans are listed in its own “domain”. The domain is typically rendered in
a tree structure and will list global information and functions (i.e. information having to do with
Call Services itself) as well as information on the deployed voice applications. Detailed
explanations of the individual MBeans are provided in the following sections.
machine on which Call Services runs, whether it be on the same machine or a remote one. Once
connected, the client provides a graphical interface for displaying the information and functions.
The client will be able to display information about the JVM itself and typically the Java
application server will publish its own set of MBeans. Call Services information will be
displayed where the MBeans are listed in its own “domain”. The domain is typically rendered in
a tree structure and will list global information and functions (i.e. information having to do with
Call Services itself) as well as information on the deployed voice applications. Detailed
explanations of the individual MBeans are provided in the following sections.
To address security, JMX client consoles will request a user name and password if they attempt
to connect to a remote server (no user name or password is required to connect to a local Call
Services because the client already has access to the local system). These credentials can be
defined at installation time. Security is most important for the administration functions as they do
affect the live system and if misused could cause instability. Note that many JMX clients do not
provide role-based authentication, so once a user has successfully logged in, the user has access
to all information and the ability to run all administrator functions. Therefore it is recommended
to provide this user name and password only to designated administrators.
to connect to a remote server (no user name or password is required to connect to a local Call
Services because the client already has access to the local system). These credentials can be
defined at installation time. Security is most important for the administration functions as they do
affect the live system and if misused could cause instability. Note that many JMX clients do not
provide role-based authentication, so once a user has successfully logged in, the user has access
to all information and the ability to run all administrator functions. Therefore it is recommended
to provide this user name and password only to designated administrators.
Of the available administration interfaces, the JMX interface for Call Services provides the
greatest functionality and flexibility. It does, however, require the JVM to have JMX active and a
JMX-compatible client. It also has a higher risk and overhead due to this flexibility.
greatest functionality and flexibility. It does, however, require the JVM to have JMX active and a
JMX-compatible client. It also has a higher risk and overhead due to this flexibility.
Administration Scripts
Most of the administration functions and some of the information about Call Services are
provided via command-line scripts that can be executed by an administrator manually or an
automated system directly. The administrator scripts do not use the JMX interface described in
the previous section and are functional by default without requiring any configuration on the
administrator’s part. The included scripts act as the client. The scripts are provided in two forms:
batch scripts for Microsoft Windows (ending in
provided via command-line scripts that can be executed by an administrator manually or an
automated system directly. The administrator scripts do not use the JMX interface described in
the previous section and are functional by default without requiring any configuration on the
administrator’s part. The included scripts act as the client. The scripts are provided in two forms:
batch scripts for Microsoft Windows (ending in
.bat
) and shell scripts for Unix (ending in
.sh
).
Scripts are provided to execute global functions (on Call Services itself) or functions for
individual applications. The scripts used for global administrator functions are found in the
individual applications. The scripts used for global administrator functions are found in the