Chat now with support
Chat with Support

Stat 6.3 - 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

Setting Up Physical Object Lock Exclusions

The second tab of the PS Options window, Object Lock Exclusions, displays a list of all the PeopleSoft proprietary object types that can be physically locked in the selected non-staging environment. You can exclude any of these file types from physical object locking, which lets you control which types of objects users can physically lock while operating in a certain environment. The list of object types varies depending on the version number of the PeopleSoft environment.

4
Click OK or Apply.

For more information on physical object locking, see PeopleSoft Proprietary Object Security and the “Object Management” sections in the change management chapters of the Stat User Guide.

Setting Up Migration Approval Lists

If an environment requires the approval of certain users before an archive set can be migrated into it, you can specify who these users are in the Migration Approval List tab. Stat activates this tab only if Req. Migr. Approval has been selected for the environment in the PeopleSoft Environment Connection Maintenance table.

When setting up a migration approval list, you can include different approver groups, including individual users and entire user classes or a combination of the two. The approval of any user or user class that you add to a list can be either required or optional.

Approval requirements that involve multiple approver groups or that can be satisfied in more than one way are defined using AND and OR operators. As you add approver groups using AND and OR operators, Stat displays the list as a tree structure and in the form of a SQL statement at the bottom of the window.

For example, let’s say a migration to a particular environment in the Financial Services service domain can be approved in one of two ways:

In this case, your approval list would look like this:

To further illustrate, let’s say that the migration must be approved by:

In this case, the approval list would look like this:

It is recommended that before setting up a migration approval list, you have a basic idea of what approver groups (users and user classes) you want involved in the approval process as well as the relationships between these groups, which you define using AND and OR operators. For example, if the approval of one or more approver groups are required, you would begin the approval list with the AND operator. If, however, the approval of only one of two or more approver groups are required, you would begin the list with the OR operator.

Click AND if the approval of one or more approver groups are required
Click OR if the approval of one of two or more approver groups are required
3
In the Service Domain field, select the service domain that you plan to associate the environment with in the PeopleSoft Migration Path Maintenance table.
4
In the Approver Type field, select the approver group you want to add to the list.
Options include User and User Class.
5
In the Approver Name field, select the name of the user or user class you want to add.
6
In the Required field, select Required if the approval is required or Optional if it is not required.
The Required option means that the individual user and every member of the user class must approve the migration. Optional means that the individual user’s approval is not required, whereas for user classes, it means that the approval of only a specified minimum number of users within that class is required.
7
If you selected User Class in the Approver Type field and Optional in the Required field, specify the minimum number of users in that class who must approve the migration in the Number field.
8
Click Add.
b
Click AND or OR.
13
Click OK or Apply.

Copying PeopleSoft Environments

If you need to define a PeopleSoft environment that closely resembles an existing environment, you can save time by copying the definition of the existing environment and editing the copy as needed. When you copy a PeopleSoft environment, all the information gets copied over, including file locations and selected PS options.

2
Click Copy.

Pre/Post Migration Steps Parameters

In the Pre/Post Migration Steps Parameters Maintenance table, you can define user and server-based parameters that can be included in the definition of pre and post migration custom command steps. This provides a convenient way to insert variables such as server names and passwords in custom commands. And because parameter values can be encrypted, sensitive information that you do not want visible to the users executing the commands can be secured.

The table also includes a number of predefined parameters, which specify commonly invoked values used to login into an environment during a migration or to invoke Stat web services.

A user must have one of the following rights to open the Pre/Post Migration Step Parameters Maintenance table:

For more information on pre and post migration steps, see the sections, Pre Migration Steps on page 152.

The parameters defined in this table are public, meaning that they specify a set default parameter values that can be included in the definition of any custom command pre and post migration step. It is possible, however, to define parameters and parameter values that are specific to individual users or servers. User and server-specific parameters can be used in conjunction with public parameters, while parameter values specific to users and servers can be used to override the default values of public parameters:

CSR_ID

CSR ID

All

SD_CD

Service domain code

All

PS_PROJECT

PeopleSoft Project

PS and Generic only

SOURCE_DB_NAME

Source database name

All

SOURCE_DB_PASSWORD

Migration source database user password

All

SOURCE_DB_USERNAME

Migration source database user name

All

SOURCE_ENV_CD

Source environment code

All

TARGET_APPLSYS_PASSWORD

Target application system password

Oracle Apps only

TARGET_APPLSYS_USERNAME

Target application system user name

Oracle Apps only

TARGET_APPS_PASSWORD

Target apps password

Oracle Apps only

TARGET_APPS_USERNAME

Target apps user name

Oracle Apps only

TARGET_DB_LISTENER_PORT

Target database listener port

All

TARGET_DB_NAME

Migration target database name

All

TARGET_DB_PASSWORD

Migration target database user password

All

TARGET_DB_USERNAME

Migration target database user name

All

TARGET_ENV_CD

Target environment code

All

TARGET_HOSTNAME

Target host name

All

TARGET_OBJECT_NAME

Target object name

All

TARGET_OBJECT_PATH

Target object path

PS and Generic only

TARGET_SERVICE_NAME

Target service name

All

TARGET_SYSTEM_PASSWORD

Target system password

Oracle Apps only

TARGET_TNS_ENTRY

Target TNS entry

 

2
Click New.
7
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating