Chat now with support
Chat mit 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 8 (PS): Assign Object Security Groups to Permission Lists

Permission Lists have been created that are unique to each developer. By assigning the appropriate collection of created groups to these permission lists, you assign the collection of groups to the individual developer.

From this point on, the developers will be impacted in PeopleSoft. They will not be able to access objects until the Stat Central Agent runs the PS Object Lock Sync jobs.

Associate the appropriate Object Security groups to the Permission Lists that you defined in Step 4.

1
Select PeopleTools | Object Security | File | Open | Permission List.
2
Open the Permission List created for a developer back in Step 4, part 'b' of this document. For example, for the developer, BODELL, we created a clone of his primary permission list and called it BODELL1.
Notice the list of Security Groups on the right-hand window. You should see a group name created for each developer, the exclude group, and the all read-only group that were created earlier.
3
Hold down the [Ctrl] key and within the noted Excluded Group ID list in the right window, click to highlight the three groups: STAT_READ, STAT_EXCLUD and STAT_%OPRID%, where %OPRID% is the current developer whose permission list you have opened.
For example, for Oprid BODELL, the permission list is BODELL1 and the groups STAT_READ, STAT_EXLUD and STAT_BODELL have been highlighted.
4
Click the single left arrow button.
The groups selected should move into the left window.
5
Select Change | Display Only.
6
Select STAT_READ and click OK.
The STAT_READ group has been changed to Display Only = Yes to indicate its cross-reference nature. Items in this list will be accessible by all developers, but without any change rights. The other groups remain Display Only= No, since they reflect individual ownership groups whose objects have been assigned and approved for changes to be made OR they are part of the exclusion group that should never be locked from changes due to PeopleSoft functionality.
7
Repeat for each developer.

Step 9 (Stat): Exclude Objects

You can exclude object types from PeopleSoft Proprietary Object Security by selecting them in the PeopleSoft Environment Connection Maintenance table. This is done per environment. For example, you can exclude queries from PeopleSoft Proprietary Object Security in Production but include queries in Development. Also, you can exclude an entire environment from PeopleSoft Proprietary Object Security either by deselecting the Use Physical Locking option for that environment in the PeopleSoft Connection Maintenance table or by excluding all the object types for that environment. If you have used either Primary (no access to App Designer) or Secondary (read only or no access to all objects in Object Permissions) PeopleSoft Security on an environment, use these lock exclusions. There is no point in having Stat take time to lock objects if it is not necessary. You may find that you want Stat to only lock objects on one or two development environments.

To exclude objects:
1
Select Maintenance | General | PeopleSoft Connect.
Stat opens the PeopleSoft Environment Connection Maintenance table.
2
Select the row for the environment in which you want to exclude objects.
3
Click PS Options. Then in the PS Options window, click on the Object Lock Exclusions tab.
4
Select the check box next to each object type you want to exclude from Object Security.
5
Press the Apply button.

Step 10 (Stat): Activate PS Locking

Define which service domains invoke PeopleSoft proprietary object security. By default, all the PeopleSoft environments associated with a service domain using Object Security participate. You can exclude an environment from Object Security by excluding all the object types it contains. This is discussed in the next section.

To activate PS Locking for service domains:
1
Select Maintenance | General | service domains.
Stat opens the service domain Maintenance table.
2
In the PS Locking column, select the check box for each service domain in which you want to use PeopleSoft Proprietary Object Security.
3
Have users logout/login to Stat for this service domain change to take effect.
4
Run lock sync jobs set up in step 11.

Step 11 (Stat): Set Up the Stat Central Agent

Up to this point, developers still cannot access objects in PeopleSoft. Object Security will take effect after the Stat Central Agent processes the PS Object Lock Sync jobs for the first time.

When the Stat Central Agent processes a PS Object Lock Sync job, it populates each Operator Security Group with the objects locked by that developer in Stat, the STAT_READ group with all of the objects defined in PeopleSoft, and the STAT_EXCLUD group with all of the objects of the excluded type.

For more information on defining Stat Central Agent jobs, see Chapter 6, Configuring the Stat Central Agent .

To define the PS Object Lock Sync jobs in Stat:
1
Select Maintenance | Stat Central Agent | Job Maintenance. Then in the Stat Central Agent Job Maintenance table, select a service domain in which you activated PS Locking in the Domain field (see Step 1).
2
Click New. Then in the Job Maintenance window, define a PS Object Lock Sync job for each environment in which you plan to use physical object locking.
3
Click the Schedule tab and specify the day(s) and time(s) you want the job to run.
You can schedule different Lock Sync jobs to run at different times and days. When finished, click OK.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen