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

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:

•
In PeopleSoft 8.x, a user gets their definition Security Permission from their Primary Permission List, not through Roles
•
In PeopleSoft 8.x, the permission list that was originally the user’s primary permission list must now be cloned and added to a role, which in turn must be assigned to the user. This enables the user to retain his or her original menu and process security.
Defining Permission Lists (8.1x):
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.
For example, with the user BODELL, the current primary permission list will be cloned to BODELL1.
2
Assign the saved permission list to User Profile as the Primary Permission List.
3
Create a new role for the former primary permission list.
By doing this and then adding the role back into the OprID definition, Component & page permission levels remain current. Also, subsequent changes to security of former permission lists would then be inherited via the role.
4
Select PeopleTools | Maintain Security | Use | Roles | General | Add.
5
Enter a name for the new Role (e.g. Stat_Former_Pclass).
6
Click the Permission Lists tab, then the Permission Lists drop-down list in the grid. Select the primary Permission List you saved earlier. Then save your changes.
7
Add new Role to OprId
8
Select PeopleTools | Maintain Security | User Profiles | Roles | Update/Display.
9
Click on the Role Name drop-down list in the grid and select the new Role created.

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.

To define a security group:
1
Select PeopleTools | Object Security | File | New Group.
2
Select Pages from the drop-down list (or the object type you used for your placeholder).
3
For PeopleSoft 8.5.3 and lower, locate ZZSTATDONOTDEL in the Excluded Pages section.
4
For PeopleSoft 8.5.3 and lower, click the single left arrow button to add ZZSTATDONOTDEL to the Pages section.
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.
For example, the correct group name using this example would be: STAT_BODELL.
6
Click OK.
* 
NOTE: The custom permission lists created for OprIDs should not be confused with the OprID value which is expected here as the substitution for OPRID
7
Select File | Save As. Then copy the same group you just created for each applicable developer.
For example, if your developer list is BODELL, JROBERTS, PNEWMAN, then copy the group and create STAT_JROBERTS and STAT_PNEWMAN.

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:

•
The name starts with the assigned Stat Operator Id
•
The name ends with _READ

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.

To define a global security group:
•
If you still have Object Security open from Step 7, do one the following:
•
Copy any of the already created groups for your developers (i.e. copy STAT_BODELL)
•
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.
•
For PeopleSoft 8.5.3 and lower, select “Pages” from the drop-down list and locate ZZSTATDONOTDEL in the Excluded Pages section. Then click the single left arrow button to add ZZSTATDONOTDEL to Pages section.
•
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:

•
The name starts with the assigned Stat Operator Id
•
The name ends with _EXCLUD, note there is no E on the end

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.

To define an exclusions security group:
1
If you still have Object Security open from Step 7, do one the following:
•
Copy any of the already created groups for your developers (i.e. copy STAT_BODELL or STAT_READ).
•
Select File | Save As. The name of the group must conform to the proper naming convention.
* 
NOTE: Make sure to omit the final ‘E’ from the group name.

If you have closed Object Security:

•
Select Go | PeopleTools | Object Security | File | New Group.
•
For PeopleSoft 8.5.3 and lower, select “Pages” from the drop-down list and locate ZZSTATDONOTDEL in the Excluded Pages section. Then click the single left arrow button to add ZZSTATDONOTDEL to Pages section.
•
Select File | Save or File | Save As. The name of the group must conform to the proper naming convention.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating