![](/images/new-backgrounds/1103032/103032125x1.webp)
Configuring Custom Actions
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 “Programming Notes for Custom 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 “Programming Notes for Custom Actions” on page
3.In the
Table 3-3. Control Types for Custom Actions
Control Type | Purpose |
|
|
Start Application | 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. |
|
|
Stop Application | 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. |
|
|
Readiness Check | Executes the custom action once during the readiness check, before |
| you initiate the Active Upgrade process. This control type allows you |
| to build your own verifications into the readiness check. |
|
|
Configuring the Active Upgrade Process