Chat now with support
Chat with Support

Stat 6.0 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department 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

Step 4 (PS): Define Primary Permission Lists

Each developer needs a unique Permission List defined in PeopleSoft. In PeopleSoft 8.x, Operator Classes are defined in Operator Security. In PeopleSoft 8.x, Permission Lists are defined in Maintain Security. In PeopleSoft 8.4x, Permission Lists are defined in Security

Bear in mind the following considerations:

1
Select PeopleTools | Security Administrator | Use | Permission List | Save As. Then save the existing Primary permission list as a unique name, perhaps based on userid.
4
Select PeopleTools | Maintain Security | Use | Roles | General | Add.
8
Select PeopleTools | Maintain Security | User Profiles | Roles | Update/Display.

Step 5 (PS): Define Object Security Groups

Each developer must have a unique Object/Definition Security group. Each group must start with “STAT_” and end with the operator ID as defined in User Security.

When you run the PS Object Lock Sync job, this group is populated with all of the objects assigned to the developer.

1
Select PeopleTools | Object Security | File | New Group.
5
Select File | Save. The name of the group must follow the following naming convention: StatPSOprid_OPRID, where StatPSOprid is the value declared in Step 1, for example, “STAT,” and where OPRID is the operator ID of the current developer for which this group is being created.
6
7
Select File | Save As. Then copy the same group you just created for each applicable developer.

Step 6 (PS): Set Up Global Definition Group STAT_READ

For each environment, you need to set up a global Definition Security group that contains all the securable objects. This security group serves as a cross reference to determine which objects a developer should be able to access but to which they cannot save changes and will eventually be assigned to all the developers' unique permission lists. The Stat Central Agent job PS Object Lock Sync populates global security groups and keeps them in sync with the PeopleSoft environments and the Stat Repository.

You must use the following naming conventions when setting up a global Object Security groups for excluded objects:

For example, if the operator ID is the default, “STAT,” the global object security group will be “STAT_READ.” During setup, the only object you need to add to this group is the placeholder object.

To initially define this group, perform a File | Save As function on one of the groups you just created for a developer. When you run the PS Object Lock Sync job, this group is populated with all of the appropriate objects.

Select File | Save As. The name of the group must conform to the proper naming convention.
Select Go|PeopleTools|Object Security|File|New Group.
Select File|Save As. The name of the group must conform to the proper naming convention.

Step 7 (PS): Set Up Global Definition Group STAT_EXCLUD

For each environment, you need to set up another global Object Security group for all the objects excluded from object security - the Exclude Group. This group will contain all the objects that are excluded from Object security in PeopleSoft. You must set up this group even if you are not excluding any objects. The Stat Central Agent job PS Object Lock Sync populates global security groups and keeps them in sync with the PeopleSoft environments and the Stat Repository.

You must use the following naming conventions when setting up a global Object Security groups for excluded objects:

For example, if the operator ID is the default, “STAT,” the global object security group will be “STAT_EXCLUD.” During setup, the only object you need to add to this group is the placeholder object.

Select File | Save As. The name of the group must conform to the proper naming convention.

If you have closed Object Security:

Select Go | PeopleTools | Object Security | File | New Group.
Select File | Save or File | Save As. The name of the group must conform to the proper naming convention.
Related Documents