Hello fellow Stat Technical Users and Administrators,
This guide will look at Point-to-Point migrations and why you may want to consider them for you larger PeopleSoft Project migrations.
The Point-to-Point (P2P) Migration is utilized for large PeopleSoft project’s where you are less concerned about archiving and recovery. An example of this may be for patches, or Tax Updates, which begin in your PS Demo environment and there are little to no customizations to the patch. Since you’ve not changed the patch, you need not worry about archiving those changes. The goal is simply to move the large amount of objects from the Source to the Target environments.
How Does the Point-to-Point Migration Work?
The Point-to-Point (P2P) Migration occurs on the same Object Management tab that you are accustomed too. Two major differences exist between a normal drag-n-drop migration and Point-to-Point migration:
1. Stat does not “Stage” the objects to the Staging Database.
2. Stat does not archive the objects in the Stat Repository.
The execution difference between a standard migration and a P2P migration is how the migration is initiated. On a standard migration you select the code set on the right side of the screen and drag-n-drop it to the left side target environment.
For a P2P migration, all activity happens on the left side of the screen, highlighted below in Green.
In the above screenshot, we would select the “HRDMO” icon in the left side window and drag directly down to the HRDEV environment. The way to tell the difference between the types of migrations you are doing is the icon that is displayed during the drag-n-drop process.
- A normal migration will display an icon that looks like two gray db icon connected with an arrow. - A P2P migration displays the gold person icon similar to the icon on the left in the “All Objects” section.
When you do a direct/P2P migration from the Source environment to Target environment, the P2P Migration Wizard displays.
See the indicator arrow below highlighted in Red .
When the Point-to-Point Migration Wizard window displays, select the project name from the Project dropdown menu. This will populate the “Object Type/Object Name” window to the right with the objects in the project.
Notice the “Warning” message highlighted in Blue above - Selecting the Next button will immediately execute the migration from Source to Target without archiving.
Select the “ Next > “ button to begin the P2P migration. Stat loads App Designer just as it does during a ‘normal’ migration.
When the migration completes, the P2P wizard details window reports the actions taken and the ending status of the migration as highlighted above in Green .
After reviewing, select the “ Finish ” button to complete the P2P process. You will notice that Stat generated a new archive set row in the “Archive Sets” window:
What’s different about this particular Archive Set? There are two main differences – Do you see them both?
The first, and most obvious, is the “Type” column of “Point-to-Point”. The second, and not so obvious, is the “Objects” column. The object count is 0. I know I migrated 62 objects from HRDMO > HRDEV. This row is more of a record for an action done, rather than a typical archive set that can be used for rollback.
To see a more detailed record of the event, select the “Migration Path” tab and double-click on the HRDEV environment database. This will launch the “Environment Status Window”.
And that is the quick guide to Point-to-Point migrations. If you have additional thoughts or tips on the subject be sure to add your own comment below.
In order to allow users to be able to do Point-to-Point migrations, they will need to have the “Run Point-To-Point Migration Wizard” rights within the PeopleSoft Migration Management rights.
And please remember: A Point-to-Point migration is just that. There’s no archiving taking place and the Archive Set created in the Archive tab cannot be used for recovery.
Thank you for taking the time to read this blog. I hope you found it informative.
William R. Hart
Dell | Quest Group, Pre-Sales