Cisco Cisco Customer Voice Portal 8.0(1) Developer's Guide

Deployment

It is up to the developer to set up the environment necessary to support the requests made by
VXML 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
VXML Server though the act of parsing XML and the details of using HTTP will add additional
overhead to the performance of VXML 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
VXML 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 VXML Server and therefore
take advantage of the graceful nature of VXML Server administration activity, while components
using the XML API are hosted on separate systems. Any changes made to system that would
affect the XML sent as response to VXML 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.

Programming Guide for Cisco Unified CVP VXML Server and Cisco Unified Call Studio Release 8.0(1)