In this window, you can deactivate any environment you do not want to include in a migration. This way, when you migrate an archive set to a distribution environment, Stat migrates the objects only to the active environments in the distribution list. To deactivate all the environments, click Set All Inactive. If you want to reactivate an environment, you can do so at any time by selecting the Active check box, or if you want to reactivate all the environments, click Set All Active.
For more information see “PeopleSoft Environment Migration Path Maintenance,” in the Stat System Administration Guide, Chapter 5, “Service Domain- Specific Maintenance.”
Also, Stat displays a warning message if it successfully completes a migration to a distribution environment but not to one or more of its associated environments (which would be the case if, for example, the password to one of the environments was incorrect). This information is also displayed in the Migration Details window. For more information, see Documenting Migrations (PeopleSoft) .
2 |
3 |
(Optional) To plan the migration for an unspecified date, clear the Migration Date check box. Planned migration can be initiated any time later by Stat Windows Client or by an external third party component using a REST API call. See “Appendix: Stat REST Web Services API” in the Stat System Administration Guide. |
4 |
(Optional) In the Description field, enter a unique description of the migration. |
5 |
(Optional) Select the Stop on Error option if you want the Stat Central Agent to terminate the migration at the first error it encounters. |
6 |
(Optional) De-select the E-mail Notification option if a business rule or personal rule triggered by a migration event has been defined for the service domain and you do not want Stat to send email notifications that may be triggered by the migration. |
9 |
(Optional) In the Migrate column, de-select the individual objects you do not want to migrate. |
11 |
If the archive set contains file objects and the target environment is Development, in the Migrate files to field select one of the following options: |
• |
Development Env– Select if you want to place the file objects in the source file locations of the Development environment |
• |
Working – Select if you want to place the file objects in the developers’ working directories. Only the file objects assigned to each developer get copied into their working directories. |
• |
Dev & Working – Select if you want to place the file objects in both the source file locations and the working directories. |
IMPORTANT: If the Development environment is a distribution environment and the archive set has both PeopleSoft proprietary objects and file objects selected for the migration, the option Working cannot be selected. To migrate file objects to Working, deselect the DB Objects option. |
13 |
(Optional) If CLI Auto Migrate has been enabled for the target environment, deselect the Auto Migration if for some reason you do not want Stat to auto-migrate the PeopleSoft proprietary objects. |
• |
Stat defined project - Select this option if you want Stat to assign a name to the project. Stat-defined project names always use the naming convention, “ST######.” |
• |
User defined project - Select this option if you want to assign a name to the PeopleSoft project. Then in the Project Name field enter the name you want. |
• |
Project in Archive Set - Select this option if you added a project definition to the archive set and want to re-use the project name. This option is only available if the archive set and the project definition included in the archive set reference all the same App Designer objects. This also applies to subobjects, meaning the option is not available if the parent objects have been removed either from the archive set or the project definition included in the archive set. The project definition included in the archive set can reference subobjects so long as the subobjects' parents are in the project definition and the archive set. For more information on subobjects, see Associating Related PeopleSoft Proprietary Objects . |
• |
Reuse project - Select this option if you are migrating an archive set that was previously migrated using the same staging database, and you have not modified the archive set after its original migration. If you select this option, by default Stat restages the project in the staging database. However, you can de-select the Restage objects option if you do not want to wait for the objects to be restaged and you are sure they were staged successfully the last time. |
IMPORTANT: If you selected the Project in archive set option, you cannot modify the settings in the Upgrade Options window. |
16 |
Click Migrate. |
18 |
After selecting the pre and post migration steps, click the Migrate button. |
If the CLI Auto-Migration feature has been enabled for the target environment (and you did not de-select the Auto Migration option), Stat launches PeopleSoft and tells PeopleSoft to copy the project from staging to target via a command line interface. While this is happening, you may see Application Designer login screen flash on your screen momentarily. For non-App Designer objects, Stat executes the DataMover import script. For more information on CLI options, see Setting Up Your PeopleSoft Connections .
If the CLI Auto-Migration feature has not been activated, or if an error or warning occurs during the auto-migration, you must perform the migration manually by logging into the staging database and pushing the project into the target environment. If CLI-Open is configured for the staging environment, Stat opens App Designer in the staging database for you. For more information, see Manually Migrating PeopleSoft Projects .
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center