Chat now with support
Chat with 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

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.

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

Object Migrations (Oracle Applications)

Migration Overview

The previous chapter explained how to archive objects by creating archive sets. This chapter explains how to migrate archive sets between your Oracle Applications 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 data objects, this means migrating them from one environment to another.

There are two places in a CSR where you can initiate a migration: the Migration Path tab and the Archive Sets tab. Migrations in Stat are not linear; a migration can go in any direction. For example, in the sample migration path shown below, you could bypass the Development environment and migrate an archive set from the Base environment directly into Production.

* 
TIP: 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 within a migration path as 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 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 data objects and file objects, with the proper security rights you can choose to migrate just the data 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 data objects.

Migration Overview

Object Migrations (Oracle Applications)

The previous chapter explained how to archive objects by creating archive sets. This chapter explains how to migrate archive sets between your Oracle Applications 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 data objects, this means migrating them from one environment to another.

There are two places in a CSR where you can initiate a migration: the Migration Path tab and the Archive Sets tab. Migrations in Stat are not linear; a migration can go in any direction. For example, in the sample migration path shown below, you could bypass the Development environment and migrate an archive set from the Base environment directly into Production.

* 
TIP: 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 within a migration path as 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 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 data objects and file objects, with the proper security rights you can choose to migrate just the data 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 data objects.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating