Chat now with support
Chat with Support

Stat 6.1 - 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: Stat Web Services Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

Testing Environment Connections

After defining an environment in the maintenance table, you can make sure that you have entered all the information correctly by clicking Test Connection. This makes Stat establish a connection to the newly defined environment. If successful, Stat immediately disconnects from the environment and displays a “Connection Successful” message. If Stat is unable to connect, it displays an error message.

You can also test connections to multiple databases simultaneously. To test multiple connections, hold the <Ctrl> or <Shift> keys and select the databases you want to test. Then click Test Selected. Stat attempts to establish a connection to each database and reports its results in the Database Test Connect window

Note that when you test a single environment, Stat does not validate the values specified in the fields Host Name, Service Name, or DB Listener Port. If any of these fields are not configured properly, the Stat Central Agent will log an error when the user attempts to migrate an object to or from the environment. When you test multiple connections, however, Stat does test both client and agent connections, including Host Name, Service Name, DB Listener Port or (in the case of Oracle-based environments) TNS Entry.

NOTE: When testing environment connections in the Stat Web Client, Stat Web attempts to connect using the Host Name, DB Listener Port, Service Name, or the TNS Entry values specified in the Stat maintenance tables for each particular environment. If there is no TNS Entry value specified for an environment, it uses the Host/Port/Service Name values. If a TNS Entry value is specified, it uses that value and disregards the others.

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.

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.

Click New.
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.
In the File Server field, select the server that the file directory is on.
In the File Path field enter the path of the file location starting after the predefined server's root or home path.
(Optional) Select Default Path if you want this to be the file type’s default source file location.
Click Test Connection.

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.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating