Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario descargar pdf (Pagina 141)

Base System Configuration

# P0602477 Ver: 3.1.11 Page 141

The file extension (*.acfg) is appended to the application name when the file is

defined with the Application Manager—Configure Applications tool. If a

configuration file is not defined before an application is assigned, a default file is

created automatically during the Assign process. When the application is assigned, it

gets appended to the list in the aseLines.cfg file (see The aseLines.cfg File

on page 149). This list may be reordered with the Application Manager—Line Start

Order During Reboot tool.

The aseLines.cfg file looks for applications in the directory

$MPSHOME/mpsN/apps (%MPSHOME%\mpsN\apps). There are a number of

variables that may be defined within an application’s configuration (*.acfg) file,

some of which are illustrated in the following example (typical applications may have

more or less).

The file configured by means of PeriView’s Application Manager Configure

Application Tool (or created on Assign) is automatically generated and should not be

edited manually. For additional information about application management, refer to

the PeriView Reference Manual. For information about application development, see

the PeriProducer User’s Guide.

Example: <appname>.acfg

# This file is automatically generated by the application

# manager. Do not edit.

type=peripro

softTerm=600

args="-r -l 500 -k 600 -M 0 -h -D 128 -t 60 -o \"Please hold on.\"1

-C libpbisSYS.so -B /usr/lib/libc.so -B /usr/lib/ld.so "

interp=vengine

env=""

appmanFlags="-C is1:/home/peri/SHARED_LIBS_TEST/libpbisP.so -C

is1:/home/peri/SHARED_LIBS_TEST/libpbisSYS.so "

1 2 ... 136 137 138 139 140 141 142 143 144 145 146 ... 305 306

Sin comentarios

Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario Pagina 141