Agents Administration - Tests
 

Default Parameters for PepPrsClientTest

This test automatically discovers the clients who are currently connected to the Scheduler, reports the number of active sessions for each client, and also reveals the number of transactions of every client that have been committed and aborted. In the process, the test pinpoints those clients who have launched too many sessions on the Scheduler; in the event that the Scheduler chokes, such clients could be considered guilty of overloading it.

This page depicts the default parameters that need to be configured for the PepPrsClientTest.

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • To collect metrics from a PeopleSoft PeopleSoft Process Scheduler, this test runs PeopleSoft Server Administration (PSADMIN) commands on the target server. The first step towards this is to launch the psadmin.exe. To enable the test to run the psadmin.exe, you need to configure the test with the full path to the directory in which the psadmin.exe resides. Therefore, in the PSADMIN HOME text box, specify the location of the psadmin.exe. Typically, this will be the install directory of the PeopleSoft application server. For instance, on Windows, your specification can be C:\ps\appsrv and on Unix, your specification can be: opt/ps/appsrv.

  • An application server DOMAIN is the collection of server processes, supporting processes, and resource managers that enable connections to the database. The Process Scheduler is also a collection of server processes that run in a domain. To monitor a Process Scheduler therefore, you need to configure the eG agent with the exact name of the domain in which the Process Scheduler is running. Specify this domain name in the DOMAIN text box.

  • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz” and $port will be changed to “80” when configuring a test.