CDA

Our Internal Sites on District T7s currently have their own private instance of the CWMS Data API connected to your local Oracle database. 


Some key things about this:

1. Control: You have FULL control over the version you use, when this is online/offline, and all the data is present without filtering.
2. Maintenance: You are responsible for maintaining the Tomcat password CDA uses to connect. Other maintenance like STIG checks are handled by G6.
   1. Updates are done by you, this is outlined on the CDA wiki: https://github.com/USACE/cwms-data-api/wiki/Installing-into-Tomcat#setting-up-a-script-to-update-cda-to-the-latest
   2. You can downgrade and upgrade CDA using the control  directory and subsequent scripts
   3. For Issues with the WEB (Apache/Tomcat) of your T7 you can submit an Incident Ticket here:
      https://usace.servicenowcloud.mil/sp?id=sc_cat_item&sys_id=5c747e7e51ac1550339aa0b1d0133b8c
3. Usage: Being this is a private instance, only the users you provide with the link will have access to this.
   1. Authentication: This is different from the National due to the T7 not having keycloak setup. It is primarily done with a CWMSLogin jsp  app. 
   2. Port Forwarding: You can have a reverse proxy established through Apache
      1. This provides you with
         1. No automated CAC prompt for data fetches
         2. Shared COOKIE between Tomcat and Apache (useful for form inputs)
         3. Easy to remember URL vs having to also remember the port

Useful Links:

CDA Instance

Tomcat: (uses port 8243 normally)

https://wm.swt.ds.usace.army.mil:8243/swt-data 

Apache (reverse proxy, requires setup)

https://wm.swt.ds.usace.army.mil/swt-data 

Tomcat Web App Manager:

https://wm.swt.ds.usace.army.mil:8243/manager/html