(Deprecated) Performing offline installation steps separately
To perform each step of process application installation separately, you can run the following commands individually or add them to a batch file or script. Doing so enables you to perform customization tasks between the installation steps.
For each of the following commands, you must specify the name of the installation package.
| Batch command | Script command | Description |
|---|---|---|
| importProcessAppPackage.bat | importProcessAppPackage.sh | Imports the installation package (.zip file) so that all library items within it are available for customization or alteration by way of custom scripts or the process application's installation service. |
| customProcessAppPreInstall.bat | customProcessAppPreInstall.sh | Runs any commands that you add. You can add commands that you want to run immediately before the process application snapshot is installed (using installProcessAppPackage) on the offline process server. |
| executeProcessAppInstallationService.bat | executeProcessAppInstallationService.sh | Runs the installation service for each referenced toolkit and then runs the installation service for the process application. |
| migrateProcessAppGlobalData.bat | migrateProcessAppGlobalData.sh | Migrates data such as teams, exposed process values (EPVs), and environment variables to the new snapshot version that you are installing. The process server migrates data according to the rules outlined in Strategies for migrating instances. |
| migrateProcessAppInstances.bat | migrateProcessAppInstances.sh | Migrates currently running process instances according to the migration option chosen when the installation package was created. Migrating instances describes the migration options. If other snapshot versions are not discovered, migration does not occur. |