NEC Express5800/R320a-E4 User Manual page 301

5. Click Add to accept the custom action. (If the Add button is inactive, ensure that you typed the
File path name and executable 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.
TIPS:
Programming Notes for Custom Actions, page 5-141
Selecting Application Services to Control, page 5-134
Managing Critical Applications During the Upgrade Process, page 5-109
Displaying the Upgrade Summary, page 5-146
Programming Notes for Custom Actions
The following topics describe some of the features available for programming and monitoring
custom actions:
•
"Starting and stopping applications" on this page
•
"Using Active Upgrade Environment Variables" on page 5-142 "Generating Exit Values" on
page 5-143
•
"Viewing Standard Output and Error Stream" on page 5-143
•
"Executing Visual Basic Scripts" on page 5-144
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 5-134 for information about how the
Active Upgrade Console changes the Startup Type for application services.
TIPS:
Programming Notes for Custom Actions, page 5-141
Configuring Custom Actions, page 5-138
Installing and Using Utilities 5-141