Cisco Cisco Customer Voice Portal 8.0(1) Guida Dello Sviluppatore
C
HAPTER
2:
C
ISCO
U
NIFIED
CVP
API
I
NTRODUCTION
V
OICE
XML
P
ROGRAMMING
G
UIDE
FOR
C
ISCO
U
NIFIED
C
USTOMER
V
OICE
P
ORTAL
R
ELEASE
4.0(1)
10
Notes:
child1 is allowed to appear multiple times because it has a * next to it. One child1 tag does
not have an attribute because it is optional. Additionally, since these tags do not encompass
any additional content, the tag is closed with a “/>” so there is no need for a closing tag.
any additional content, the tag is closed with a “/>” so there is no need for a closing tag.
child2 contains its two child tags. The another_child1 and another_child2 tags encapsulate
text so they have an open and close tag. another_child1 must specify its required attribute.
child3 can be omitted because it is optional.
child4 contains any number of its child tags in any order. It would be a syntax error to not
child4 contains any number of its child tags in any order. It would be a syntax error to not
include any child tags at all since at least one is required.
The order in which the child tags of parent must conform to the diagram. If child4, for
example, appeared before the child1 tag, that would be a syntax error.
Deployment
It is up to the developer to set up the environment necessary to support the requests made by
Unified CVP VoiceXML Server. Since the API is accessed over HTTP, the XML content must
be served by a web or application server. This content could potentially be served on the same
machine as Unified CVP VoiceXML Server though the act of parsing XML and the details of
using HTTP will add additional overhead to the performance of the VoiceXML Server. To get
the best performance, the setup should consist of a separate system handing the requests on the
same subnet as the machine on which the VoiceXML Server is installed. Maintaining the two
systems on the same subnet will reduce any network overhead as well as allow the administrator
to restrict communication to occur only within the same subnet.
Unified CVP VoiceXML Server. Since the API is accessed over HTTP, the XML content must
be served by a web or application server. This content could potentially be served on the same
machine as Unified CVP VoiceXML Server though the act of parsing XML and the details of
using HTTP will add additional overhead to the performance of the VoiceXML Server. To get
the best performance, the setup should consist of a separate system handing the requests on the
same subnet as the machine on which the VoiceXML Server is installed. Maintaining the two
systems on the same subnet will reduce any network overhead as well as allow the administrator
to restrict communication to occur only within the same subnet.
Keep in mind that unlike Java, changes made to components using the XML API are not
graceful. Components using the Java API are deployed on top of Unified CVP VoiceXML
Server and therefore take advantage of the graceful nature of the VoiceXML Server
administration activity, while components using the XML API are hosted on separate systems.
Any changes made to a system that would affect the XML sent as response to VoiceXML Server
requests would be available immediately. The administrator must ensure that maintenance
activity be performed on both systems to ensure callers do not experience changes within a
single phone call. A recommended method for handling updates to applications using
components using the XML API is to suspend the application before changes are made to the
server hosting the XML.
graceful. Components using the Java API are deployed on top of Unified CVP VoiceXML
Server and therefore take advantage of the graceful nature of the VoiceXML Server
administration activity, while components using the XML API are hosted on separate systems.
Any changes made to a system that would affect the XML sent as response to VoiceXML Server
requests would be available immediately. The administrator must ensure that maintenance
activity be performed on both systems to ensure callers do not experience changes within a
single phone call. A recommended method for handling updates to applications using
components using the XML API is to suspend the application before changes are made to the
server hosting the XML.