Table 3-3. Control Types For Custom Actions - NEC Express5800/320Ma User Manual

2. Executable files for custom actions must be located
on a system disk. If a executable file is located on an
external or network disk, the Upgrade Side loses
access to the file while the system is in split mode.
3. For information about writing your own programs for
custom actions, see
Actions" on page
To configure a custom action
1. On the Custom Actions page, do one of the following:
•
Next to File, type the full path name and file name of the executable file you
want to run. (The file must already exist on the system.) For example:
C:\bin\mybatchfile.bat
•
Click Browse to locate the executable file using a file browser. Click the file
name in the file browser, then click Open to select the file.
2. Next to Arguments, type any arguments that you need to run with your executable
file.
No arguments are required; however, see
Actions" on page 3-15
environment variables to your executable file.
3. In the drop-down list for Control type, select the option that best describes when
the Active Upgrade console should execute your custom action, as described in
Table 3-3.

Table 3-3. Control Types for Custom Actions

Control Type
Start Application
Stop Application
Readiness Check
"Programming Notes for Custom
3-15.
for information about optionally passing Active Upgrade
Purpose
Executes the custom action whenever the Active Upgrade console
needs to start applications. For example, the console needs to restart
applications on the Upgrade Side when you merge the system.
Executes the custom action whenever the Active Upgrade console
needs to stop applications. For example, the console needs to stop
applications on the Upgrade Side when you split the system. It also
stops applications on the Production Side when you merge the
system.
Executes the custom action once during the
you initiate the Active Upgrade process. This control type allows you
to build your own verifications into the readiness check.
Configuring Custom Actions
"Programming Notes for Custom
readiness
Configuring the Active Upgrade Process
check, before
3-13