
Application Manager — Overview
# P0602566 Ver: 2.7 Page 127
When you begin the Start or Restart Lines action from a selected tree object, it
displays with predefined application and locations information.
An application can execute in either IVR mode (voice) or Web mode (Internet),
depending upon the configuration parameters associated with the application.
Start and Restart Lines Progress
The rate at which applications are started or restarted displays to the screen in the form
of a Progress Box.
As the indicator bar progresses from 0–100%, the name of the application and the
location to which it is being assigned, started, or restarted displays in the window.
The Start and Restart Lines process can be halted by selecting Cancel.
Terminate or Unassign Action
Use the Terminate or Unassign Lines action to terminate applications and un-assign
them from the locations to which they had been assigned. You can terminate an
application without un-assigning it. The tree in the workspace indicates the most
current information about the domain.
When applications are assigned, they are associated with the user that launched the
Application Manager. Only that user (with the exception of root) is able to start,
restart, terminate, or un-assign that phone line.
Applications are terminated and unassigned in the order in which selected locations
are listed in the Locations scrolling window. The order of the Locations list reflects
the default line start order.
If applications have been assigned to locations subsequent to the list being reordered,
these applications are appended to the locations list.
File Maintenance
The Terminate and Unassign Lines actions provide an option for automatically
removing executable (*.vex), configuration (*.acfg) files when the last
occurrence of the application is un-assigned from a location. Linked applications and
shared libraries cannot be removed with this option because only those applications
that are assigned to phone lines display in the window.
During the assign process, application files and user shared libraries are copied from
their source location to the designated directories on the node where processing
occurs.
• Executable file (*.vex) and configuration files (*.acfg) for all
applications (main and linked) will be copied to the directory the following
locations:
Komentarze do niniejszej Instrukcji