Object Archives (PeopleSoft)
Using Stat, developers can take ‘snapshots’ of objects as they exist in a particular environment and archive them indefinitely in the Stat Repository. Because archive sets are stored in the Stat Repository and not a PeopleSoft environment, you can archive different versions of objects and rollback to previous versions when necessary.
Once a developer locks the objects that he or she wishes to change, Stat automatically takes a snapshot of those objects before any changes occur. This is called a base archive set. The base archive set is the “pre-change” version of all the objects locked in the CSR. You can use this snapshot, like all archive sets, to restore PeopleSoft proprietary objects, data objects, and file objects to their previous state.
As you make changes to the objects, you can also create interim archive sets. This is effectively backing up your work as you go along.
The ability to create the archive sets that include file objects, data objects, and PeopleSoft proprietary objects is activated at the service domain level by your system administrator.
About Archive Sets
Using Stat, developers can take ‘snapshots’ of objects as they exist in a particular environment and archive them indefinitely in the Stat Repository. Because archive sets are stored in the Stat Repository and not a PeopleSoft environment, you can archive different versions of objects and rollback to previous versions when necessary.
Once a developer locks the objects that he or she wishes to change, Stat automatically takes a snapshot of those objects before any changes occur. This is called a base archive set. The base archive set is the “pre-change” version of all the objects locked in the CSR. You can use this snapshot, like all archive sets, to restore PeopleSoft proprietary objects, data objects, and file objects to their previous state.
As you make changes to the objects, you can also create interim archive sets. This is effectively backing up your work as you go along.
The ability to create the archive sets that include file objects, data objects, and PeopleSoft proprietary objects is activated at the service domain level by your system administrator.
Archive Set Types
You use archive sets to recover objects to PeopleSoft environments and migrate completed changes. There are three main types of archive sets: Base, Interim, and Final. There are also two other types called Merged and Point-to-Point which are created automatically by Stat. A Merged archive set is the result of using the Object Merge Wizard to combine the definition of two versions of the same PeopleSoft proprietary or data object, whereas a Point-to-Point archive set is the result of using the Point To Point Wizard to not migrate a PeopleSoft project directly between environments.
You can use any archive set type to restore or move objects. Each archive set contains objects that belong to one CSR, while the CSR itself may contain one or more archive sets, including the base, the final, and all the interim or merged archive sets.
When you create an interim or final archive set, you tell Stat what environment the archives of the objects should come from. For the PeopleSoft proprietary objects and data objects, the archives come from the selected PeopleSoft environment. For the file objects, the archives come from the source file locations defined for each file type. For each active PeopleSoft environment, your system administrator can define as many possible file locations for each file type as needed. When archiving a file object, Stat looks for the file in the first location. If the file is not found, Stat looks in the second location, and so on. Stat archives the first instance of the file that it finds.
Source file locations are where the files for that environment reside. In Stat, each user also has a working directory defined for them. This is where users make changes to the file objects assigned to them. File object archives can be taken from either the environment source locations or from the user's working directory.
The base archive set is the most important because it contains the “pre-change” version of all the objects in the CSR. Stat automatically creates the base archive set when you save your CSR after locking objects. The base archive set is created from the Base environment in your migration path. Your system administrator defines which environment is the Base environment for each migration path. Your system administrator also defines each file type's source file locations for the Base environment. It is from these locations that Stat takes the “pre-change” version of the file objects locked in the CSR.
A CSR can contain only one base archive set, which contains all the locked objects. The base archive set is dynamic, meaning that Stat automatically adds to it objects that are locked in the Base environment after the set is initially created. The base archive set continues to grow as Stat issues more locks on objects in the CSR.
You should never delete base archive sets from the system, since they contain objects in their original, “pre-change” state. The moment you request a lock on objects, Stat places a holder in the system for the base set. Before you save the CSR, the status of the base set is In Process. If you do not save the CSR, the objects are not locked and the base archive is not created.
As you make changes to objects, you can save the modified objects in interim archive sets. Interim archive sets contain objects that are currently being modified and can be taken from any environment on your migration path, although by default the source environment is Development. If the archive set contains file objects, the archive of the file objects is taken either from the first source location defined for the specified environment or the developer’s working directory. For PeopleSoft proprietary objects and PeopleSoft files, when an object does not exist, the interim archive set will complete with warning. For other object types, when an object does not exist, the interim archive set will complete with error.
You can create an unlimited number of interim archive sets. An interim archive set is also dynamic. Stat can add objects to it after it is created. However, you cannot add or delete objects from an interim archive set once it has been migrated. This is to keep referential integrity intact. If you need to archive an object that is not in one of your interim archive sets, just create a new interim archive set for that object.
An interim archive set can contain some or all the objects associated with a CSR. You create interim sets to save objects after significant changes have been made throughout the development process.
For the Development environment, your system administrator defines source file locations for each file type just like all other environments. Your system administrator also defines working directories for each developer. Working directories are where developers make their changes. When creating an archive set from the Development environment, you can take the file archives either from the source file locations of the Development environment or from the developer’s working directory.
Once your changes are completed and approved, you should create a final archive set. The final archive set is static, and although it is not mandatory that you create one, it is strongly recommended. A CSR can contain only one final archive set, and objects cannot be added to it once it is created. When the final archive set is created, Stat automatically adds to it all objects of the CSR.
You can create a final archive set from any environment on the migration path of the CSR. As with interim archive sets, if the final archive set contains file objects, the archive of the file objects is taken either from source locations defined for the particular file types or the developers’ working directories.
Merged archive sets are automatically created by Stat when you use the Object Compare Wizard to combine the definition of two versions of the same PeopleSoft proprietary or data object. Merged archive sets are automatically added to the CSR from which the original versions of the object were selected. A CSR can contain an unlimited number of merged archive sets. For more information, see The Object Compare Wizard .
Point-to-point archive sets are created automatically when Stat uses CLI functionality to open PeopleSoft and migrate the objects in a PeopleSoft project directly from a source environment to a target environment. Stat does not stage the objects and does not archive them. This means that point-to-point archive sets are created strictly for reporting purposes and cannot be used to roll back the migration since none of the objects in the project were archived. For more information on point-to-point migrations, see Point-to-Point PeopleSoft Project Migrations
Archive Sets Table
The Archive Sets table shows the archive sets that have been created for a particular CSR. You can create and migrate archive sets whenever this table is displayed. To open the Archive Sets table, select the Archive Sets tab in the CSR window. The table appears in the right section of the tab page.
The Archive Sets button becomes activated whenever you select the CSR node, the All Objects node, or the Migration Path node in the tree view on the left side of the tab page. If you select any object or developer node in the tree structure while the Archive Set table is displayed, the view switches to the Environment Info table and the Archive Sets button becomes dithered. This is because archive set information is not specific to these nodes and cannot be filtered.
To view archive set information by environment, select any of the environment nodes under the Migration Path node. This filters the archive set table to show information about only the archive sets created from that environment.
To sort rows of information in the archive set table, click on the column headings.
The archive set table displays the following information:
This is the archive set ID, which Stat automatically generates. Archive sets appear in the order you create them.
This is the source environment from which you copied the objects in the archive set. It must be an environment in the migration path defined for the CSR. A “-w” appears at the end of the environment name if the archive set was taken from the Development environment and it contains files that were taken from the users' working directories rather than the source file locations of the development environment. If it was taken from a VCM repository, a “-v” appears on the end of the environment name.
This is the type of archive set. Options include Base, Interim, Final, Merged, and Point-to-Point.
The description you entered when you created the archive set. Descriptions help distinguish between different interim archive sets. Base archive sets always contain the description: “Stat Baseline Set.”
This indicates how many objects the archive set contains. For a base or final archive set, this number is the total number of objects contained in the CSR. An interim archive set may contain less than that number.
This indicates the current status of the archive set. Possible statuses include:
|
• |
In Process – Indicates that Stat is currently archiving the objects. When you add objects to a CSR, the archive set is in this initial status until all objects are archived. When the Stat is finished archiving, the status changes to Complete. |
|
• |
Complete – Indicates that all objects are archived |
|
• |
Complete/With Errors – Indicates that the archive set is created but errors were detected during the archiving process. For PeopleSoft, this could mean that PeopleSoft SysAudit or PeopleSoft DDDAudit are not clean, or it could mean that Stat could not find the file objects you wanted to archive, or that the file location information was not set up correctly. Some errors are so severe that the archive set is unusable. Refer to the Logs window for further information. |
|
• |
Complete/With Warnings – Indicates that the archive set is created but warnings were issued during the archiving process. You can still migrate an archive set in this status. Refer to the Logs window and investigate further. |
|
• |
Delete Pending – Indicates that the archive set is set for deletion. It remains in this status until Stat completes its tasks. |
|
• |
Deleted – Indicates that Stat deleted the archive set |
If selected, this indicates one or both of the following:
For more information, see Migration Approvals and Mass Migrations (PeopleSoft) .
This indicates the status of any archive set that you marked as Ready to Migrate. Before you select the target environment(s) for the archive set, the status is N/A. After you select the target environment(s), the status is In Process. Once the archive set has been migrated to all the selected environment(s), the Ready to Migrate check box is unchecked and the status reverts to N/A.
This is the date that the archive set was created.
The archive sets table features the following short cut buttons:
|
• |
New – Opens the Archive Set window where you can define new archive sets |
|
• |
Edit – Opens the Archive Set window where you can edit the selected archive set |
|
• |
Delete – Deletes the selected archive set |
|
• |
Refresh – Refreshes the window with the most up-to-date information from the environment. You can also press <F5> to refresh. |
|
• |
Print – Prints the contents of the archive set table |
|
• |
Migration Target – Opens the Target Environments window for the source environment of the selected archive set. This button is activated when the Ready to Migrate check box is selected for the archive set. |
