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

PeopleSoft Object Security Setup Instructions

Object Security setup involves both the Stat Repository and the PeopleSoft development environments. Object security terminology differs somewhat between the different versions of PeopleTools that Stat supports, and although the following instructions are intended for all supported versions of PeopleTools, the examples are based on PeopleTools 8.1x, as does the terminology when specificity is required. This chapter assumes that the administrator setting up object locking in Stat has a working knowledge of PeopleSoft security and access to the PeopleBooks for their release of PeopleTools.

Some of the terminology differences include:

•
The term ‘Operator Classes’ is replaced by the terms ‘Permission Lists’ and ‘Roles’ in PeopleTools 8.1x and 8.4x
•
The term ‘Object Security' in PeopleTools 8.1x is replaced by the term 'Definition Security' in PeopleTools 8.4x

In general terms, the procedure for setting up object security between Stat and PeopleSoft (regardless of version) entails defining a unique Object/Definition Security Group for each developer. The security groups are associated to the user’s Primary Permission List (Primary Operator Class). The security groups have a designated format of STAT_Operid. You will need to decide what format to use for your new Primary Permission Lists or Operator Classes in your environments. Note that Object/Definition Security is assigned at the Primary Permission List level, not by the Roles associated with a user.

For PeopleSoft 8.5.3 and lower, to ensure that the security group is never empty, you create a unique object that always resides in the security group. This is referred to as the placeholder object.

After the groups are defined and associated to users in PeopleSoft, turn on object locking at the service domain level in Stat, turn on Physical Locking at the environment level, and then set up an Agent job to synchronize the groups.

1
Assign Stat’s PS Oprid.
2
Assign developer’s PS Oprids.
3
Add Placeholder object (for PeopleSoft 8.5.3 and lower).
4
Define Primary Permission Lists.
5
Define Definition Security Groups.
6
Define global definition Group, STAT_READ.
7
Define global definition Group, STAT_EXCLUD.
8
Assign security groups to Permission Lists. For STAT_READ group, set Display Only flag.
9
Set up lock exclusions, if necessary.
10
Activate PS Locking in Stat.
11
Set up Stat Central Agent.

Step 1 (Stat): Assign Stat's PS Oprid

Step 1 (Stat): Assign Stat’s PS Oprid

Object security requires that you define a PeopleSoft Operator ID in Stat for each environment. PS Oprid is a prefix for Definition Security Groups. A default value of “STAT” is assigned by the system, for example, STAT_READ or STAT_EXCLUD. You can keep the default ID or specify a different one. The ID can be up to thirty characters in length and does not have to be set up in PeopleSoft.

To assign a PeopleSoft ID:
1
In the PeopleSoft Environment Connection Maintenance table, select the row for the environment you want. Then click in the Stat PS Oprid column and enter the ID you want.
* 
NOTE: If you assign an ID that is different than the default, you need to modify the PS_OPRID value for each PS environment that uses Object Security as determined by the service domain. This includes ALL environments in the service domain whether or not Exclusions will be added.

Step 2 (Stat): Assign Developers' PS Oprids

Step 2 (Stat): Assign Developers’ PS Oprids

For each PeopleSoft environment using Object Security, you need to define a unique PeopleSoft Oprid for each developer. It is recommended that after you define the Oprids, you have each developer specify his or her own password.

In Stat, you can enter PeopleSoft Oprids and passwords from three different locations. As a system administrator, you can enter them either by user from the User Maintenance table or by environment from the PeopleSoft Environment Connection Maintenance table. In addition, users can enter their own IDs and/or passwords from their workstations by selecting User Options | PeopleSoft Options.

To add PeopleSoft OprIds to Stat:
1
Do one of the following to open a PS Options window.
•
If by user, select Maintenance | Security Settings | User Maintenance. Then in the User Maintenance table, double-click on the user you want. This opens the Other Information window. Click the PS Options tab.
•
If by environment, click PS Options... in the PeopleSoft Environment Connect Maintenance table.
2
Select the row for the user or environment you want. Then click in the PS Oprid column and enter the Oprid.
3
Click OK or Apply to save your work.
4
Inform users that they should now specify their PeopleSoft passwords from their own workstations.

Step 3 (PS): Add Placeholder Object (for PeopleSoft 8.5.3 and lower)

The next step is to create a single, “placeholder” object for each PeopleSoft environment in the Application Designer. These objects keep Object Security groups open while the Stat Central Agent processes synchronization jobs. The Placeholder object’s object type must not be an excluded object type, and the object itself must not be deleted from PeopleSoft.

You must use the following naming conventions when adding a placeholder object to a PeopleSoft environment:

•
The name starts with ZZ and ends with DONOTDEL.
•
The operator ID assigned to Stat goes in-between.

For example, if the operator ID is the default, “STAT,” the placeholder object would be “ZZSTATDONOTDEL.”

Placeholder objects are only used by Stat. You can use copies of other objects or new objects as long as you follow the above naming conventions.

* 
IMPORTANT: Do not use a record as the object placeholder since PeopleSoft only allows record names to have a length of 15. It is recommended that you use a panel/page instead.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating