The CWMS CAVI, CWMSVue, and a variety of other programs included in the CWMS Client installation package have been updated to include bug fixes and/or new features.  Please review the various notes in this section to determine if you need to address any configuration issues or make any other changes to your watersheds.

Login/Accounts 

  • In CWMS 3.3.0, the CWMS login has changed and prior connections from CWMS 3.2.3 are no longer in the history. There are three main server connections directly supported in the CWMS Server Setup
    • CWMS HTTPS Login Server
      • Connection to CWMS T7 database
      • Requires Host URL
    • CWMS RMI Login Server
      • Connection to CWMS T7 database
      • Requires Host URL and Port
    • CWMS Data API (formerly CWMS Radar)
      • Direct connection support to the CWMS Data API database
      • Requires Host URL and Office

The structure of CWMS servers in the CAVI has been modified and requires re-creation of your connections in CWMS 3.3.0.

Connections to the database and CAVI have been modified in CWMS 3.3.0. A database updated to CWMS 3.3.0 supported schema will not be able to be connect to a CWMS 3.2.3.1 application.

Added checking server status to the server login page

Updated interface for adding Server location.

Added direct connection from CWMS RADAR

Scripting 

The structure of CWMS has been modified immensely; therefore, some scripts will require modifications to operate accordingly. Please see script transition page for more information and suggested workflow process.

Team Modeling 

If you update the Master Watershed location, this will force all users to update. So please plan ahead before updating a master watershed.

In all versions, check the storage on /var/tmp if experiencing problems uploading to master watersheds hosted on CWMS servers.    During initial upload the watershed files are staged in a scratch folder under /var/tmp, which has only 10G total space in standard T7 configuration.    The files are cleared out of /var/tmp before the synchronization process finishes, but the upload will fail if available space runs out while staging.  Avoid performing simultaneous uploads among users sharing the server, especially of large watersheds.     

If you desire to use the CAVI dashboard with a team modeling watershed, you will need to delete some files on the master watershed to ensure the dashboard can be used amongst several computers (issue HEC is looking into and is denoted in the Dashboard area). Please see dashboard section for more information.

 CAVI

When the CAVI freezes or becomes unresponsive and the user wishes to close CWMS, make sure to use the HEC-RTSTaskList.exe that is found within the CAVI folder of CWMS.  This program ensures that all programs associated with CWMS are closed.  Using Window's Task Manager does not always catch all the programs, and "zombie" processes can lead to errors such as "HMS: ERROR 10013: Another instance of HEC-HMS is currently using project…”.   Similar issues might arise if the user closes the console window of CAVI.

Multiple CAVI instances are supported in this version of CWMS; however, both instance write to the same log location, this can cause issues if you desire to view the log files once the watershed is closed.

There is a CAVI.config modification to create a unique log per each CAVI instance (this will cause for a large amount of log files, so you might need to go to log location to cleanup periodically)
Add vmparam -DLogFileHasPid=true to the CAVI.config file.