ATD2 10511 - Fuelsmanager Services; Fmsystemmanager; System Start-Up; System Shutdown

FuelsManager Services
ADM003GVAE1005 25
FuelsManager Services
FMSystemManager
FMSystemManager performs master initialization and scheduling for the
FuelsManager System. It starts up the previously mentioned server programs on
its local machine. In addition, it provides shared system resources (Coded
Variables, Modifiers, Engineering Units Strings, Products, Graphic File Names,
Help File Names, and up to 16 sets of User Defined String tables) and services
that are used by all FuelsManager programs.
Each machine contains FMSystemManager, which must be started before any
other FuelsManager program. FuelsManager can be set up to start
FMSystemManager manually or as a service. When started as a service,
FMSystemManager automatically starts when Windows opens. It also executes
under the SYSTEM account, so it is not necessary for a user to be logged into the
system for FMSystemManager to execute.
System Start-up
After loading and initializing the shared system resources, FMSystemManager
then starts up programs such as FMDataManager, FMCommManager,
ArchiveManager, and ReportManager. The selection of programs depends on the
local FuelsManager configuration. The startup mode of each program can be
configured using the FuelsManager Configuration application.
System Shutdown
Shutting down FMSystemManager closes all FuelsManager programs such as the
FMDataManager, FMCommManager, ArchiveManager, and the ReportManager.
System Resources
As mentioned previously, FMSystemManager manages certain system resources
that are maintained in files. These files may be managed independently on each
computer or cooperatively for a network of computers. The SERVER value under
HKEY_LOCAL_MACHINE\Software\FuelsManager in the registry controls this
functionality. System Manager accomplishes this by using either Independent
system files or Master system files.
Independent System Files
By default, the local computer independently maintains all system resource files.
The SERVER registry key contains the local computer system name.
Configuration changes are applied to the local files and are not visible to other
FuelsManager stations on a Local Area Network (LAN).
The default ‘Independent’ method is normally used for single computer
FuelsManager systems. This method is also used when interconnected systems
are using different languages or when the client computer is connected to the
main FuelsManager system using low-speed serial communications.
Master System Files
Under this method, a master server maintains multiple computer systems. The
SERVER registry key contains the master server’s computer name. All
configuration changes to shared resources are directed to the master server
instead of the local system.
During start-up, the FMSystemManager on each FuelsManager computer loads
system files. If the registry designates another computer as the server, a link to