Chat now with support
Chat with Support

Stat 6.0 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department Maintenance Country Maintenance Customer Maintenance Object Type Maintenance PeopleSoft Environment Connection Maintenance Pre/Post Migration Steps Parameters Oracle Applications Configuration Oracle Applications Connection Maintenance Generic Application Connection Maintenance Schema Object Parameters Maintenance Data Object Maintenance PeopleSoft Search Configurations Stat Report Definition Maintenance Version Control Management Connection Maintenance
Service Domain-Specific Maintenance Configuring the Stat Central Agent Email Configuration Object Security Appendix: Sample Service Domain Configuration Appendix: User Class Rights Appendix: Creating a Staging Database Appendix: Database Tuning Appendix: Oracle Applications File Type Directory Appendix: Ports and Firewalls Appendix: Stat Web Services Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

Predefined Automatic Steps

Stat can execute three predefined, automatic post migration steps: Create Project Build Script, Compile COBOL, and Run DataMover Script.

When this step is triggered, Stat logs into the target PeopleSoft environment of the migration and creates the project build script for the project used during the migration. Stat uses the command line statement to launch PeopleSoft. It uses the PeopleSoft build settings from the Windows registry to generate the SQL script for create or alter. This step is applicable for PeopleSoft versions 8 and higher only.

When this step is triggered, Stat automatically launches the PeopleSoft COBOL Compile program, either CBLBLD for NT or pscbl.mak for Unix. When executing this step, Stat uses the following file server variables:

Except for the definition of the operating system, all of these settings can be changed at the time of execution.

When this step is triggered, Stat logs in to the PeopleSoft environment (by default, the target environment of the migration) using the user’s PS operator ID and password and runs the selected Data Mover script. By default, Stat uses the .dms file in the subdirectory “\script,” which is appended to the PeopleSoft Home Directory (PS_HOME) defined in the PeopleSoft Configuration Manager. All of these settings can be changed at the time of execution.

Defining a Custom Command

You can define automatic post migration steps in the form of custom commands. These are operating system commands executed by the client server Stat is running on. All drive mappings and file paths are relative to the client server.

1
In the Post Migration Step Maintenance window, click New and specify the object class and object type of the automatic step you want to create.
2
In the Automatic Post Migration Step field, select Run Custom Command.
3
4
Click Apply to save your work.
5
Click Define Command.

<<YY>>

The current year, 2-digit format

01

<<YYYY>>

The current year, 4-digit format

2001

<<MM>>

The current month, 2-digit format

01

<<DD>>>

The current day of month, 2-digit format

31

<<DDD>>

The current day of week

Monday

<<HH>>

The current hour, 2-digit format

13

<<NN>>

The current minutes, 2-digit format

45

<<SS>>

The current seconds, 2-digit format

23

<<ENV>>

The target environment of the migration

PROD

<<PROJ>>

The name of the PeopleSoft project used in the migration

ST001095

<<SDCD>>

The service domain that the CSR belongs to

HR

<<CSRID>>

The CSR ID number

6086

<<OBJTYPE>>

The object type the post migration step is defined for

Panel

6
In the Command with parameters field, enter the command you want Stat to run.
10
(Optional) In the SSH time-out in seconds field, specify a longer connection timeout amount.
11
(Optional) Click Interpret Command.
The Interpreted Command field displays how the command is interpreted by the client/server. Be aware, however, that certain variables can only be resolved when the user opens the Command Editor window during a migration. When the Command Editor window is opened by a system administrator through the maintenance window, the following restrictions apply:
12
(Optional) Click Run Command.
NOTE: When the Command Editor window is opened by a system administrator through the maintenance window, the Run Command button is limited the same way as the Interpret Command button in terms of resolving certain types of variables. See the list of restrictions in the preceding step.
14

Pre Migration Steps

The Pre Migration Steps Maintenance table defines actions that should be taken before an archive set is migrated. Like post migration steps, pre migration steps are either manual or automatic, meaning they are performed either by users or by Stat.

You can associate pre migration steps with object types and with target environments (unlike post migration steps, which are only associated with object types). This means that pre migration steps are triggered whenever users migrate an archive set that includes an associated object type, or when they migrate an archive set to an associated environment.

When defining a pre migration step, you can specify it should be run only once for a particular CSR, migration, or target environment. This way, you can prevent a step from being run multiple times when it should be run only once (e.g., a step that executes a script against a particular database).

Pre migration steps security is controlled by the following user class rights:

The Pre Migration Steps Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Domain-Specific | Pre Migration Steps.

Active

If selected, activates the value in Stat

Pre Migration Step
(Required Value)

The type of step. Options include Custom Command, Run DMS, and Manual.

NOTE: Custom Command and Run DMS are also used as post migration steps and are defined the same way.

Step Name
(Required Value)

The name of the step

Object Class
(Key Value)

The class of object for which the step is defined. Options include data objects and file object for all three change management modules supported by Stat, as well as PeopleSoft Proprietary objects.

Object Type
(Key Value)

The object type the step is associated with (if any)

Target Env.

The target environment the step is associated with (if any)

Run Per

If selected, specifies that the step should be run only once for a particular CSR, migration, or target environment. This option is used to prevent a step from being run multiple times when it should be run only once. The default option is Migration.

Order
(Required Value)

A number that determines per object type the sort order for the step on the post migration checklist. Steps with a lower number are displayed at the top of the list.

Last Update
(Read Only)

The date and time that this record was last updated

Update By
(Read Only)

The user that who updated this record

Release Management Maintenance

The Release Management Maintenance table defines major and minor release labels that users can assign to archive sets. This gives users the ability to upgrade their applications or roll back to previous versions by mass migrating archive sets based on application release number. For more information on mass migrating archive sets based on application release labels, see the “Object Migrations” sections in the change management chapters of the book, Stat User Guide.

Application releases are based on a branching concept by which minor releases reference their immediate parent releases. This way, when a user mass migrates archive sets based on a minor release label, for example, 2.1, any archive set assigned its parent release label, 2.0, are migrated as well.

Application release security is controlled by the following user class rights:

The Release Management Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | Domain-Specific | Release Management.

Application release numbers are specific to service domain and change management module.

Release Level
(Key Value)

A tree view displaying major and minor releases

Active

If selected, activates the value in Stat

Release Name

Name assigned to the release number

Last Update
(Read Only)

The date and time that this record was last updated

Update By
(Read Only)

The user who last updated this record

1
In the Domain field, select the service domain.
2
In the Module field, select the change management module.
6
Click Apply or OK.
Related Documents