Cisco Cisco Unified Customer Voice Portal 10.0(1) Guía Del Usuario
C
HAPTER
7:
S
TANDALONE
A
PPLICATION
B
UILDER
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
C
ALL
S
ERVICES
,
U
NIVERSAL
E
DITION
AND
U
NIFIED
C
ALL
S
TUDIO
122
Chapter 7: Standalone Application Builder
Normally a designer builds an application in Call Studio and then deploy to Call Services. Call
Studio has the ability to deploy an application locally as well as to a remote system via FTP.
Deploying an application becomes more difficult in an environment where many designers are
working on a single application or when the enterprise follows a strict deployment policy to the
runtime servers. In the first scenario, multiple designers are adding content to a source repository
system and no single designer may have the full application in necessary to perform the
deployment and even if possible, would require coordination among all designers involved. In
the second scenario, the production environments do not allow direct access via FTP and require
an automated system to place new content on to those environments, providing the flexibility to
control exactly how and when the content is deployed. The desire is to extract the ability to
create a Call Services application from the Call Studio project without requiring a person to
launch Call Studio and deploy.
Studio has the ability to deploy an application locally as well as to a remote system via FTP.
Deploying an application becomes more difficult in an environment where many designers are
working on a single application or when the enterprise follows a strict deployment policy to the
runtime servers. In the first scenario, multiple designers are adding content to a source repository
system and no single designer may have the full application in necessary to perform the
deployment and even if possible, would require coordination among all designers involved. In
the second scenario, the production environments do not allow direct access via FTP and require
an automated system to place new content on to those environments, providing the flexibility to
control exactly how and when the content is deployed. The desire is to extract the ability to
create a Call Services application from the Call Studio project without requiring a person to
launch Call Studio and deploy.
Universal Edition provides a tool to support this requirement named the Standalone Application
Builder. It is packaged with Call Studio and allows for the deployment of an application through
a command-line interface. By exposing this as a command-line tool, an administrator can
integrate this tool into any process that has the ability to execute scripts. For example, the
administrator can configure a crontab to launch this utility every day with the latest content
checked into a source repository. Another example is to modify existing build and deploy Ant
scripts to deploy the application once all other components such as elements, grammars, etc. are
assembled.
Builder. It is packaged with Call Studio and allows for the deployment of an application through
a command-line interface. By exposing this as a command-line tool, an administrator can
integrate this tool into any process that has the ability to execute scripts. For example, the
administrator can configure a crontab to launch this utility every day with the latest content
checked into a source repository. Another example is to modify existing build and deploy Ant
scripts to deploy the application once all other components such as elements, grammars, etc. are
assembled.
This chapter explains what the Standalone Application Builder does and how to use it.
Standalone Application Builder Introduction
The Standalone Application Builder is a utility that deploys a studio application project to a
format that is required by Call Services. It is launched via a batch script (for Windows) named
format that is required by Call Services. It is launched via a batch script (for Windows) named
buildApp.bat
or shell script (for Linux) named
buildApp.sh
.
The Standalone Application Builder is bundled with Call Studio as a ZIP file in the folder XXX.
The archive can be unzipped on to any location and is completely independent of Universal
Edition software Additionally, there is no license required to use the utility. Only the following
32-bit operating systems are supported: Microsoft Windows XP, Microsoft Windows Vista, and
Red Hat Enterprise Linux WS 4 for x86.
The archive can be unzipped on to any location and is completely independent of Universal
Edition software Additionally, there is no license required to use the utility. Only the following
32-bit operating systems are supported: Microsoft Windows XP, Microsoft Windows Vista, and
Red Hat Enterprise Linux WS 4 for x86.
When launched, the Standalone Application Builder will first validate the Call Studio project to
ensure it is a valid application, and if successful, deploys the Call Services version of the
application to the destination folder. If there are validation errors, those errors are displayed in
the output similar to validation errors that are displayed in Call Studio. The tool only deploys a
single application at a time. To deploy multiple applications, the script can be called repeatedly
pointing to different projects.
ensure it is a valid application, and if successful, deploys the Call Services version of the
application to the destination folder. If there are validation errors, those errors are displayed in
the output similar to validation errors that are displayed in Call Studio. The tool only deploys a
single application at a time. To deploy multiple applications, the script can be called repeatedly
pointing to different projects.