Chatta subito con l'assistenza
Chat con il supporto

Stat 7.0 - 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 Enabling Web Client to perform PeopleSoft migrations 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: Oracle Agent: Stat.conf and log4j2.xml configuration Appendix: Custom Report Files

PS Object Lock Sync

This job makes sure that the PeopleSoft Object Security groups contain the correct objects. They might not contain the correct objects if, for example, someone has modified the group definitions in PeopleSoft. The job has two steps:

•
Sync objects locked in Stat by Stat developers with the Object Security Groups for the PeopleSoft developers in PeopleSoft
•
Sync all objects in PeopleSoft with the Stat_Read and Stat_Exclud Groups in Object Security

There are two key differences between the physical locking that occurs when users lock objects in a CSR and the PS Object Lock Sync job:

•
When a user saves a CSR after locking an object associated with it, Stat Central Agent automatically processes this object lock. It inserts a row in the Assigned Developer’s Object Security Group in PeopleSoft for the locked object. This is not done using the PS Object Lock Sync job. Stat Central Agent does it automatically in the background. Once Stat Central Agent finishes this process, the developer can open and modify this object in PeopleSoft.
•
You can schedule the PS Object Lock Sync job to run for the selected PeopleSoft environment any time you wish. It is recommend once a day at night.

PS Database parameter: Click the arrow button and select the PeopleSoft environment that this job is run for.

Purge Agent Event Tables

This job purges entries from the Stat Central Agent event tables. It is recommended that you keep at least 7 to 14 days worth of history for troubleshooting purposes.

Retention Days parameter: Enter the number of days for which you want to retain Stat Central Agent event history.

* 
NOTE: For Oracle Applications users, this job also purges all non-patch related entries.

Purge Audit Tables

Purges the STAT_AUDIT table. Unlike other purge jobs, this job only needs to be set up in one service domain as the data on the table is not service domain-specific. This job is best defined as a “Run Once” job that needs to be coordinated with Auditor visits.

Retention Days parameter: Enter the number of days for which you want to retain data regarding audit ables. Can be set from 1 to 999 days.

Purge Deleted Archive Sets

This job purges all data regarding deleted archive sets. It is service domain independent and needs to be set up only once to purge deleted archive set data across all service domains.

Retention Days parameter: Enter the number of days for which you want to retain data regarding deleted archive sets.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione