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

Migration Path Diagram

After you have specified the migration code and description, click Apply to save your work. Then select the migration path and click Template.... This opens the Migration Path Definition window. The left section of the window displays a list of each environment that can be added to the new migration path. The right section of the window is where you arrange the icons to create a graphical diagram representing the sequence of the migration.

To switch the environment’s place in the migration path with another environment, select Swap environment number. Then in the prompt select the number of the environment you want to switch and click OK.

Defining Distribution Environments

Distribution environments allow users to migrate objects to multiple environments distributed over a network at one time. When a user migrates an archive set to a distribution environment, Stat automatically migrates the archive set to a list of connected environments.

You define distribution environments at the migration path level. The first step is to designate certain environments in a migration path as distribution environments. Then you determine which environments you want to connect to them. For example, let’s say you have ten production environments. 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 you would define the local or ‘in-house’ production environment as the distribution environment on the migration path 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 connected to a distribution environment. Likewise, objects can only be migrated to them; you cannot archive objects from these environments.

For more information on distribution environments, see the book, Stat User Guide, Chapter 12, “Change Management for Oracle Applications.”

Click Add.

Updating CSR Migration Paths with Additional Environments

You can add environments to existing migration paths that are already associated with CSRs. You then have the option of updating the migration path on selected CSRs to include the new environments.

Follow the instructions in the section Migration Path Diagram to add environments to the migration path.
Click Add new env. to CSR.
Select the Update option for each CSR you want to update.
Optionally, select the Update Objects List option if you want to copy the objects from either the Base or Development environment to the newly added environments. Then select Base or Dev.

Post Migration Steps

The Post Migration Steps Maintenance table defines the actions to be taken on certain types of objects in an archive set after it has been migrated. Post migration steps are either manual or automatic, meaning they are performed either by users or by Stat.

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

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


If selected, activates the value in Stat

Post Migration Step
(Required Value)

The type of step. Options include Custom Command, Run DMS, Create Project Build Script, Compile Cobol, and Manual.

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.

(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

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating