Chat now with support
Chat with Support

Stat 6.2 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department Maintenance Issue Tracking 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: REST Web Services API Appendix: SOAP-Based Web Services API Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

Inactivating PeopleSoft Environments

To inactivate an environment, de-select Active. Stat displays a warning message if the environment is currently part of a migration path.

* 
CAUTION: Be careful inactivating environments that are part of migration paths. Objects in inactive environments cannot be archived or migrated.

Managing File Locations by Environment

For each PeopleSoft environment connected to Stat, you can define an unlimited number of source file locations for each type of file object in that environment. When Stat creates an archive set for a file object from a PeopleSoft environment, it searches for the file in the first location you specified (Path ID = 1). If the file is not there, Stat searches in the second location, and so on. If you plan to archive file objects from, or migrate to, a particular PeopleSoft environment, you must define at least one source file location for each file type.

To define source file locations by environment, select the environment in the PeopleSoft environment Connection Maintenance window and click File Locations. This opens the Stat File Locations window, which displays a list of all the active PeopleSoft file types defined in Stat. For each file type, you can specify as many source file locations as you want. Source files can be located on different servers, or they can be located on the same server but in different directories.

* 
NOTE: You can also specify source file locations by file type. For more information, see Object Type Maintenance .
To set source file locations for an environment:
1
Click New.
2
In the File Type field, select the file type for which you want to define a location.
Stat assigns a unique ID number to each file location you define per file type and displays the number in the Path ID field. This number determines the order that file locations are searched during the file archive process. The path with the ID 1 is searched first, and so on.
3
In the File Server field, select the server that the file directory is on.
4
In the File Path field enter the path of the file location starting after the predefined server's root or home path.
5
(Optional) Select Default Path if you want this to be the file type’s default source file location.
This is where Stat will copy file objects of the selected type during a migration. Each file type must have one of its source file locations designated as the default.
6
Click Test Connection.
See the section, Testing File Locations, Servers, and Default Directory Locations for more information.
7
Define additional file locations as needed.
8
Save your changes by clicking either Apply or OK.

PeopleSoft Options

To physically lock objects in a PeopleSoft environment, a user requires an operator ID and password by which to connect to that environment. You can define these operator IDs and passwords by user, as discussed in the section, Defining User Classes , or you can define them by environment. This is done in the PS Options window. In this window, you can also exclude certain object types from object locking within a selected environment and create migration approval lists.

Setting Up User Connections

The PS Options by Environment tab resembles the PS Options tab of the Other User Information window. The difference is that unlike the PS Options tab, which displays a list of all the environments that a specific user can connect to, the PS Options by Environment tab displays a list of all the users that can connect to a specific environment. From here you can assign to each user a separate operator ID and password. You can also configure CLI functionality. For more information, see Defining Stat Users .

* 
NOTE: Users can define their own IDs and passwords by selecting User Options | PeopleSoft Options and entering the information in the PeopleSoft Options window. In addition, users can share the same PS Operator ID and password for staging purposes if that is how your PeopleSoft environment is configured. For example, you could assign all users the operator ID “PS” or “VP1.”
To set up user environment connections:
1
In the maintenance table, select the environment you want and click PS Options....
Stat opens the PS Options window for that environment.
2
Select the user that you want to set up the database connection for.
3
Complete the remaining steps for defining the user’s PS operator ID and pass-word and, optionally, enabling CLI functionality.
These steps are identical to those described earlier in the section, Defining User Classes .
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating