Cisco Cisco Unified Customer Voice Portal 10.0(1) Guía Del Usuario
C
HAPTER
2:
U
NIVERSAL
E
DITION
C
OMPONENTS IN
D
ETAIL
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
C
ALL
S
ERVICES
,
U
NIVERSAL
E
DITION
AND
U
NIFIED
C
ALL
S
TUDIO
37
Custom Say It Smart plugins can be constructed to read back formatted data not handled by
Universal Edition Say It Smart plugins, such as spelling playback or reading the name of an
airport from its three-digit code. Plugins can also be created to extend the functionality of
existing plugins, such as adding new output formats to play the information in another language.
For example, a plugin can define a new output format for the Universal Edition Date Say It
Smart plugin that reads back dates in Spanish.
Universal Edition Say It Smart plugins, such as spelling playback or reading the name of an
airport from its three-digit code. Plugins can also be created to extend the functionality of
existing plugins, such as adding new output formats to play the information in another language.
For example, a plugin can define a new output format for the Universal Edition Date Say It
Smart plugin that reads back dates in Spanish.
Refer to the Programming Guide for Cisco Unified Call Services, Universal Edition and Unified
Call Studio for a full description of the process of building custom Say It Smart plugins.
Call Studio for a full description of the process of building custom Say It Smart plugins.
Start and End of Application Actions
Universal Edition provides mechanisms to execute some code when an application is launched or
shut down. A start of application action is run when the Call Services web application archive
(WAR) starts up (which occurs when the application server first starts up or the application
server reloads the WAR), or the application is updated. An end of application action is run when
the application is updated, released, or the web application is shut down (which occurs if the
application server reloads or shuts down the web application or the application server itself is
shut down).
shut down. A start of application action is run when the Call Services web application archive
(WAR) starts up (which occurs when the application server first starts up or the application
server reloads the WAR), or the application is updated. An end of application action is run when
the application is updated, released, or the web application is shut down (which occurs if the
application server reloads or shuts down the web application or the application server itself is
shut down).
The purpose of the start of application action is typically to set up global data or application data
that would be accessed by components within the callflow. Since global and application data’s
lifetime is the lifetime of the application and they can contain Java objects, the start of
application action could even set up persistent database connections or other communications to
external systems that would remain connected as long as the application were running. Note that
should an error occur within the start of application class, the application deployment will
continue unchanged. The designer can specify that an error in a particular start of application
class should stop the application deployment. This would be done if the class performs
mandatory tasks that are necessary for the application to run correctly.
that would be accessed by components within the callflow. Since global and application data’s
lifetime is the lifetime of the application and they can contain Java objects, the start of
application action could even set up persistent database connections or other communications to
external systems that would remain connected as long as the application were running. Note that
should an error occur within the start of application class, the application deployment will
continue unchanged. The designer can specify that an error in a particular start of application
class should stop the application deployment. This would be done if the class performs
mandatory tasks that are necessary for the application to run correctly.
The purpose of the end of application action would be to clean up any data, database
connections, etc. that would no longer be needed once the application is shut down. Note that the
end of application action is called even when the application is updated because the update may
have changed the data that is needed by the application.
Every application deployed on Call Services has the ability to define any number of start and end
of application actions that are executed in the order in which they appear in the application
settings.
connections, etc. that would no longer be needed once the application is shut down. Note that the
end of application action is called even when the application is updated because the update may
have changed the data that is needed by the application.
Every application deployed on Call Services has the ability to define any number of start and end
of application actions that are executed in the order in which they appear in the application
settings.
Loggers
The act of logging information about callers to the system is performed by loggers. An
application can reference any number of loggers that “listen” for logging events that occur.
These events range from events triggered by a call, such as a caller entering an element or
application can reference any number of loggers that “listen” for logging events that occur.
These events range from events triggered by a call, such as a caller entering an element or