1.5.40 enhancements

PATROL History Loader 1.5.40 includes the following features and enhancements:

History Propagator configuration in TrueSight console

You can now configure the History Propagator in a monitoring policy in the TrueSight console. For more details, see Configuring History Propagator using the TrueSight console. 

Security configuration in secure store

All security configuration is stored in the secure store and not in pconfig.

Debug output in log file

Debug output is stored in a log file instead of the PATROL Console system output window (SOW). For more details, see Troubleshooting.

Parameters changed from Gauge to Graph

The followings History Loader parameters have been changed from Gauge to Graphs to allow for better representation of the data:

• Number of Files Waiting for Loader
  See the following links for details:
  • Number of files Waiting for loader (FilesWaiting) - DB2
  • Number of files Waiting for loader (FilesWaiting) - Oracle Server
  • Number of files Waiting for loader (FilesWaiting) - Microsoft SQL Server
• Number of Loader Errors
  • Number of Loader Errors (LoaderErrors) - DB2
  • Number of Loader Errors (LoaderErrors) - Oracle Server
  • Number of Loader Errors (LoaderErrors) - Microsoft SQL Server

New History Propagator parameters

• Configuration status (ConfigurationStatus) - Boolean parameter that indicates if the History Propagator configuration status is ok.
• Time Since Last Transmission (TimeSinceLastTransmission) - The number of minutes that passed since the last successful propagation cycle.

Database credentials in PATROL menu command dialogs

In the PATROL Console, database credentials for all supported databases are now entered in the appropriate PATROL menu command dialog boxes, and not in the Customize menu item.