Default Parameters for PepPrsTransTest

This tesr periodically checks the status of transactions on a configured Process Scheduler domain, and reports how many transactions are in which state presently. This can reveal the number of active transactions on the domain, based on which the current load on the domain can be determined. In addition, the test also warns administrators of transactional errors that may cause transactions to abort, thus enabling administrators to take pre-emptive steps in this regard.

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

• 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.