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

Manually Migrating PeopleSoft Projects

If the CLI Auto-Migration feature has not been activated (or you de-selected the Auto Migration check box), you must perform the migration manually by logging into the staging database and pushing the project into the target environment.

2
Log in to the PeopleTools Application Designer in the staging environment. Select Tools | Copy Project to copy the project from the staging database to the target environment.

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 triggered either manually by the user or automatically by the Stat Central Agent.

Pre and post migration steps can be associated with object types, object classes and with target environments. 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 a window that allows you to select which pre and post migration steps to run. This window displays a list of recommended steps that should be performed before or after the archive set is migrated.

Although recommended pre and post migration steps are added by default to the migration, you can exclude any step from the list. You can also change migration step order, update pre migration step status, and run pre migration steps. Once a pre migration step is run, it cannot be excluded from the migration. Pre migration steps can only be run before the migration is started. Post migration steps can only be run after the migration is successfully completed. The same is true for updating post migration status.

When a pre migration step completes with an error, the entire migration halts with “Waiting for Pre-Step” status. When a post migration step completes with an error, then migration halts with “Waiting for Post-Step” status. When a step completes with an error, you can fix the issue or manually update the migration step status to “Complete” or “Canceled.” This will trigger the Stat Central Agent to continue the migration.

To set a pre migration step status to “Complete,” manually select the step and then select Complete from the Update Status drop-down list. Then click the Update button beside it.
To view the pre migration step command log, select a step and click the View History button. 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.

Click the Migrate button after you finalize with pre and post migration steps.

Automatic steps consist of predefined custom commands executed by Stat. These steps will be automatically triggered and executed by the Stat Central Agent.

For more information on automatic steps, see the Stat System Administration Guide, Chapter 5, “Service Domain-Specific Maintenance.”

When this step is triggered, Stat uses your PS operator ID and password to log in to the PeopleSoft environment (by default, the target environment of the migration) and runs the selected .dms file. Before executing the step, however, Stat displays the DataMover Variables dialog box. Here you can specify a different environment, which .dms file you want to run, and the location of the script files. For a default location, Stat appends the subdirectory “\script” to the PeopleSoft Home Directory (PS_HOME) defined in the PeopleSoft Configuration Manager.

The default script location is based on the registry entry for the version of PeopleSoft that you were last working in.

After specifying the variables you want, click Run to execute the step. You can run this step for each .dms file included in the migration, or you can run this step for the same file but in a different environment or script location.

You may run manual pre migration steps before the migration has been initiated in the Select Pre and Post Migration Steps to Run window. Custom commands are operating system commands executed by the Stat Central Agent. To run a pre migration step, select the step and click the Run button. This action opens the Pre Migration Step dialog where you can review the command and command options, interpret the command, and run the step by clicking the Run button. After the migration is initiated, the steps can be run from the Migration Console.

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 Stat System Administration Guide, Chapter 4, “General Maintenance Tables”.

The Create Project Build Script step is a post migration step applicable for PeopleSoft versions 8 and higher only. When this step is triggered, Stat uses your PeopleSoft operator ID and password to log into the PeopleSoft environment that is the target of the migration and creates the build script for the project that was used during the migration. Stat uses the PeopleSoft command line statement to accomplish this and the build settings from the Windows registry to generate the SQL script for Create or Alter. The build script is placed in the location specified for build settings in your PeopleSoft configuration.

When this post migration step is triggered, Stat automatically launches the PeopleSoft COBOL Compile program, either CBLBLD for NT or pscbl.mak for Unix. Your system administrator defines the default server and variables required to run the compiler. For Unix, these variables include the PeopleSoft home directory and the Cobol Compile directory. For Windows servers, these variables also include the drive and directory where the compile is to take place. If you want to specify a different server and variables, you can do so in the Cobol Compile Variables dialog box, which Stat opens when you click Run.

After specifying the variables you want, click Preview to see how the object will be compiled. If satisfied with the results, click Run to execute the step.

Stat executes a Cobol Compile post migration step on a mainframe server as follows:

Stat changes the directory based on the values in the Directory and Cobol Compiler Location: Drive and Root Directory fields of the File Server Maintenance table.
If the Directory field has a value, it is displayed in the PS Home field on the Post Migration step window. This field cannot be modified on the Post Migration step window.
The Cobol Compiler Location:Drive and Root Directory value is displayed in the Cobol Compiler field on the Post Migration step window. This field can be modified when the step is run.

When running the step, Stat executes the login sequence as follows:

9

Point-to-Point PeopleSoft Project Migrations

If you want to migrate a PeopleSoft project that contains a large number of objects, but you do not necessarily want to spend the time required to archive all these objects, you can use Stat simply as a migrating tool by performing a point-to-point migration.

During a point-to-point migration, Stat uses CLI functionality to open PeopleSoft and migrate the objects in the project directly from the source environment to the target. Stat does not stage the objects and does not archive them. This means that while a record of the migration is recorded in Stat for reporting purposes, you cannot use Stat to roll back the migration since none of the objects in the project were archived.

To execute a point-to-point migration, you must add the project you want to migrate to a CSR and the CLI Auto-Migration option must be activated for both the source and target PeopleSoft database. For more information on activating CLI functionality, see the section, Setting Up Your PeopleSoft Connections .

6
(Optional) In the Description field, enter a unique description of the migration.
8
Click Migrate.
When finished, Stat displays the Migration Console, which records the Point-to-Point archive migration. For more information, see Migration Console . Point-to-point migrations are also recorded in the Migration Details window, which is described in the section Migration Details Window on page 158.

Migrating Non-App Designer PeopleSoft Proprietary Objects

When Stat migrates PeopleSoft proprietary objects, it first moves copies of the archived objects into a staging database. Stat then creates a PeopleSoft project (called an Application Designer project), which contains references to the objects you just staged. However, there are PeopleSoft proprietary objects that cannot be included in an Application Designer project. For some of these objects, Stat provides an alternative form of migration support. These objects include:

 

You archive non-Application Designer objects the same way you do other PeopleSoft proprietary objects. When you migrate them, however, Stat executes the following steps after the archived objects are moved to the staging database:

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen