NEC EXP320J, Руководство пользователя

Страница: 343 / 504

Installing and Using Utilities 5-125
Advanced Executes the custom action during every step of the Active Upgrade
process, including interim steps such as PrepareSplit and PrepareMerge,
which occur prior to the Split and Merge operations.
This control type allows you to have more precise control over a custom
action. Your executable will run each time the Active Upgrade process
switches states, but you can write a program with conditional statements
based on Active Upgrade environment variables to specify exactly when
and where particular tasks should be executed. For example, you can
write a conditional statement that will trigger only on the Upgrade Side if
the system is in merge mode.
If you have more than one custom action, the Advanced control type also
allows you to control the order in which the custom actions are executed
(step 4).
Backup Executes the custom action when the system is merged, allowing you to
back up files that were modified on the Production Side system disk while
the system was in split mode (before these files are lost during the commit
process).
4. If you selected the Advanced control type, optionally select an item from the Timing
drop-down list which best describes the order in which you want this custom action to run with
your other custom actions. The below table, “Timing for the Advanced Control Type”,
describes the timing options. If the timing does not matter, keep the
Default setting.
IMPORTANT:
The Timing will not affect the order in which custom actions run with other Active Upgrade tasks.
Use this option only if you want to ensure that one custom action runs before or after another
custom action.
Timing for the Advanced Control Type
Timing Purpose
Default Executes the custom action in the default, consecutive order.
Before Executes the custom action early in the list of custom actions, before items
marked as Default or After.
After Executes the custom action late in the list of custom actions, after items
marked as Before or Default.
Your custom actions will run consecutively according to their timing options. Subsequent custom
actions will not start until the current custom action terminates.