Chat now with support
Chat with Support

Foglight for PeopleSoft 5.6.11 - User and Reference Guide

Using Foglight for PeopleSoft
Exploring the PeopleSoft Dashboards Foglight for PeopleSoft Agents PS_AppMonitor Agent PS_AppServer Agent PS_DB2SQL Agent PS_MSSQL Agent PS_OracleSQL Agent PS_PPM Agent PS_SchedMonitor Agent PS_SchedServer Agent PS_Scheduler Agent Manual Agent Naming Deployment Scenario Procedures
Foglight for PeopleSoft Reference
Views
PS_AppServer Views PS_DB2SQL Views PS_MSSQL Views PS_OracleSQL Views PS_PPM Views PS_SchedServer Views PS_Scheduler Views
Data

Setting the PS_Scheduler Job and Process Collection Properties

To set the job and process collection properties:
1
Go to the Jobs/Prcs Collection set of properties.
2
Enter the desired value in the Max Rows Per Collection box.
The default is 20.
The maximum value (hard limit) for this parameter is 50. At any given collection cycle, no more than 50 rows of data are collected for the QueueJobs, QueuePrcs, RunPrcs, and ReportDistributionPrcs tables.
If the number of rows returned equals or exceeds the value entered for this parameter, then an event notification kicks off stating that the Maximum Rows limit was reached or exceeded. For the QueueJobs, QueuePrcs, RunPrcs, and ReportDistributionPrcs tables, the data is sorted depending on the status of the jobs/processes/ReportDistribution.
 
Table 1. Data Returned Prioritized by Status
Queue Jobs and Queue Processes
Report Distribution Processes
1. Error
1. Not Posted
2. Not Successful
2. Generated
3. Unable to Post
3. Processing
4. Warning
4. Posting
5. Blocked
5. Delete
6. Restarted
6. Scheduled/NA
7. Processing
7. Posted
8. Cancel
 
9. Cancelled
 
10. Initiated
 
11. Pending
 
12. Queued
 
13. Generated
 
14. Posting
 
15. Posted
 
16. Success
 
17. Resend
 
18. Hold
 
19. Delete
 
 
For example, based on the above priority list, if the maximum rows to be collected in the agent properties is entered as 25, and there are 10 jobs that have each (190 total) of the above statuses for any given collection time interval, the following jobs are collected and reported for the QueueJobs tables:
•
10 Error
•
10 Not Success
•
5 Unable to Post
If the total number of jobs during a collection interval is less than the value of the maximum rows to be collected that is entered in the agent property, all the jobs are collected for the QueueJobs table regardless of their status. The same collection criteria apply to the QueuePrcs, RunPrcs, and ReportDistributionPrcs tables.
3
Enter the desired value in the Max Days in Hold Status box.
For Jobs and Processes that have the status of Hold, the agent collects (for the QueueJobs and QueuePrcs tables) only those jobs and processes that have been on hold for less than the value (in days) entered in this box.
The default is seven days.
 
* 
IMPORTANT: Jobs and processes with statuses other than Hold (for example, Pending) that have changed status to “Hold” and are older than the age specified in the agent property are NOT collected, as the original Run Time is taken into account for computing the age of the jobs and processes.
4
Click Save.
5
Go to the Setting the PS_Scheduler Oracle Database Properties section.

Setting the PS_Scheduler Oracle Database Properties

To set the Oracle database properties:
1
Go to the Oracle DB set of properties.
2
Enter the path to the TNSNAMES.ORA file in the SQL*Net Configuration File box.
3
Enter the login name for database access in the Database Login Name box.
 
* 
IMPORTANT: This user should have select authority access to the following Oracle V$ and PeopleSoft tables and views:
- V$SESSION (Oracle) - System View
- PSLOCK - Table in PeopleSoft 7.x and 8.x·
- PSSTATUS - Table in PeopleSoft 8.x·
- PS_SERVERDEFN
- PSPRCSRQST
- PSPRCSQUE
- PSSERVERSTAT
- PSDBOWNER- PS_CDM_AUTH_U_VW
- PS_CDM_LIST
4
Enter the password for the login name in the Database Login Password box.
5
Enter the full path to the ORACLE_HOME in the Oracle Home box.
6
Click Save.
7
Go to the Setting the PS_Scheduler DB2 UDB Database Properties section.

Setting the PS_Scheduler DB2 UDB Database Properties

To set the DB2 UDB database properties:
1
Go to the DB2 UDB DB set of properties.
2
Enter the DB2 Instance name in the DB2 Instance box.
 
* 
NOTE: This field is case sensitive.
3
Enter the login name for database access in the Database Login Name box.
 
* 
NOTE: This user should be a member of the DB2 administration group. In addition, this user should have select authority access to the following PeopleSoft tables:
- PSLOCK
- PSSTATUS
- PS_SERVERDEFN
- PSPRCSRQST
- PSPRCSQUE
- PSSERVERSTAT
- PSDBOWNER
- PS_CDM_AUTH_U_VW
- PS_CDM_LIST
4
Enter the password for the login name in the Database Login Password box.
5
Enter full path to the DB2 UDB home in the DB2 UDB Home box
6
Click Save.
7
Go to the Setting the PS_Scheduler MSSQL Database Properties section.

Setting the PS_Scheduler MSSQL Database Properties

To set the MSSQL database properties:
1
Go to the MSSQL DB set of properties.
2
Enter the login name for database access in the Database Login Name box.
 
* 
NOTE: This user should have select authority access to the following SQL Server System and PeopleSoft tables:
- sysprocesses – SQL Server system table
- PSLOCK – Table in PeopleSoft 7.x and 8.x
- PSSTATUS – Table in PeopleSoft 8.x
- PS_SERVERDEFN
- PSPRCSRQST
- PSPRCSQUE
- PSSERVERSTAT
- PSDBOWNER
- PS_CDM_AUTH_U_VW
- PS_CDM_LIST
 
* 
NOTE: This user must have select authority to access the following Microsoft SQL Server 2000 system and PeopleSoft tables:
- sysprocesses
- PSLOCK
- PSSTATUS (PeopleTools 8.x)
 
* 
NOTE: The user must have the following Privileges for MSSQL.

To retrieve the SQL statement, the user requires the following privileges.
- Execute DBCC TRACEON (3604,3626)
- Execute DBCC INPUTBUFFER (spid)

To retrieve the BufferGets, DiskReads, RowsProcessed, the user requires the following privileges:
- Execute DBCC TRACEON (3604,4032)
- Execute BCC PSS (0,spid)

Privilege to execute the DBCC PSS command is not applicable for SQL Server 2005 because the DBCC PSS command does not work in this version.

For SQL Server 2005, instead of the privilege for executing DBCC PSS command, the user must have the select authority for the following system views:
- sys.dm_exec_requests
- sys.dm_exec_sql_text

To retrieve PSApplicationUser, PSDatabaseUser, PSDomainName, PSMachineName, PSOSUser, PSPercentCpu, PSPercentIO, PSProcessName, PSProcessPID, PSRawIOCount, PSSessionID, Status, the user requires privileges to perform the following:
- Select from table master..sysprocesses and master..sysdatabases
3
Enter the password for the login name in the Database Login Password box.
4
Enter the full path to the MS SQL Server home directory in the SQL Server Home box.
5
Click Save.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating