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

Stat 6.2 - 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

Point-to-Point PeopleSoft Project Migrations

If you want to migrate a PeopleSoft project that contains a large number of objects, but you do not necessarily want to spend the time required to archive all these objects, you can use Stat simply as a migrating tool by performing a point-to-point migration.

During a point-to-point migration, Stat uses CLI functionality to open PeopleSoft and migrate the objects in the project directly from the source environment to the target. Stat does not stage the objects and does not archive them. This means that while a record of the migration is recorded in Stat for reporting purposes, you cannot use Stat to roll back the migration since none of the objects in the project were archived.

To execute a point-to-point migration, you must add the project you want to migrate to a CSR and the CLI Auto-Migration option must be activated for both the source and target PeopleSoft database. For more information on activating CLI functionality, see the section, Setting Up Your PeopleSoft Connections .

To migrate a PeopleSoft project point-to-point:
1
Open the CSR that contains the project you want to migrate.
2
In the CSR window, select the Objects tab.
3
Open the Migration Path node in the tree view.
4
Click and drag from the source database to the target database.
This opens the Point To Point Migration Wizard.
5
(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.
* 
IMPORTANT: If Stat is unable to execute the migration at the scheduled time for whatever reason, (the workstation is turned off or the Auto Migration feature is deactivated), the migration will have a status of PS Pending until Stat either completes the migration or you migrate the objects manually.
6
(Optional) In the Description field, enter a unique description of the migration.
The field defaults to “Point-to-Point Migration.”
7
If there are more than one project associated with the CSR, select the project you want to migrate in the Projects field.
The Wizard displays all the objects sorted by object type that are contained in the selected project.
8
Click Migrate.
Stat invokes CLI functionality to open PeopleSoft and migrate the project directly from the source database to the target database.
When finished, Stat displays the Migration Console, which records the Point-to-Point archive migration. For more information, see Migration Console . Point-to-point migrations are also recorded in the Migration Details window, which is described in the section Migration Details Window on page 158.

Migrating Non-App Designer PeopleSoft Proprietary Objects

When Stat migrates PeopleSoft proprietary objects, it first moves copies of the archived objects into a staging database. Stat then creates a PeopleSoft project (called an Application Designer project), which contains references to the objects you just staged. However, there are PeopleSoft proprietary objects that cannot be included in an Application Designer project. For some of these objects, Stat provides an alternative form of migration support. These objects include:

•
Record Groups
•
Mass Change Templates
•
Mass Change Types
•
Mass Change Prompt Records
•
Mass Change Datetime Parms
•
Strings Table Programs
•
Import Definitions
•
nVision Scopes
•
TableSet Control
•
TableSet IDs
•
Object Security Groups

 

You archive non-Application Designer objects the same way you do other PeopleSoft proprietary objects. When you migrate them, however, Stat executes the following steps after the archived objects are moved to the staging database:

1
Stat dynamically creates DataMover export and import scripts and stores them in the user's Log Directory as defined in the Stat User Options window.
2
Using CLI functionality, Stat runs the export script using DataMover in the staging database. This creates a .dat file that contains the non-Application Designer object definitions in the user's Log Directory.
* 
IMPORTANT: To migrate non-Application Designer objects, you must activate CLI Auto Migrate functionality for each target environment.
3
Stat uses CLI functionality to run the import script in the target environment. This import script deletes the non-Application Designer object definitions contained in the target environment. Then it imports the data from the .dat file created by the export script. This data is then imported into the target environment.
If migrating to a distribution environment, Stat uses CLI functionality to execute the import script in each of the distributed environments.

Migration Approvals and Mass Migrations (PeopleSoft)

Stat provides advanced version control and change management support in the form of migration approvals and mass migrations:

•
Migration approvals provide a way for system administrators to maintain data integrity in PeopleSoft environments. Before you can migrate an archive set into an environment that requires migration approval, one or more authorized users must approve the migration.
•
Mass migrations allow a user to group multiple archive sets and migrate them as a single unit to the same environment. There are two ways to perform a mass migration, either by flagging individual archive sets as candidates for a mass migration, or by specifying an application release label assigned to certain archive sets within the service domain.

Marking Archive Sets for Migration

When you want to perform a migration that requires approval, or you want to flag an archive set for a mass migration, the first step is to mark the archive set for migration. This is done either by individually selecting the Ready to Migrate option on the Objects tab of the CSR window, and then selecting the environment(s) that you want to target, or by marking multiple archive sets in the Ready to Migrate window.

* 
NOTE: The security right, PS Archive Set - Ready to Migrate, allows you to mark an archive for a migration even if you do not have the user class rights to perform migrations. This way, users that have migration rights can migrate your archive set for you.
Marking Individual Archive Sets
To mark an archive set for a migration:
1
On the CSR the archive set belongs to, open the Objects tab of the CSR window. Then click Archive Sets.
2
In the Archive Set table, select Ready to Migrate for the archive set.
3
Save the CSR.
4
Click Migration Target.
This opens the Target Environments window. Here you can specify the environment(s) to which you want to migrate the archive set.
5
In the table on the right side of the window, select Migrate for each environment that you want to designate as a target environment.
* 
NOTE: In the table displayed in the right section of the Target Environments window, distribution environments and their associated distributed environments are designated by small blue and yellow icons, respectively. When you select Migrate for a distribution environment, all the environments on its distribution list are selected as well. Also, you cannot select a distributed environment without selecting its distribution environment as well.
6
Click Premigration List to view a checklist of any actions you should take before migrating the archive set.
For more information on pre migration steps, see the section, Pre and Post Migration Steps .
7
Click OK or Apply to save your work.
Once you click OK or Apply, the archive set appears in the Mass Migration window for the target environment, and the approval requests, if any, are generated and sent out to each user authorized to approve the migration.
* 
NOTE: If you later decide you do not want to migrate to a particular environment, deselect it in the Target Environments window. When you click OK or Apply, any approval requests that were generated the first time are deleted.
Marking Multiple Archive Sets

The Ready to Migrate window displays all the archive sets that have not yet been individually marked for migration and which share the same release label and environment on the migration paths of their respective CSRs. After you specify the target environment and release label, Stat retrieves all the qualifying archive sets that have not been marked for migration. Retrieved archive sets are marked for migration by default. You can unmark any archive set you do not want marked as Ready to Migrate.

To mark multiple archive sets for migration:
1
Select Migration Management | Archive Sets - Ready to Migrate.
2
In the Module field select the change management module you are using.
3
In the Service Domain field select the service domain of the archive sets.
4
In the Environment field select the migration target environment of the archive sets.
Stat retrieves archive sets that share the selected environment in the migration paths of their respective CSRs.
5
In the Release field select a release label.
Stat retrieves archive sets that have been assigned to that release. Release labels can be minor or major and are defined by system administrators.
* 
NOTE: A Minor release is considered a branch of its parent release. This means that when you select a minor release label, Stat retrieves all the archive sets assigned the parent release labels as well. For example, using a typical version sequence, if you select the release label 2.2.1, Stat also retrieves archive sets assigned its parent release labels, 2.2 and 2.0.
6
(Optional) Deselect Ready to Migrate for any archive set that you do not want to be marked for migration.
7
Click OK to save the archive sets as Ready to Migrate.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation