Cisco Cisco Customer Voice Portal 8.0(1) Veröffentlichungshinweis
C
HAPTER
16:
A
PPLICATION
M
ANAGEMENT
API
P
ROGRAMMING
G
UIDE FOR
C
ISCO
U
NIFIED
CVP
VXML
S
ERVER
AND
C
ISCO
U
NIFIED
C
ALL
S
TUDIO
R
ELEASE
7.0(1)
91
•
Installation Key
•
Licensed Ports
•
License Expiration Date
•
Licensed GW Adapters
VXML Server MBeans implement a Java API set that is defined for management interfaces.
Developers can create custom management beans that use the API. Figure 16-1 depicts the
relationship among the management API packages:
Developers can create custom management beans that use the API. Figure 16-1 depicts the
relationship among the management API packages:
com.audium.server.management
and the
built-in beans (which use the package
com.audium.server.management.mbean
) and custom
beans.
Figure 16-1
When VXML Server starts, all the beans that are deployed to
management
directory would be
loaded and registered to the JMX server. Depending on the base class it extends, a bean is
grouped in VoiceApplication, Global or Info under the domain “Cisco VXML Server
Application Management API”. For an application-scoped bean that either extends
grouped in VoiceApplication, Global or Info under the domain “Cisco VXML Server
Application Management API”. For an application-scoped bean that either extends
AbstractApplicationCommand
,
AbstractApplicationConfig
or
AbstractApplicationData
, a bean instance will be created for each application. For instance, if
bean A extends
AbstractApplicationCommand
and there are currently two applications
deployed: appA and appB, then two instances of bean A class will be created, one for appA, the
other for appB.
other for appB.
For a logger that has been deployed with an application, a management bean will be dynamically
generated and registered for it. Currently there is no extra requirement for a logger to become
manageable. However, the following operations are excluded from logger beans due to their
irrelevance with respect to managealibility:
generated and registered for it. Currently there is no extra requirement for a logger to become
manageable. However, the following operations are excluded from logger beans due to their
irrelevance with respect to managealibility:
log(), init(), equals(), destroy(),
initialize(), hasCode(), getClass(), wait(), notify(), notifyAll(),
toString()
.