The CWMS 3.3 Client package comes with an upgrade to some of the individual modeling applications and most of the client applications that make up CWMS.  Many of these upgraded applications require user input during the conversion of models or configuration files to the newer version.  To smoothly manage the migration of your CWMS 3.2.3 implementation into CWMS 3.3, this Migration Tips page was prepared.  Please read this page carefully before you start the migration.

BACKUP YOUR WATERSHEDS! 

Watershed models brought into CWMS 3.3 will become incompatible with prior versions of CWMS. Before opening an existing watershed for the first time using the new CWMS CAVI and servers:

  • Zip up each copy of the watershed on your PC, as well as any master watersheds on your servers. 
  • Rename each zip file appropriately, so that you and/or your team members will know which archive(s) can be used should you need to revert to the previous CWMS version.

If you use Team Forecasting, coordinate with your team members to determine whether to update a master watershed or create a new copy of the master watershed for CWMS 3.3.  A "How To" article on backing up a watershed can be found here.

Updating Individual Models

If you open a CWMS 3.2.3 watershed in CWMS 3.3 without first updating the individual models, then prompts for each model will ask whether to update the data to the new version, or quit the update).  In all cases, once updated, the models will no longer be usable in CWMS 3.2.3 (i.e. there is no backward compatibility between model versions).  

Best practice is to make copies of the watershed and models, or create backup copies, then upgrade all the model using the latest versions of the individual HEC programs.

PC Installation

To avoid CWMS executables from being blocked by antivirus software, the portable CWMS software package should be not be installed or run from the user profile area (i.e. C:\Users\<userID\Desktop\CWMS-vX.Y.Z). 

Rather, the portable CWMS software package should be installed and run from a folder under the C Drive (e.g. C:\Programs\CAVI-vX.Y.Z or C:\Local_Software\HEC\CAVI-vX.Y.Z, etc.).

CWMS Login 

The CWMS login establishes connection to the CWMS host server for data access through:

  • Time Series Icons
  • CWMS-Vue CAVI Plugin
  • Extract/Post Editors
  • Data Validation Editor
  • Data Status Summary Report

In addition, login to the CWMS host server gives CAVI access to a Team Watershed and remote DSS files on that server.

During CWMS migration (and COOP exercises), it is expected that the server information stored in the watershed properties may not match the latest CWMS host server information.  Here are a few scenarios describing what the user should expect:

  1. When the user logs into the same server configured for the watershed, no additional login dialog should show up and user stays logged in.
  2. When the user initially logs into a different server than that configured for the watershed, another login dialog should appear with a drop-down list presenting the user with the following options:
    1. If the user switches to the watershed's server, the user will be logged out of the server initially logged into and then will be logged into the watershed's server.
    2. If the user picks the same server they had already logged into, the would maintain access to that server.
    3. If the user picks a different server than the one already logged into and different than the server specified in the watershed properties, the user will be logged out of the server initially logged into and then will be logged into the newly selected server.
    4. If the user cancels the login dialog, they would maintain access to the same server initially logged into.
    5. If the user picks "Local" from the login dialog, the user will be logged out of the server initially logged into. This is the equivalent to the Logoff menu item.

Regardless of the choices above, the server information stored in the watershed properties will remain unchanged unless manually updated in the Watershed Properties dialog.

Logging into a Different Server than the Watershed's Server

When logging into a server that is different than the watershed's server, the retrieval of CWMS data will work if time series records and DSS file location names match between the different servers. So, CWMS time series record data previously set up for the watershed will work with a different server connection as long as the CWMS time series data records are the same in both databases and the remote DSS files set up for the watershed are named the same and in the same locations on each server.  This includes the Extract and Post processes, Time Series Icons, Data Validation, and Data Status Summary. For example, if a remote gridded file is used in one of the Extract Groups for a specific server set up, but the log in uses a different server, the extract will still work if the gridded data is stored in the same location structure. Same is true for Oracle records.  If the extract records exist on the CWMS database that is logged into, the extract will still work. 

Restarting the CAVI

If it becomes necessary to restart the CAVI due to irresponsiveness, please use the HEC-RTSTaskList.exe (located where CWMS is installed within the CAVI folder) to ensure that all its associated processes are cleared before starting it back up.   See section denoted "CAVI" in "CWMS Client Software - CAVI and CWMSVue".

Avoiding Multiple Instances of HEC-RAS

When a user has an existing HEC-RAS standalone instance open and subsequently opens a CAVI watershed, the CAVI commandeers the HEC-RAS instance. This causes the existing project to close immediately (terminating any ongoing computations) and opens the watershed HEC-RAS project in its place. Recommend users make sure all instances of HEC-RAS are closed before opening a CAVI watershed.