Stat 6.2 - User Guide


	NOTE: If objects are removed from a CSR, those objects are also removed from all the archive sets on that CSR. This keeps the base archive set accurate and up-to-date.

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.

Interim Archive Sets

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.

Final Archive Sets

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

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

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.

Source

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.


	NOTE: If the base archive set contains file objects, these are copied from the source file locations of the Base environment. Interim archive sets are copied from the Development environment by default.

Type

This is the type of archive set. Options include Base, Interim, Final, Merged, and Point-to-Point.

Description

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.”

Objects

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.

Archive Set Status

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

Ready to Migrate

If selected, this indicates one or both of the following:

•

The archive set is to be included in a mass migration with other archive sets that target the same environment

•

The migration of the archive set must be approved before it can be moved into the target environment

For more information, see Migration Approvals and Mass Migrations (PeopleSoft) .

Migration Status

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.

Create Date

This is the date that the archive set was created.

Buttons

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.

Creating Archive Sets (PeopleSoft)

As you make your changes to objects, you should periodically make interim archive sets. This lets you save your work at that point in time. When all your changes are completed and approved, you should make a final archive set. The procedure for both is the same.

To create an archive set:

In the Archive Sets tab of the CSR window, click New.

This opens the Archive Set window.

In the Archive Set window you enter basic information about an archive set. From here you define the archive type and source environment and add a description and comments. This window also provides you with read only information, such as number of objects and the time and date the archive set was created.


	NOTE: You can re-size this window as needed by clicking and holding an edge of the window and dragging to size you want.

In the Type field select the type of archive set you want to create. Your options include Interim and Final. Base sets are automatically created by Stat.


	NOTE: You can create unlimited number of interim archive sets, but only one final archive set.

In the Environment field select the environment containing the objects you want to include in the archive set.

This environment should be the one in which you made your changes. The default environment for interim archive sets is Development.


	IMPORTANT: If the CSR contains a reserved object for the selected environment, you cannot create a final set. If the CSR contains an unlocked object for the selected environment, you can create a final archive set but Stat displays a warning message.

In the Description field enter a short description of the changes you made to the objects.

This entry helps identify the archive set elsewhere in Stat.

If you are adding file objects to the archive set, do one of the following in the Files From field:

•

Select Environment if the source environment is Development and you want to take the file archives from the environment’s source file locations

•

Select Working if the source environment is Development and you want to take the file archives from the assigned user’s working directories. Or select No if you want to take the archives from the source file locations of Development.

•

Select VCM if you have associated the CSR with a version control management record and you want to take the file archives from the VCM repository. After selecting this option, a VCM-specific field is displayed (Revision for SVN and P4, Tag/Branch for CVS and Git, Label for PVCS, and Version for TFS). In this field you can specify the particular version of the objects you want to add from the VCM repository. Your system administrator may have configured a default value, but you can override it either by entering the version you want manually or by clicking the control button and selecting the version from the dropdown list. If left blank, Stat adds the most recent version of the objects in the repository.


	NOTE: When you save the archive set, Stat retrieves the objects from VCM repository. Your system administrator can configure Stat to archive the objects themselves or pointer to those objects.

(Optional) If you intend to include the archive set in a mass migration based on application release label, select the release label you want in the Release field. For more information, see Mass Migrating Objects .

(Optional) Enter comments about the archive set.

Comments can include a longer description of the changes or any other helpful information.

Click on the Objects tab and click Add.

Stat opens the Select Objects window, which displays a list of the objects contained in the base archive set.


	NOTE: When creating a final archive set, Stat automatically adds all the objects in the base archive set and does not open the Select Objects window.

To sort the rows in the Select Objects window, click a column heading to have the rows sorted based on that column.

Select the objects you want to add to the archive set.

An interim archive set can contain one, some, or all the objects in the CSR.

If you have performed previous migrations or deleted objects on the CSR, check the existence of each object by selecting it and clicking Check Existence.

Stat goes out to the source environment and looks for the object. If it finds the object it displays the value Yes in the corresponding Exists field. If the object does not exist, Stat displays the value No. Objects that do not exist in the source environment cannot be included in the archive set.

If the CSR has managed a PeopleSoft project, then the Synchronize PeopleSoft Ugrade/Action flags option would appear. When the option is selected and objects are included to the PeopleSoft managed project, the Stat Central Agent will synchronize the Upgrade/Action flags against the source environment.

Click OK.

This returns you to the Archive Sets tab in the CSR window, which shows your new archive set at the bottom of the archive set table. The Status column will display the value In Process until the Stat Central Agent finishes archiving all the objects.

Archive Set Object Information

To see the details of your archive set, double-click on the new row in the archive set table. This re-opens the Archive Set window. The Details tab should look familiar since this is the tab you filled out when you created the archive set. The next tab, Objects, now contains all of the object information for the archive set.


	NOTE: After adding objects to an archive set, the Migration Flags tab is added to the Archive Set Window. For more information, see Modifying Object Upgrade and Action Values .

The Objects tab displays the following information:

Migr Order

N/A. Oracle Applications only.

Class

Indicates the class of object. Archivable object classes include PeopleSoft proprietary, data, schema, and file.

Reflects the current status of the object. Possible statuses include:

•