NEC 320Fc - Manual (Page 65)

Configuring Custom Actions
Configuring the Active Upgrade Process 3-15
Custom actions run consecutively according to their timing options. Subsequent
custom actions do not start until the current custom action terminates.
5. Click Add to accept the custom action. (If the Add button is inactive, ensure that
you typed the File path name and file name correctly. The executable file must exist
to be added.)
You can view the custom actions you have created at the bottom of the Custom
Actions page. If you want to remove a custom action from the list, select it and click
Remove.
When you have finished specifying custom actions to run, or if you have no custom
actions to specify, you can click Next to proceed with the next configuration step.
Related Topics
•
“Programming Notes for Custom Actions”
•
“Selecting Application Services to Control” on page 3-9
• “Managing Critical Applications During the Upgrade Process” on page 2-6
• “Displaying the Upgrade Summary” on page 3-19
Programming Notes for Custom Actions
The following topics describe some of the features available for programming and
monitoring custom actions:
•
“Starting and Stopping Applications”
•
“Using Active Upgrade Environment Variables” on page 3-16
• “Generating Exit Values” on page 3-17
• “Viewing Standard Output and Error Stream” on page 3-17
•
“Executing Visual Basic Scripts and Other Types of Executable Files” on page 3-18
Starting and Stopping Applications
If you write a program to control a critical application during the upgrade process,
ensure that your program not only stops and starts the application at the appropriate
times, but also disables and enables the default startup mechanism for the application
(for example, the default Startup Type setting in the Services Control Manager or a
startup item in the system registry). If you do not disable the default startup type for an
application, it might interfere with or override your custom action.
See “Selecting Application Services to Control” on page 3-9 for information about how
the Active Upgrade console changes the Startup Type for application services.