Converse agora com nosso suporte
Chat com o suporte

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.

To set up object lock exclusions:
1
In the PeopleSoft Environment Connection Maintenance table, select the non-staging environment you want and click PS Options....
Stat opens the PS Options window for selected environment.
2
Select the Object Lock Exclusions tab.
This tab is available only for non-staging environments.
3
Click the check box next to each object type you want to exclude from physical object locking. To select all the objects, click Select All. To deselect multiple objects, click Select None.
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:

•
By a certain user AND one user in the Administrator user class
OR
•
By two users in the Fin Developer user class

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

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

•
Two users
AND
•
One user in the Administrator user class OR two users in the Fin Developer user class.

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

* 
NOTE: Migration approval lists closely resemble status transfer approval lists and the procedures for defining them are much the same. For more information on transfer approval lists, see Setting Up Transfer Approval Lists .

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.

To set up a migration approval list:
1
Do one of the following:
•
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
The operator icon is added to the approval list diagram.
2
Click on the AND or OR operator icon you just added.
* 
TIP: The icon background appears blue when selected and changes to gray when other fields or action buttons are activated. As long as the background of the operator icon is blue or gray, then approver groups and other operators can be attached to the operator.
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.
When adding approvers, be aware of the following:
•
Although you can add any user or class to an approval list, be aware that only users that have access to an environment and the selected service domain (as defined in the User Maintenance table) will be able to approve a migration into that environment or receive email notifications regarding their pending approval. If an approver does not have access to the environment, the migration cannot be approved until either the user is granted access to the environment or the migration’s approval requirements are overridden by another user with proper security rights. For this reason, it is recommended that you first verify users have access to a particular environment and service domain before adding them to an approval list.
•
Adding individual users to approval lists could create problems if those same users are later inactivated or have their service domain and environment access restricted. For this reason, it is recommended that you add user classes to approval lists rather than individual users whenever possible.
•
Users assigned to a migration approval list must have the user class rights to operate in the same change management module in which the migration takes place. Also, you can assign user class rights that enable users to migrate objects regardless of approval status and also to approve migrations on the behalf of other users.
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.
The approver is added to the tree structure under its approver group label and the initial AND or OR operator. Required approvers are displayed in bold.
At this point, how you proceed depends on the different approver groups you want to add to the list and how you want to define the relationships between these groups using AND and OR operators.
9
(Optional) Do the following to add additional AND or OR operators to your approval list:
a
Depending on the relationship between approver groups in your list, select the operator icon to which you want to attach additional operators.
b
Click AND or OR.
c
Repeat as necessary to add more operator icons to the approval diagram.
10
(Optional) To add additional user classes, select the appropriate operator icon in the approval diagram and repeat steps 4 through 8.
When you the first add an individual user to an approval list, Stat automatically creates the ad hoc group “users” in the approval diagram and attaches it to the appropriate operator icon. All subsequent users you add to the list must belong to this group.
* 
TIP: In a scenario in which you want to create approval relationships between multiple user approver groups, you may consider adding users to new user classes or queues created expressly for this purpose.
11
(Optional) To add additional users, select the “users” group and repeat steps 4 through 8.
12
(Optional) Do any of the following to edit the diagram as needed:
•
To change an operator from AND to OR or from OR to AND, right-click on the icon.
•
To change the Required status of an approver, right click on it in the diagram. This changes required user classes to optional with 1 minimum user approval.
•
To change the minimum number of user approvals in an optional user class, double-click on the group label and specify the minimum number of user approvals you want.
•
To move approver groups or entire operator relationships, click and hold on the group label or operator icon and drag and drop to a different operator icon in the diagram.
•
To delete approver groups or entire operator relationships, click and hold on the group label or operator icon and drag and drop to the Trash Can icon.
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.

To copy a PeopleSoft environment definition:
1
In the PeopleSoft environment Connection Maintenance window, select the environment definition you want to copy.
2
Click Copy.
Stat prompts you to specify a database code and short description.
3
Specify the database code and short description. Then click OK.
4
Edit the new environment definition as needed.

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:

•
Pre/Post Migration Server Parm - Add
•
Pre/Post Migration Server Parm - Edit
•
Pre/Post Migration User Parm - Add
•
Pre/Post Migration User Parm - Edit

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:

•
User-specific parameters (such as user names and passwords) apply to particular Stat users, who define them themselves. For more information on user-specific parameters, see the Stat User Guide, “Appendix: User-Specific Parameters.”
•
Server-specific parameters (such as home directories and version numbers) apply to particular file servers. You can define server-specific parameters here, or you can define them on the File Servers tab of the Object Type Maintenance window. For more information, see the section, Server-Specific Pre/Post Migration Step Parameters .
•
Predefined parameters are commonly used parameters included as a convenience. These parameters, which specify values used to login to an environment during a migration or to invoke Stat web services, are read-only and cannot be modified or removed. Certain predefined parameters are specific to particular change management modules, as noted in the table below:
Predefined Parameter
Description
Module

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

 

* 
NOTE: The parameters used to login into source and target environments include the database (identified by name or environment code) as well as user names and passwords. These values are encrypted.
To define a pre/post migration step parameter:
1
Depending on the type of parameter you want to define, select either the User Parameters or Server Parameters tab.
2
Click New.
3
Enter the parameter name.
4
Enter the parameter value.
This is the parameter’s public default value, which can be overridden by a user or server-specific value that is defined for the public parameter.
* 
NOTE: If you do not enter a parameter value, the value defaults to null.
5
Select the encrypted option if you do not want the parameter value to be visible to users executing the pre/post migration custom command step.
6
(Optional) Enter a description of the parameter.
7
Click OK.
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação