ExpressCluster X 2.0 for Windows Reference Guide - Nec

Section I Detailed functions of ExpressCluster
Starting the applications or services (armload command)
Notes (1) This command can be specified only in scripts.
(2) When you start the application with GUIs without specifying an
account, select Allow service to interact with desktop on the
ExpressCluster Server service. When not selected, GUIs of the
application are not displayed.
(3) When you specify a user account, it should have “local logon”
permission. For information on the user permissions, see the help of
the domain user administrator.
When you specify the domain of an account explicitly, specify the
following. Note that the domain name and the user name should be
within 15 characters.
When the account is a local administrator:
armload watchid /u administrator ap.exe
When the account is a domain\administrator:
armload watchid /u domain\administrator ap.exe
(4) When you use the monitoring function (/M option) of the
ARMLOAD command, specify Dr. Watson (DRWTSN32.EXE) as
a default debugger used by the operating system.
To check this setting, go to the registry
\\HKEY_LOCAL_MACHINE\Software\Microsoft\
Windows NT\CurrentVersion\AeDebug
and find the value with the name “Debugger” or “Auto.”
Check if the value of “Auto” is set to 1, and “Debugger” to
“DRWTSN32.”
When the setting values are different from those, change the settings
to use Dr.Watson in addition to the default debugger you are using.
For this setting, start Dr.Watson by running the drwtsn32 –i
command on the command prompt.
At OS installation, the value of “Auto” is set to 1, and “Debugger”
to “DRWTSN32.”
(5) Applications not suitable for ARMLOAD monitoring function
The applications whose processes do not stay resident persistently
are not suitable for the process monitoring (*). Since the process
monitoring is assumed to monitor processes that stay persistently
and do not terminate by themselves, it determines that an error
occurs on an application when the started process is terminated.
(*) The following applications are examples:
An application whose process started by ARMLOAD does not stay
resident persistently
An application whose process started by ARMLOAD starts its child
process, and the process started first does not stay resident
persistently (ARMLOAD only monitors the process it started)
(6) The application that requires GUIs may be terminated when it is
started by the ARMLOAD command and logged off. To prevent the
application from being terminated, start it with an account (/U
option).
341