Sentinel interacts with the PeopleSoft database using an ODBC or JDBC connection. It can simultaneously support multiple PeopleSoft Pillars (HR, FS, CS) and PeopleTools versions.
The application does not create or modify tables within a PeopleSoft environment. Transaction history and audit reports are stored in the Sentinel database.
Security changes made in Sentinel and PeopleSoft are automatically synced after they occur. To differentiate between PeopleSoft and Sentinel updates, each update from Sentinel is prefixed by SNT_(User ID) in the PeopleSoft database.
Account Requirements
A databaseaccount is required for proper functionality, and installation cannot be completed without the database account credentials.
A separate database account is required for each PeopleSoft Environment.
*The client is solely responsible for creating and maintaining their account credentials.
Add A Database Connection
Navigate to Settings - Databases.
Click 'Add,' located at the top right.
Input the following database account credentials and connection information:
Click 'Test Connection.'
If successful, click 'Create.'
If an error occurs, verify there is connectivity between the Sentinel server and the PeopleSoft database server.
After a new database is added to Sentinel, the initial build process must be manually run for the database to be accessible. *The process runs automatically after the initial build.
Database Info is used to configure the Environment Name, PeopleSoft Shortcut Link, and Write Access Settings.
Environment Name - The name of the environment as it is displayed to users.
PeopleSoft Environment URL - Creates a shortcut link to the PeopleSoft application.
Lock Environment - Disables all Sentinel updates & makes environment 'Read-Only.'
Deactivate - Stops the database connection and can be removed from Sentinel.
Database Settings are used to configure the Sentinel functions allowed in each PeopleSoft environment.
Environment Settings:
Production Environment - Used to identify Production environments within Sentinel.
Read Only - Disables Sentinel updates to Roles & Permission Lists.
Allow Data Sync - Must be enabled to use Sentinel migration features.
Data Scrubbing - Allows data in tables to be updated. *Not permitted in production.
Direct Access - Allows User & Role permissions to be updated via the navigation menu.
Report Statistics - Audit and Security report statistic calculations can impact performance. Recommended for Production only.
Track Role Changes - Track user role changes. Not recommended for environments that are frequently refreshed.
Database Connection is used to maintain the database account credentials.
*The client is solely responsible for creating and maintaining their account credentials.
The Build Process imports new PeopleSoft objects or customizations. This runs on a nightly basis or can be initiated manually.
After a new database is added to Sentinel, the initial build process must be manually run. *The process runs automatically after the initial build.
Run The Build Process [Manually]:
Navigate to Settings - Databases.
Select an Environment.
Under the 'Build' tab, complete each step in the given order.
The Database Log captures the details of the nightly build process, changes to database settings, and connection updates.
Types of Events:
No Connection - A connection to the database could not be established.
Connection Lost - The database can no longer be reached.
Insufficient Table Access - The database account being used by Sentinel does not have sufficient access. Verify Database Account Requirements.
Insufficient Write Access - The database account being used by Sentinel does not have enough permission to perform security updates.
Connected - Database connection is active. All sync jobs were complete.
Database Refresh - The current database has been refreshed with data from another database.
Deactivated - The database connection has been manually terminated. The database will not be accessible to users.
The client is solely responsible for creating and maintaining their account credentials:
To ensure the security of these credentials and comply with organizational policies, it is recommended that they be changed regularly. Proper precautions should always be taken to maintain secrecy and protection.
