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

PeopleSoft Object Mover Instruction Update Utility

When you upgrade Stat or when PeopleSoft has a major PeopleTools release, you may need to run the PeopleSoft Object Mover Instruction Update Utility. This utility tells Stat how to migrate and recover different versions of PeopleSoft proprietary object types. The utility works by executing a set of commands contained in a file named psominst.psr located in your Stat directory.

You can also use this utility to fix problems you may experience when migrating archive sets. If Stat displays error messages that read “Load SQL definitions ( ) failed to open cursor” or “Load SQL definitions did not find any definitions for object type:__PeopleSoft version __,” this may be because you need to update the Object Mover instructions.

Access to this utility should be restricted to system administrators.

Select Maintenance | General | Update PS Object Mover Instructions.
Click Update.

Stat Security

Stat Security Layers

Stat comes equipped with a powerful, two-layered security system. At the first layer, strict login protocols control access to the Stat Repository, and at the second layer, a set of internal security measures controls access to sensitive areas within the application database.

Internal security is based on service domains and user classes. User classes are logical groupings of access rights which are assigned to users according to their functional needs. These rights can include everything from working within different service domains to adding and editing activity codes. User classes effectively maintain security within Stat by limiting users’ access to only the data and functions that pertain to them.

Login Security

Whenever a user attempts to login to Stat, two security checks, or “passes,” are made against the Stat Repository before the user’s login ID and password are validated. In this way, a total of three validations are performed before a user is granted access to the system. This process is as follows:

If the ID is valid, the appropriate security is put in place and Stat is loaded with all the internal security measures defined for the user in place. The user never actually logs into the Stat Repository using his or her login ID. First the STATLOGIN ID is used, then the ID from the Stat_Login table. Stat user IDs are used to identify the functions that users can and cannot perform once they are logged in.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating