• Supports OS versions Windows 2000 and Windows 2003 on the OVO management server
• Supports managed nodes running: Windows 2000 and Windows 2003
• Supports PeopleSoft 7.05, 7.5, 8.1 and 8.4
• Monitors, detects, and displays the status of PeopleSoft batch jobs as well as components such as the process scheduler
• Monitors log-files dynamically to keep track of any important events registered in the various, distributed error logs from PeopleSoft, Tuxedo, and any databases.
• Provides pre-configured automatic actions help to ensure minimum server down time
• Pre-defined reports identify the owners of batch jobs that are causing problems (such as high system load) and help to prevent performance bottlenecks
• Monitors the status of all the crucial components in the PeopleSoft environment, such as applications and application servers, database servers, and sub-systems such as Tuxedo

The problems are grouped into the following categories:

• "General Discovery Strategy and Prerequisites"
• "Discovery/Activation"
• "ITO Monitors and Commands"
• "MeasureWare Integration"
• "De-installation"

Discovery/Activation

Symptom:

If there are multiple PeopleSoft databases or Application server domains with identical names on a single system with multiple PeopleSoft installations, only one will be accepted by the discovery process. A message similar to the following will be printed when running the PS Discovery application:

ERROR: Duplicate PeopleSoft DB name hcdmo754 in different PS_HOMEs: c:\ps_tge and d:\TEST\psoft. Ignoring for D:\TEST\psoft.

Solution:

With this release of the SPI names of PeopleSoft elements must be unique on one system.

Symptom:

If a PeopleSoft Application server domain crashed or has been aborted ungraceful the SPI TMIB monitor may hang when accessing the Tuxedo TMIB. An indication is an OVO message appearing similar to:

Can’t start monitor script for object ’PSSPI-TMIB-Col-05min_1’. Script still running. (OpC30-610)

Solution:

Always shutdown domains properly. Try to re-boot or re-configure the domain. If this does not help you may need to re-boot the whole system.

Symptom:

SPI log file templates are still active even if the SPI has been turned off. Unexpected OVO messages may arrive.

Solution:

The COLLECTION state in the file psspi.cfg affects only monitor scripts and programs but not log file templates. Use the OVO utility opctemplate to disable and enable templates. See the PeopleSoft SPI manual for details (Templates and Monitors on MC/ServiceGuard Nodes).

Symptom:

If SPI templates have been distributed before the instrumentation has been deployed, OVO messages similar to the following may appear:

Logfile <‘perl -S psspi_appsv.pl‘> doesn’t exist. Treating as empty. (OpC30-108)

Solution:

Always make sure that the instrumentation is deployed before the templates.

Symptom:

If a PeopleSoft Application server domain is down, the previous values about all other domain parameters will be used, i.e. the graphs will show a non-zero number of server processes, even if the domain is down.

Solution:

Ignore the other graphs if the domain graph shows a zero value.

Symptom:

The de-installation of the SPI does not remove the created services representing the PeopleSoft environment.

Solution:

Remove the services manually in the console GUI.