Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Stat 6.3 - User Guide

Introduction to Stat Connecting to Stat Change/Service Requests Stat Consoles Tasks and Time Entries Stat Projects Search Engines Reports and Graphs Personal Rules Object Tools and Wizards Change Management for PeopleSoft
Object Management (PeopleSoft) Object Archives (PeopleSoft) Object Migrations (PeopleSoft)
Change Management for Oracle Applications
Object Management (Oracle Applications) Patch Management Object Archives (Oracle Applications) Object Migrations (Oracle Applications)
Change Management for Generic Applications
Object Management (Generic Applications) Object Archives (Generic Applications) Object Migrations (Generic Applications)
Appendix: Troubleshooting Chart Appendix: Migration Options Appendix: User-Specific Parameters Appendix: Supported PeopleSoft Proprietary Objects Appendix: Stat Reports

Mass Migrating Objects

If you need to migrate several archive sets to the same environment, rather than migrate them one at a time, you can perform a mass migration. There are two types of mass migration supported by Stat:

•
Using the Ready to Migrate method, you can include as many archive sets from different CSRs in a mass migration as you want, even if the objects are assigned to different developers and come from different source environments.
•
Mass migrating archive sets based on an application release label allows you to quickly update a target environment with the latest version of objects or roll back to earlier versions.

Because mass migrations can include objects assigned to different users and belonging to different CSRs, it is recommended that a limited number of users be allowed to perform mass migrations. With proper security, users can perform mass migrations that override workflow rules and approval requirements. In addition, Stat features the Release Recovery window, which allows users to perform application release mass migrations that override workflow rules, approval requirements, and object locks. For more information on the Release Recovery window, see Object Tools and Wizards .

To perform a mass migration:
1
Mark each archive set for a migration, as described earlier in this chapter.
2
Select Migration Management | Mass Migration.
Stat opens the Mass Migration window.
* 
TIP: You can resize the window and the panels as needed to view the complete listing of archive sets and objects.
3
(Optional) If you want the Stat Central Agent to process the migration job at some later time, enter the date and time in the Migration Date field.
The field defaults to the current date and time. You can schedule the migration up to 90 days in the future.
4
(Optional) In the Description field, enter a unique description of the migration.
The field defaults to “Mass 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.
System administrators may set this option to be selected or de-selected by default.
6
In the Module field select Generic Applications.
* 
TIP: You can set a default value to be displayed in the Module field. To do this, select User Options | Stat Options. Then in the Stat User Options window, select the value you want in the Default Module field.
7
In the Service Domain field, select the service domain associated with the migration path containing the target environment you want.
The service domain you select filters the list of target environments as well as the list of release labels if you opt to mass migrate objects assigned the same release label.
8
In the Target field select the environment to which you want to migrate the archive sets.
If using the Ready to Migrate method, Stat displays a list of each archive set that has been marked as Ready to Migrate into the selected environment.
9
In the Type field select one of the following:
•
Select Ready to Migrate if you want to mass migrate archive sets that have been individually marked for migration
•
Select Migration by Release if you want to mass migrate archive sets that have been assigned the same application release label. When you select this option, the Release field is displayed. Then in the Release field select the release label you want. Release labels can be minor or major and are defined by system administrators. After you select a release label, Stat displays a list of archive sets that have been assigned that label.
* 
NOTE: A Minor release is considered a branch of its parent release. This means that when you mass migrate archive sets based on a minor release label, Stat migrates all the archive sets assigned the parent release labels as well. For example, using a typical version sequence, if you mass migrate archive sets labeled release 2.2.1, Stat also migrates archive sets assigned its parent release labels, 2.2 and 2.0. When the same object is found in archive sets with different release labels, Stat migrates the object with the latest release label.
10
(Optional) In the Sources section, deselect Migrate for each archive set that you do not want to include in the mass migration.
By default, this check box is selected for each archive set that has met migration approval requirements.
* 
NOTE: Using the Ready to Migrate method, if the same object exists in two or more archive sets, Stat displays a message box prompting you to select which object you want to migrate.
11
(Optional) In the Archive Migr Order column, change the order in which selected archive sets will be migrated.
By default, Stat assigns archive sets a migration order number. The first archive set is assigned the order number 1, the second 2, and so on. You can change this order by assigning your own order numbers. Lower order numbers are migrated first.
With the proper security rights, you can exclude certain object classes from the migration. You can also exclude individual objects. If the same object is contained in more than one archive set, the most recently archived version is selected by default in the Migrate column. You can override this selection by selecting a different version.
12
(Optional) Deselect the class of objects (file objects or database objects) you do not want to migrate.
13
(Optional) In the Migrate column, deselect the individual objects you do not want to migrate.
If you are migrating to a distribution environment, the window displays the list of active target environments. By default, each environment in the distribution list is selected as a target. However, with the appropriate security rights, you can exclude certain environments from the migration.
14
(Optional) If migrating to distribution environment, deselect any environment in the list of active target environments you want to exclude from the migration.
15
Click Migrate>.
At this point, Stat prompts you to perform the pre-migration steps (if any) that have been defined for the target environment or for the objects or object types in the archive set.
16
Complete any required pre-migration steps.
For more information, see Pre and Post Migration Steps .
After completing the pre-migration steps, Stat opens the CSR Migrations Console, which shows that the migration job has been submitted to the Stat Central Agent. The Agent either begins processing the migration immediately, or if you scheduled the migration, at the date and time you specified. For more information, see Migration Console .
Mass Migrating to a Distribution Environment

Keep in mind the following when mass migrating to distribution environments:

•
When you flag a distribution environment for migration, all of the distributed environments are automatically flagged for migration as well.
•
When you mass migrate to a distribution environment, the objects are migrated to all the active environments in the distribution list.
•
You can only mass migrate to a distributed environment by migrating to the distribution environment. After migrating to a distribution environment, the distribution environment and distributed environments are no longer flagged for migration, even if some of them were not included in the migration.
•
The distribution environments can be on different migration paths

The mass migration cannot proceed for the following situations:

•
The selected archive sets have different distribution environment types for their target environments (One is ‘Yes’, the other is ‘—’).
•
When distribution environments are selected, the distribution environments have different distributed database lists
•
The migration has not received all the necessary approvals. If a distributed environment requires user approvals before a migration can take place, and one or more of the archive sets did not get necessary approvals, none of the archive sets included in the mass migration will be migrated into that environment. Stat only migrates to the distributed environments that either do not require approvals or have received approvals for each archive set included in the mass migration.

If any archive set is causing errors when mass migrating, you can opt not to include that archive set in the mass migration. You can then mass migrate the other archive sets and resolve the issue at a later time.

Documenting Migrations (Generic Applications)

After creating and migrating a base, interim, and final archive set, your migration path may look like this:

The sample migration path above shows:

•
The migration path has 5 environments
•
At least 3 archive sets have been created: 1 base, 1 final, and at least 1 interim
•
The base archive set was migrated to Development 8.0 from Prod 8.0
•
An interim archive was created in Development 8.0 and migrated to QA 8.0
•
The final archive was created from Development 8.0 and migrated to Test 8.0
•
No archive sets have been migrated to Train 8.0 or Prod 8.0

Flag Indicators

Flags appear to the right of environment graphics and indicate that an archive set was created in that environment. Flags include ‘B’ for base, ‘I’ for interim, and ‘F’ for final. If multiple interim archive sets were created in an environment, only one ‘I’ flag is shown.

Migration Indicators

When you migrate an archive set, the target environment graphic appears to fill up. When you migrate an interim archive set, the environment graphic appears half full, and the color changes. When you migrate the final archive set, the environment graphic appears full and the color changes again. Migrating the final archive set fills up both the source and target environments. Also, the graphic for the source environment of the final archive set reads “final src.”

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation