Configuring Custom ActionsConfiguring the Active Upgrade Process 3-132. Executable files for custom actions must be locatedon a system disk. If a executable file is located on anexternal or network disk, the Upgrade Side losesaccess to the file while the system is in split mode.3. For information about writing your own programs forcustom actions, see “Programming Notes for CustomActions” on page 3-15.To configure a custom action1. 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 youwant 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 filename 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 executablefile.No arguments are required; however, see “Programming Notes for CustomActions” on page 3-15 for information about optionally passing Active Upgradeenvironment variables to your executable file.3. In the drop-down list for Control type, select the option that best describes whenthe Active Upgrade console should execute your custom action, as described inTable 3-3.Table 3-3. Control Types for Custom ActionsControl Type PurposeStart Application Executes the custom action whenever the Active Upgrade consoleneeds to start applications. For example, the console needs to restartapplications on the Upgrade Side when you merge the system.Stop Application Executes the custom action whenever the Active Upgrade consoleneeds to stop applications. For example, the console needs to stopapplications on the Upgrade Side when you split the system. It alsostops applications on the Production Side when you merge thesystem.Readiness Check Executes the custom action once during the readiness check, beforeyou initiate the Active Upgrade process. This control type allows youto build your own verifications into the readiness check.
