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

Running a Migration (Generic Applications)

3
(Optional) In the Description field, enter a unique description of the migration.
4
(Optional) Select the Stop on Error option if you want the Stat Central Agent to terminate the migration at the first error it encounters.
5
(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.
8
(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. If the archive set does not contain any file objects or the target environment is not Development, this option is dithered with a value of “NA.”
11
Click Migrate.

Pre and Post Migration Steps

Pre and post migration steps define certain activities you should perform before and after migrating an archive set. Migration steps are performed either manually by the user or automatically by Stat. The steps are meant to promote adherence to development standards and are not mandatory or enforced.

Pre and post migration steps can be associated with object types, object classes and with target environments. This means that when you initiate a migration with an archive set that includes an associated object type or class, or when you initiate a migration to an associated target environment in either a single or a mass migration, Stat opens the Pre Migration Steps window. This window displays a checklist of recommended actions that should be taken before the archive set is migrated.

As with Pre Migration steps, after you successfully migrate an archive set that contains an associated object type or class, or after you migrate to an associated target environment, Stat opens the Post Migration Steps window.

Regarding Pre and Post Migration Steps windows:

Unlike the Pre Migration Steps window, the Post Migration Steps window is not opened automatically. Instead, post migration steps have a default status of Pending, which means that until the user changes the status of a post migration step to either Complete or N/A (Not Applicable), the migration will have a status of Wait for Post Step in the Migration Console. This is how Stat prompts users to complete post migration steps as intended. Once all the post migration steps have been marked as Complete or N/A, the status of the migration will change to Complete.

Automatic steps consist of custom commands defined by your system administrator. For more information on automatic steps, see the Stat System Administration Guide, Chapter 5, “Service Domain-Specific Maintenance.”

To execute an automatic step, click Run. Depending on the step, Stat may prompt you to specify additional parameters.

Custom commands are operating system commands executed by the client server that Stat is running on. When a custom command step is triggered, Stat opens the Custom Command Variables window. Here you can edit the command by adding or replacing parameters as needed, or you can run the command directly.

When defining a command, system administrators can include predefined parameters and user and server-based parameters that have been defined in Stat. This provides a convenient way to specify values commonly invoked by operating system commands, such as server names and download directories. In addition, parameters offer a way to secure sensitive information by encrypting values that you do not want visible to users, such as passwords.

Predefined parameters specify values used to login to a target environment during a migration (database name, user name and password), whereas user and server-based parameters generally invoke values specific to the users and file servers defined in Stat. Also, certain parameters may be defined so that their values are different depending on which user or server they are being applied to. For more information on pre and post migration step parameters, see the book, Stat System Administration, Chapter 4, “General Maintenance Tables”.

1
In the Command with parameters field, enter the command you want Stat to run.
NOTE: System administrators can restrict user access to certain servers at the service domain level. The servers displayed in the Server field drop-down list may be limited if the server access of the current user has been restricted. For more information, see Stat System Administration, Chapter 3, “Stat Security.”
3
Click Interpret >>.
The Interpreted Command field displays how the command is interpreted by the client server. Null values and encrypted values are enclosed in angle brackets. Encrypted values are not displayed but replaced with asterisks.
5

To view the history of any automatic step, select it and click History. This opens the Migration Step History window, which displays a record of each time Stat successfully executed the command. These records display the date and time the step was run, the user who ran it, and what parameters were used.

To view the log for the step, click Log. To print the history table, click Print. To export it to a file format, click Export.

2
Select Complete for each step that Stat performs successfully.
NOTE: Until a post migration step has been marked as either Complete or N/A (non-applicable or not applied), the migration will have a status of Wait for Post Step in the Migration Console. Once all the post migration steps have been marked as Complete or N/A, the status of migration will change to Complete.
4
Click OK.

Your migration path now shows the base archive set in your Development environment. You can go into the Development environment and begin making changes to the generic application objects.

The process is the same for migration of all types of archive sets.

Migration Approvals and Mass Migrations (Generic Applications)

Stat provides advanced version control and change management support in the form of migration approvals and mass migrations:

Marking Archive Sets for Migration

When you want to perform a migration that requires approval, or you want to flag an archive set for a mass migration, the first step is to mark the archive set for migration. This is done either by individually selecting the Ready to Migrate option on the Archive Sets tab of the CSR window, and then selecting the environment(s) that you want to target, or by marking multiple archive sets in the Ready to Migrate window.

2
In the Archive Set table, select Ready to Migrate for the archive set. Then click Apply.
3
Click Migration Target.
4
In the table on the right side of the window, select Migrate for each environment that you want to designate as a target environment.
NOTE: In the table displayed in the right section of the Target environments window, distribution environments and their associated distributed environments are designated by small blue and yellow icons, respectively. When you select Migrate for a distribution environment, all the environments on its distribution list are selected as well. Also, you cannot select a distributed environment without selecting its distribution environment as well.
5
Click Premigration List to view a checklist of any actions you should take before migrating the archive set.
7
Click OK or Apply to save your work.
Once you click OK or Apply, the archive set appears in the Mass Migration window for the target environment, and the approval requests, if any, are generated and sent out to each user authorized to approve the migration.

The Ready to Migrate window displays all the archive sets that have not yet been individually marked for migration and which share the same release label and environment on the migration paths of their respective CSRs. After you specify the target environment and release label, Stat retrieves all the qualifying archive sets that have not been marked for migration. Retrieved archive sets are marked for migration by default. You can unmark any archive set you do not want marked as Ready to Migrate.

1
Select Migration Management | Archive Sets - Ready to Migrate.
2
In Module field, select the change management module you are using.
3
In Service Domain field, select the service domain of the archive sets.
4
In Environment field, select the migration target environment of the archive sets.
5
In Release field, select a release label. Stat retrieves archive sets that have been assigned to that release.
6
(Optional) Deselect Ready to Migrate for any archive set that you do not want to be marked for migration.
7
Click OK to save the archive sets as Ready to Migrate.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating