
Application Manager
# P0602566 Ver: 1.5 Page 109
Introduction to Application Management
The APPMAN tool is the PeriView tool that is used to manage applications in the
network. Tree objects depict their state (up, down, unreachable), in near real-
time, by the color (green, red, black) of individual objects. You can assign
applications from the Application Management window.
When you launch the Application Management window, the applications that are
currently assigned to the domain displayed in the workspace are listed in the
Applications scrolling window. If you choose the action from a tree object to
which applications are assigned, information specific to the object displays in the
Locations scrolling window. The Applications, Locations, and Options display
areas are inactive until you select an Action.
You can control the order in which applications are assigned by manipulating the
Locations list. Applications are assigned in the order in which the selected
locations are listed. When you choose this action, the order of the Locations
listings, reflects the current default line start order. This information is stored in
the $MPSHOME/component_typeN/etc/aseLines.cfg
file.
When you reorder the list in this window, the new order applies only to the current
session. Each time this window is closed and reopened, the listing reflects the
default order (specified in the aseLines.cfg
file), not the order specified in
the previous session.
Application files and user shared libraries are copied from their source location to
the designated directories, on the node where they will process during the Assign
process. Executable files (*.vex) and configuration files (*.acfg) for all
applications (main and linked) are copied to the following locations (on the node
where they will process).
Solaris: $MPSHOME/component_typeN/apps
Windows 2000:%MPSHOME%\component_typeN\apps
User shared libraries (*.so or *.dll) will be copied to the following
locations:
Solaris: $MPSHOME/component_typeN/apps/lib
Windows 2000:%MPSHOME%\component_typeN\apps\lib
Application Configuration
An application’s executable and configuration files (*.vex and *.acfg) are
required to exist in the same directory before the application can be assigned to a
location. If you select an executable file a corresponding configuration file is not
detected, a notice box displays to inform you that a configuration file is created
before the assign process continues. Press OK to continue.
• If you selected a PeriProducer application, it is configured using the
values specified in the executable file (*.vex) and default values for all
options that have not been explicitly specified.
• Use the Terminate or Un-Assign Lines action to un-assign the
application.
• Open the Application Configuration window, modify the configuration
Comentarios a estos manuales