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

Comparing File and Schema Objects

You can use the File Comparison Tool to compare the contents of file and schema objects and easily identify differences.

In the File Comparison window, the contents of the two file or schema objects are displayed side by side separated by a center divider. Differences between the two versions are highlighted with color. The colors may be customized by the user. Using the default color values, the following occurs:

•
Differences between two versions are highlighted in red
•
Text that only occurs in one version is matched by a corresponding grey area in the other version
•
Minor differences, such as whitespaces, are picked out in blue

The tool finds lines of text that correspond to each other and does not depend solely on the line number.

* 
NOTE: When comparing file objects that have been migrated between Unix and Windows environments, it is recommended you only compare objects based on the Image format. FTP inserts carriage returns into ASCII-type objects when they are migrated from a Windows environment to a Unix environment, and this may cause the File Comparison Tool to report differences between what is in fact the same file object. For more information on file formats, see the Stat System Administration Guide, Chapter 4, “General Maintenance Tables.”

Optionally, Stat can use an external third party compare tool for comparing files.

To switch to an external compare tool:
1
Install a third party compare tool, for example, WinMerge.
2
Open the Stat.ini file in a text editor and add a line similar to the following to the Options section (the following example is based on using WinMerge):
ExternalCompareTool=C:\Program Files (x86)\WinMerge\WinMergeU.exe %1 %2 /dl "%3" /dr "%4"
Where:
%1 - Placeholder for first file
%2 - Placeholder for second file
%3 - Placeholder for left source description
%4 - Placeholder for right source description
NOTE: The external third party compare tool must be installed separately and is not included with the Stat installation package

 

 

Change Management for PeopleSoft

•
Object Management (PeopleSoft)
•
Object Archives (PeopleSoft)
•
Object Migrations (PeopleSoft)

Object Management (PeopleSoft)

Setting Up Your PeopleSoft Connections

Before Stat can interact with the objects in your PeopleSoft environments, it must first connect to those environments. For certain activities, such as editing or auto-migrating objects, it does this using the PeopleSoft Operator ID and password assigned to you for each environment. This allows Stat to access these environments and physically lock the objects you want to work with or open the object you want to edit. Your system administrator can specify your operator ID and password for each environment in the User Maintenance table, or you can do it yourself in the PeopleSoft Options window.

The PeopleSoft Options window displays a list of all the PeopleSoft environments defined in Stat that you can connect to. Here you can define a separate PeopleSoft operator ID and password for each environment.

In this window, you can also configure Stat to do the following:

•
Open PeopleSoft and automatically log you in to the environment in which you have staged objects during a PeopleSoft migration. This way, you do not have to open the project in PeopleSoft manually to verify the staging of objects.
•
Automatically migrate the objects in your project from the staging database to the target environment during a PeopleSoft migration
•
Automatically migrate the objects out to all the environments included in the distribution list when migrating to a distribution environment

If you want Stat to perform any of these tasks, you must specify both your PS Operator ID and password for the selected environment.

Staging databases and PeopleSoft environments are defined by system administrators in the PeopleSoft Environment Connection Maintenance table, which is described in the Stat System Administration Guide, Chapter 4, “General Maintenance Tables.” Migration paths and distribution environments are defined by system administrators in the PeopleSoft Environment Migration Path Maintenance table, which is described in the Stat System Administration Guide, Chapter 5, “Service Domain-Specific Maintenance.”

To set up a PeopleSoft Operator ID and password:
1
Select User Options | PeopleSoft Options.
This opens the PeopleSoft Options window which displays a list of all the PeopleSoft environments that you can connect to.
2
Select the PeopleSoft environment that you want to connect to.
3
Enter a PS Operator ID in the PS Oprid column.
This ID is case-sensitive, must correspond to the PeopleSoft Operator ID for the given environment, and must be no more than 30 characters in length.
4
Click the corresponding Enter Password button in the PS Password column.
5
In the Change Password dialog box, enter the password in the New Password and Verify Password fields.
This password is case-sensitive, must correspond to your PeopleSoft Operator ID’s password for the given environment, and must be no more than 32 characters in length.
6
Click OK.
A green checkmark icon appears to the right of the Enter Password button indicating that a password has been created.
7
(Optional) Select CLI Open for any designated staging database.
Selecting this option configures Stat to login automatically to the environment and open the project you just staged. You can then verify the staging of objects and push the project to the target environment.
8
(Optional) Select CLI Auto-Migr for any environment designated in a migration path as either the target environment for staged objects and/or as a distribution environment.
For a single target environment, selecting this option automatically migrates objects to the target environment from the staging database. To use CLI functionality for a distribution environment, you must select it for each environment that qualifies for auto-migration within the distribution environment list. For more information, see Auto-Migrating PeopleSoft Projects .
When migrating PeopleSoft objects, you have the option of disabling the auto-migration feature.
Stat executes a DataMover script to auto-migrate non-App Designer objects.
9
If you selected either CLI Open or CLI Auto-Migration, specify the directory of the user’s PS Tools executable in the PS Tools Directory field.
This information is required if you plan to use CLI functionality in any PeopleSoft environment. You can specify a directory location either manually or by browsing for the location:
•
If the executable is in the same location as when first installed, keep the default value, “PS_HOME\bin\client\winx86,” where PS_HOME is the user’s PS_HOME variable defined in the PeopleSoft configuration
•
If the executable has been moved to a different location within the %PS_HOME% directory, specify the new subdirectory, for example, “PS_HOME\setup”
•
If the executable has been moved to a location outside the %PS_HOME% directory, specify the entire location including the drive, for example, “G:\software\psft\ps815”
10
(Optional) After specifying the PS Tools directory location, test the connection to an environment by selecting it and clicking Test Connection.
If Stat cannot connect, it displays a PeopleSoft generated error message, for example, “Unsuccessful CLI connection to PS database.”
11
Save your changes by clicking either Apply or OK.

Setting Up Your PeopleSoft Connections

Object Management (PeopleSoft)

Before Stat can interact with the objects in your PeopleSoft environments, it must first connect to those environments. For certain activities, such as editing or auto-migrating objects, it does this using the PeopleSoft Operator ID and password assigned to you for each environment. This allows Stat to access these environments and physically lock the objects you want to work with or open the object you want to edit. Your system administrator can specify your operator ID and password for each environment in the User Maintenance table, or you can do it yourself in the PeopleSoft Options window.

The PeopleSoft Options window displays a list of all the PeopleSoft environments defined in Stat that you can connect to. Here you can define a separate PeopleSoft operator ID and password for each environment.

In this window, you can also configure Stat to do the following:

•
Open PeopleSoft and automatically log you in to the environment in which you have staged objects during a PeopleSoft migration. This way, you do not have to open the project in PeopleSoft manually to verify the staging of objects.
•
Automatically migrate the objects in your project from the staging database to the target environment during a PeopleSoft migration
•
Automatically migrate the objects out to all the environments included in the distribution list when migrating to a distribution environment

If you want Stat to perform any of these tasks, you must specify both your PS Operator ID and password for the selected environment.

Staging databases and PeopleSoft environments are defined by system administrators in the PeopleSoft Environment Connection Maintenance table, which is described in the Stat System Administration Guide, Chapter 4, “General Maintenance Tables.” Migration paths and distribution environments are defined by system administrators in the PeopleSoft Environment Migration Path Maintenance table, which is described in the Stat System Administration Guide, Chapter 5, “Service Domain-Specific Maintenance.”

To set up a PeopleSoft Operator ID and password:
1
Select User Options | PeopleSoft Options.
This opens the PeopleSoft Options window which displays a list of all the PeopleSoft environments that you can connect to.
2
Select the PeopleSoft environment that you want to connect to.
3
Enter a PS Operator ID in the PS Oprid column.
This ID is case-sensitive, must correspond to the PeopleSoft Operator ID for the given environment, and must be no more than 30 characters in length.
4
Click the corresponding Enter Password button in the PS Password column.
5
In the Change Password dialog box, enter the password in the New Password and Verify Password fields.
This password is case-sensitive, must correspond to your PeopleSoft Operator ID’s password for the given environment, and must be no more than 32 characters in length.
6
Click OK.
A green checkmark icon appears to the right of the Enter Password button indicating that a password has been created.
7
(Optional) Select CLI Open for any designated staging database.
Selecting this option configures Stat to login automatically to the environment and open the project you just staged. You can then verify the staging of objects and push the project to the target environment.
8
(Optional) Select CLI Auto-Migr for any environment designated in a migration path as either the target environment for staged objects and/or as a distribution environment.
For a single target environment, selecting this option automatically migrates objects to the target environment from the staging database. To use CLI functionality for a distribution environment, you must select it for each environment that qualifies for auto-migration within the distribution environment list. For more information, see Auto-Migrating PeopleSoft Projects .
When migrating PeopleSoft objects, you have the option of disabling the auto-migration feature.
Stat executes a DataMover script to auto-migrate non-App Designer objects.
9
If you selected either CLI Open or CLI Auto-Migration, specify the directory of the user’s PS Tools executable in the PS Tools Directory field.
This information is required if you plan to use CLI functionality in any PeopleSoft environment. You can specify a directory location either manually or by browsing for the location:
•
If the executable is in the same location as when first installed, keep the default value, “PS_HOME\bin\client\winx86,” where PS_HOME is the user’s PS_HOME variable defined in the PeopleSoft configuration
•
If the executable has been moved to a different location within the %PS_HOME% directory, specify the new subdirectory, for example, “PS_HOME\setup”
•
If the executable has been moved to a location outside the %PS_HOME% directory, specify the entire location including the drive, for example, “G:\software\psft\ps815”
10
(Optional) After specifying the PS Tools directory location, test the connection to an environment by selecting it and clicking Test Connection.
If Stat cannot connect, it displays a PeopleSoft generated error message, for example, “Unsuccessful CLI connection to PS database.”
11
Save your changes by clicking either Apply or OK.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating