ReadMe For Hi-Track Monitor Release V4.4

Device Support Changes
   o  New Brocade device types may be defined in an XML file
   o  HDS Storage Units AMS1200, AMS600, AMS400 will now be reported as 
   AMS2500, AMS2300, AMS2100.  
   
   
Other Changes
   o  Hi-Track Monitor is now supported on the Microsoft Windows Vista and 2008 
   Server Operating Systems, and on Red Hat Linux on x86-64 systems.
   o  Java 6 is now used, instead of Java 5.
   o  The Windows Installer now includes a Pre-Install Command (batch) file
   (CheckSpecial.cmd) that checks for special characters in the Username and 
   Temp directories and allows the user to specify a different Temp directory.
   o  Proxy Configuration for HTTPs and FTP(s) Transports may now be entered 
   and changed from the Transport page, instead of in the User Management page.
   o  Devices that do not have a Hi-Track Site-ID. will not be reported
   o  Sorting the Summary page by Site-ID. is now supported.
   o  The InstallEdit script (on Linux installations) is required in fewer cases.
   o  The 'Last Communication' timestamp on HDS 9200, 9500 AMS, and WMS devices 
   will now show the time of the last successful poll, rather than the time of 
   any communication.
   o  The number of emails generated within a defined time period will now be 
   limited. Additional emails generated within the time period will be 
   discarded.  The current defined limit is 20 mail messages within any 30
   minute period.
   o  The default device poll time (used to calculate multi-thread requirements)
   is changed from 10 seconds to 2 seconds (2000 milliSeconds).
      
Corrections
   o  During the Import function, the DataStore (DFFILE.STORE) will now be 
   deleted and re-created, rather than emptied.
   o  HDS 9200 and 9500 units will hold the DataStore lock for a longer period
   during device entry. 
   o  Run-Time exceptions in device polling and reporting now affect only one 
   device.  That device may be marked 'Not Monitored'.
   o  The Linux version of the 'rundfmon' script has been modified to handle 
   the import and export functions correctly.
   o  The FTP Transport should always create a Transport History entry when the
   connection attempt fails.

   