Most voice applications will run without any changes on Blueworx Voice Response systems
that are configured as a single system image. State tables, prompts, or custom servers that
use application data (by, for example, playing or recording voice segments)
do not need to be aware of whether or not they are running on a single system image: they
will access that data in exactly the same way whether they are running on
a stand-alone Blueworx Voice Response system, on a client node, or on a database server node. However, you should consider the following points when you design a voice
application that will be run on a single system image:
- The LogEvent state table action causes application data to be
written to an AIX file on the node on which the event occurs. This file is
not shared in the single system image, so an application that processes this data for the
whole single system image will have to collect data from the log files on each node.
- If your voice application uses custom servers to access hardware or software
resources that cannot be made available in exactly the same way on all client
nodes of the single system image, your application must be able to handle any differences.
For example, if a telephone call cannot be directed to the particular node
that is known to have the resource required to process it, the voice application
may need to transfer the call to that node.
- Applications that play voice segments using prompts will perform better
in a single system image because such voice data may be cached locally on the client nodes,
and will not require voice data to be accessed using the network.
- Using uncompressed voice segments instead of compressed voice segments
will increase the network bandwidth required by a factor of 5, unless such
data has been cached using the prompt mechanisms and the segments are played
using prompts.