サポートと今すぐチャット
サポートとのチャット

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

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 (Generic 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 generic application 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.

Migrations in Stat are not linear; a migration can go in any direction.

* 
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 (Generic Applications)

The previous chapter explained how to archive objects by creating archive sets. This chapter explains how to migrate archive sets between your generic application 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.

Migrations in Stat are not linear; a migration can go in any direction.

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

Synchronizing Your Development Workspace

It is good practice to synchronize your development workspace with your base archive set. This ensures that you are making changes to the correct version of the objects. This is true of all your environments. As you make changes, you should create interim archive sets that document those changes and then migrate them to the appropriate environments. The migration process is virtually the same, regardless of the type of archive set.

The development workspace is where you make the changes. For data objects, this is the Development environment. For file objects, it can be either the Development environment’s source file locations or the assigned developers’ working directories. It is recommended that each developer make changes to file objects in their own working directories so that the changes can be documented and controlled. System administrators can enforce that developers modify objects only in either their working directories or in the source file locations.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択