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

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

Migrating PeopleSoft Proprietary Objects

When an archive set contains PeopleSoft proprietary objects, Stat first moves copies of the archived objects into a staging database, which is simply a temporary holding bin for objects. Stat then creates a PeopleSoft Project, which contains references to the objects in the staging database. At this point, if the CLI Auto-Migration option has been activated for the target environment, Stat completes the migration automatically using the PeopleTools command. Optionally, you can complete the migration by logging in to PeopleTools in the staging environment and manually pushing the project into the target environment.

Migrating Data Objects

Data object definitions are archived in the Stat Repository. When you migrate an archive set that contains data objects, Stat copies the data object definitions from the Stat Repository to the target environment. If the data object already exists in the target environment, Stat replaces that object definition with the archived copy using the delete and insert method.

Migrating File Objects

When an archive set contains file objects, the file archives are stored in the Stat repository. When you migrate the archive set to a PeopleSoft environment, Stat copies the file archives from the Stat Repository to the file locations defined for the target environment. If the file objects already reside in any of these source file locations, Stat replaces each existing instance with the archive copy. If the files exist in none of the source file locations, Stat either copies the files to all the source locations defined for the target environment or copies the files to the designated default location. These options are set up by system administrators when configuring the target environment.

To migrate file objects in an archive set to the developers’ working directories, you migrate the archive set to the Development environment. Stat gives you the option of migrating the file objects to the Development environment’s source file locations, the developers’ working directories, or to both. To migrate an archive set taken from the Development environment’s source file locations to the developer’s working directories, or vice versa, the migration must be initiated from the Archive Sets tab, not the Migration Path tab.

If two or more environments on a migration path share the same source file locations for a particular file type, whenever you migrate an archive set that contains file objects of that type to one of the environments, by default the file objects are also migrated to the other environment(s) that share the same source file locations. For example, if the Development environment and Test environment share the same source file locations for COBOL file objects, and you migrate an archive set containing a COBOL file object to Development, Stat documents that the same file object was also migrated to Test. This eliminates the time consuming process of having to perform multiple migrations in order to document the migration of the same file objects to each environment on the migration path.

Migrating to Distributed Environments

When you migrate objects to a distribution environment, by default Stat migrates those objects to all the environments on its distribution list. However, you can opt to exclude certain environments from the migration.

When defining a migration path, system administrators designate distribution environments and add other environments to their distribution lists. For example, let’s say you have ten production environments and each one physically resides in a different location. All of your development work is done centrally, and when ready, changes are migrated out to all the production environments at the same time. Most likely your system administrator would define the local or ‘in-house’ production environment as the distribution environment and connect it to the nine other production environments.

Although connected to the distribution environment, the other environments are not represented graphically and are not technically part of the migration path. This means that objects cannot be locked in the environments on a distribution list. Also, objects can only be migrated to them, not from them.

Graphically, distribution environments are designated by a small icon displayed to the left of the environment graphic, as shown below:

To view a listing of the environments connected to the distribution environment, double-click on the distribution icon. Stat opens the Distributed Environments window, which shows a list of all the environments connected to the distribution environment.

In this window, you can deactivate any environment you do not want to include in a migration. This way, when you migrate an archive set to a distribution environment, Stat migrates the objects only to the active environments in the distribution list. To deactivate all the environments, click Set All Inactive. If you want to reactivate an environment, you can do so at any time by selecting the Active check box, or if you want to reactivate all the environments, click Set All Active.

For more information see “PeopleSoft Environment Migration Path Maintenance,” in the Stat System Administration Guide, Chapter 5, “Service Domain- Specific Maintenance.”

For Stat to migrate PeopleSoft proprietary objects automatically to a distribution environment and its associated environments, the CLI Auto-Migration option must be activated for the distribution environment, as well as each environment on the distribution list. If the CLI Auto-Migration option is activated for just some of the environments in the distribution list, Stat migrates PeopleSoft proprietary objects only to those environments.

Also, Stat displays a warning message if it successfully completes a migration to a distribution environment but not to one or more of its associated environments (which would be the case if, for example, the password to one of the environments was incorrect). This information is also displayed in the Migration Details window. For more information, see Documenting Migrations (PeopleSoft) .

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级