Chat now with support
Chat with Support

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

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

Running a Migration (PeopleSoft)

(Optional) To plan the migration for an unspecified date, clear the Migration Date check box. Planned migration can be initiated any time later by Stat Windows Client or by an external third party component using a REST API call. See “Appendix: Stat REST Web Services API” in the Stat System Administration Guide.
(Optional) In the Description field, enter a unique description of the migration.
(Optional) Select the Stop on Error option if you want the Stat Central Agent to terminate the migration at the first error it encounters.
(Optional) De-select the E-mail Notification option if a business rule or personal rule triggered by a migration event has been defined for the service domain and you do not want Stat to send email notifications that may be triggered by the migration.
(Optional) In the Migrate column, de-select the individual objects you do not want to migrate.
Development Env– Select if you want to place the file objects in the source file locations of the Development environment
Working – Select if you want to place the file objects in the developers’ working directories. Only the file objects assigned to each developer get copied into their working directories.
Dev & Working – Select if you want to place the file objects in both the source file locations and the working directories.
(Optional) If CLI Auto Migrate has been enabled for the target environment, deselect the Auto Migration if for some reason you do not want Stat to auto-migrate the PeopleSoft proprietary objects.
It is recommended that you leave the Auto Migration option selected. If auto-migration is turned off, you need to manually migrate the PeopleSoft objects to the target environment. This also prevents Stat from executing the DataMover script to migrate non-App Designer objects.
Stat defined project - Select this option if you want Stat to assign a name to the project. Stat-defined project names always use the naming convention, “ST######.”
User defined project - Select this option if you want to assign a name to the PeopleSoft project. Then in the Project Name field enter the name you want.
Project in Archive Set - Select this option if you added a project definition to the archive set and want to re-use the project name. This option is only available if the archive set and the project definition included in the archive set reference all the same App Designer objects. This also applies to subobjects, meaning the option is not available if the parent objects have been removed either from the archive set or the project definition included in the archive set. The project definition included in the archive set can reference subobjects so long as the subobjects' parents are in the project definition and the archive set. For more information on subobjects, see Associating Related PeopleSoft Proprietary Objects .
Reuse project - Select this option if you are migrating an archive set that was previously migrated using the same staging database, and you have not modified the archive set after its original migration. If you select this option, by default Stat restages the project in the staging database. However, you can de-select the Restage objects option if you do not want to wait for the objects to be restaged and you are sure they were staged successfully the last time.
IMPORTANT: If you selected the Project in archive set option, you cannot modify the settings in the Upgrade Options window.
Click Migrate.

Auto-Migrating PeopleSoft Projects

If the CLI Auto-Migration feature has been enabled for the target environment (and you did not de-select the Auto Migration option), Stat launches PeopleSoft and tells PeopleSoft to copy the project from staging to target via a command line interface. While this is happening, you may see Application Designer login screen flash on your screen momentarily. For non-App Designer objects, Stat executes the DataMover import script. For more information on CLI options, see Setting Up Your PeopleSoft Connections .

If the archive set contains a PeopleSoft project definition and you have opted to migrate the archive set using a Stat created project, Stat runs the PeopleSoft project copy CLI twice: once for the Stat created project and once for the PS Project in the archive set. The CLI for the PS project only copies the project definition, but it updates the project version appropriately.

If the CLI Auto-Migration feature has not been activated, or if an error or warning occurs during the auto-migration, you must perform the migration manually by logging into the staging database and pushing the project into the target environment. If CLI-Open is configured for the staging environment, Stat opens App Designer in the staging database for you. For more information, see Manually Migrating PeopleSoft Projects .

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating