立即与支持人员聊天
与支持团队交流

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

Archive Set Logs

The Logs tab of the archive set window displays any messages Stat logged during the archive process.

This tab provides you with a complete list of messages logged by Stat. It is a running log of the activities involved with the archive sets.

The Logs tab displays the following information:

Date and Time

The date and time the message was logged.

Object

Archive sets are created by processes run by different objects in Stat. These object processes each have their own capabilities and tasks. The Object column displays the Stat object that reported the message. These objects include:

•
Mgr – The manager object creates, destroys, and instructs all the other objects
•
Trg – Indicates the target environment
•
Src – Indicates the source environment
Type

There are three types of messages: Information, Error, and Warning.

Information

The text of the message.

Buttons

The Objects tab features the following short cut buttons:

•
Next Error – Navigates you through your error/warning messages
•
Print – Prints the contents of the window. Pressing this button automatically sends a job to the printer. There are no print options.
•
Export – Exports the information in this window. Pressing this button opens a Save As window. Several file types are available for selection using the vertical scroll. An Excel format is most useful for evaluating this data.
•
Clear – Clears the logs generated for this archive set

Re-archiving Objects

If for some reason the Stat Central Agent is unable to create an archive set without errors, rather than creating a second archive set, you can simply re-archive selected objects in the original archive set. When you re-archive objects, the Stat Central Agent deletes the original archive set and creates a new archive set containing only those objects you selected.

Although you can re-archive objects in any archive set, even those that were created without errors, you should only re-archive objects that were not successfully archived the first time. If you want to re-archive objects in an archive set that was created without errors, you should create an interim archive set.

* 
IMPORTANT: When re-archiving a Record or Field type object that has already been archived successfully, Stat does not re-archive information in the following tables: PSDBFIELD, PSIDXDDLPARM, PSINDEXDEFN, PSKEYDEFN, PSRECDEFN, PSRECFIELD, PSBUSPITEMIMG, PSBUSPITEMLANG, PSBUSPROCITEM.

To re-archive objects, in the Objects tab, select the objects you want to re-archive and click Re-Archive.

Archiving PeopleSoft Project Definitions

•
In addition to modifying Upgrade and Action values, you can view the audit flags and DDL settings for any PeopleSoft project definition that you have archived. You can also view the settings for portal structure permission list references. This way, if you wish to modify the project properties, you can do so in App Designer and then re-archive the project.

In addition to the objects contained in a PeopleSoft project, you can archive and migrate PeopleSoft project definitions as separate object types. You can associate PeopleSoft project definitions to a CSR in two ways:

•
You can associate a project definition manually the same way you would any other PeopleSoft proprietary object type by selecting it in the Objects tab of the CSR window
•
You can use the PeopleSoft Project Read wizard to associate a project definition to a CSR

Stat records how certain project definition properties have been set in the archive’s source environment, including audit flag and DDL settings. Stat also records the settings for portal structure permission lists, display size page property, and the database field format. Stat records whether these properties will be copied into the target environment during a migration or whether the settings as defined in the target environment will be retained. After you have archived or migrated a project definition, you can view its property settings as recorded in Stat in the Upgrade Options window.

To open the Upgrade Options window, double-click on the project definition in the Objects tab of the Edit Archive Set window. You can also open this window by double-clicking on a project definition in the Migration History Wizard.

Object Migrations (PeopleSoft)

Migration Overview

The previous chapter explained how to archive objects by creating archive sets. This chapter explains how to migrate archive sets between your PeopleSoft environments.

Migrating objects updates your environments with the most recent version of those objects, or, if necessary, lets you roll back your environments to earlier versions.

In Stat, migrating file objects entails moving them to designated source file directories or developers’ working directories. For PeopleSoft proprietary objects, Stat creates a PeopleSoft project that contains the archived objects. This project is created in a staging database, which is simply a temporary holding bin for objects. Once the objects are staged, Stat completes the migration by pushing the project from the staging database to the target PeopleSoft environment.

There are two places in a CSR window where you can initiate a migration: the Migration Path tab and the Archive Sets tab. Migrations can also be initiated outside CSRs using certain tools and Wizards. Migrations in Stat are not linear; a migration can go in any direction. For example, you can bypass the Development environment and migrate an archive set from the QA environment directly into the Production environment.

* 
NOTE: For a comparison of the various migration tools and techniques supported by Stat, see Appendix: Migration Options .

System administrators can set up Stat to support auto-migrating archive sets to multiple environments distributed over a network. This is done by designating particular environments on a migration path as a distribution environments and then associating them with lists of interrelated environments. This way, when you migrate an archive set to a distribution environment, Stat automatically migrates the archive set to all the associated distributed environments as well. This spares you the time-consuming task of migrating an archive set to each environment separately and is especially helpful when a migration path calls for more environments than the limit of nine that can be represented graphically.

When you migrate an archive set that contains both PeopleSoft proprietary objects and file objects, with the proper security rights you can choose to migrate just the PeopleSoft proprietary objects in the archive set, just the file objects, or both. System administrators can enforce that certain users only migrate file objects while others only migrate PeopleSoft proprietary objects.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级