Avaya PeriView Reference Manual (Software Release 2.1) - Business Communications Manager Manual de usuario descargar pdf (Pagina 79)

Application Configuration

# P0602566 Ver: 2.7 Page 65

Introduction to Application Configuration

Use the Configure Applications tool to create the file that defines an application’s

execution parameters and run-time environment. For PeriProducer applications (a

generated .vex file), the configuration file (*.acfg) is copied, along with the

application’s executable file (*.vex), to the node where you assign the application.

Although you can assign an application with a default configuration file, you can use

this tool define individual configuration parameters.

For VoiceXML applications, the .acfg file is explicitly defined on the node (in the

appropriate component directory) on which it runs. See “Configure VoiceXML

Applications” on page 104.

Configurations Options

Configuration options are categorized as follows:

• Data Processing

• Host Communications

• Diagnostic

• Vocabulary

• Shared Libraries

• Execution Parameters

Although you can define configuration options within the application itself, when you

define these parameters in a configuration file, you can easily display and modify

them with this tool.

An application can execute in either IVR mode (voice) or Web mode (Internet),

depending upon the configuration parameters associated with the application.

File Requirements

Only a single configuration file can exist for an application at any one time. When you

redefine an application’s configuration, the existing file gets saved with new

information. For standard applications, the file names of an application’s

configuration file (*.acfg) and executable file (*.vex) differ only with respect to

the file extension.

During the assign process, if a configuration file is not located in the same directory as

the application’s executable file, the application is assigned with a default

configuration.

During the assign process, application files and user shared libraries are copied from

their source location to the designated directories on the node where they will process.

• Executable file (*.vex) and configuration files (*.acfg) for all applications

(main and linked) will be copied to the directory the following locations:

Solaris: $MPSHOME/componentN/apps

Windows 2000:%MPSHOME%\componentN\apps

• User shared libraries (*.so or *.dll) will be copied to the following

locations:

1 2 ... 74 75 76 77 78 79 80 81 82 83 84 ... 287 288

Sin comentarios

Avaya PeriView Reference Manual (Software Release 2.1) - Business Communications Manager Manual de usuario Pagina 79