Office of Science & Technology Systems Engineering Center February 3, 2011

1. AWIPS IILocal Application Migration TrainingSession #1 Office of Science & Technology Systems Engineering Center February 3, 2011

2. Overview • AWIPS II Infrastructure • AWIPS II Status • Stability • Performance • Local Application Metrics • Trac • Subversion • Resources • Moving Forward

3. AWIPS II Infrastructure

4. AWIPS IIContents • CAVE (Common AWIPS Visualization Environment) • Common framework for many AWIPS applications • CAVE PERSPECTIVES: N-AWIPS, D2D, GFE, Hydro Apps, etc. • CAVE DIALOGS: Volume Browser, WarnGen • STANDALONE, LAUNCHED VIA CAVE: SSHP, RiverMon • GUIs resemble AWIPS I versions • …but with new features such as Localization Management & Data Browsing • Can be extended via RCP plug-ins • Installed on workstations • EDEX (Environmental Data EXchange) • Data ingest, Data storage, Data dissemination • Installed on servers • AlertVIZ (Alert Visualization) • Independent, centralized tool for displaying AWIPS II alerts/status

5. <<Java>> HDF5DataStore <<Java>> DataLayer <<abstract>> BaseDao AWIPS II SOA Architecture Client/Presentation Services JMX CAVE External Programs Mission Services Layer ProductSrv NotifySrv Ingest Services Hydro Models AdapterSrv TextDBSrv GFE Services UtilitySrv LAPS PurgeSrv Hydro Services Security Services /Demilitarized Zone (DMZ) Enterprise Service Bus - Communication FORTRAN/C/C++ Command Line Programs Data Access Layer Hibernate HDF5 API Synchronous Interface Localization Store Platform Layer PostgreSQL HDF5 Data Persistence Store Metadata Index Spatial Index

6. AWIPS II Architecture AWIPS II Reference Architecture Enterprise Service Bus (ESB) <<Visualization Framework >> CAVE <<Service Framework >> EDEX Core Generic Services Headless CAVE Plug In Pattern VIZ PlugIns Meta Data VIZ Scripts Data Core Libraries Data Types Custom Displays Libraries Libraries Scripts Scripts

7. AWIPS II Status

8. AWIPS IIStatus • DR Count continues to fall • 657 Priority 1-3 DRs (as of 1/31/11) • Raytheon is closing ~100/week • System is more stable • FIT restarts much less common • Performance is improving • 2/3 of ingest metrics pass • 1/3 of CAVE metrics pass • ADAM full deployment starts 2/7/11 • r1g1-7 baseline • Virtual Lab connectivity • No direct connection from ADAM to Wiki, Subversion yet • Sneakernet until end of February

9. AWIPS IILocal Applications • FBSO (Fix Before System OT&E) • All FBSO local apps have been migrated • FBFO (Fix Before Field OT&E) • 547 open migration tickets (as of 1/28/11) • Complete by 5/31/11 • Deployment • 919 open migration tickets (as of 1/28/11) • Complete by 9/30/11

10. Trac

11. AWIPS-IITrac • System used for Local App Migration tickets • Two types of Local App tickets • Migration tickets for actual local app migration • Implementation tickets for each WFO registered • Full ticket lifecycle • Assigned->Accepted->In Progress->Testing->Closed • Canceled (duplicate, invalid) • Standard SQL queries via pulldown menus • https://collaborate.nws.noaa.gov/trac/am_OTE/report • Click on “My Tickets” report • or…click on “Custom Query” link in upper right

12. AWIPS IIMigration Tickets

13. Trac Demo

14. Subversion

15. AWIPS-IISubversion • Version control system for local apps • Open source • Raytheon using during AWIPS II development • LAD/STR has a limited life • Subversion is replacing the LAD/STR • Subversion has many advantages • Links • https://collaborate.nws.noaa.gov/trac/asdt/wiki/AiiHbDevEnvUseSu • https://collaborate.nws.noaa.gov/trac/ncladt/wiki/RepoLayout • Subversion demo in session #2 (next week)

16. AWIPS-IISubversion Steps for LAM • Download AWIPS I version of app from LAD/STR • http://www.mdl.nws.noaa.gov/~applications/LAD/ • http://www.mdl.nws.noaa.gov/~applications/STR/ • Commit AWIPS I version to Subversion • Useful for comparisons between AWIPS I & II migrated apps • Change status from “accepted” to “in progress” for Trac ticket • Migrate the local application • Periodically commit local application to Subversion branch • Update/modify/create local app documentation • Create/update test instructions

17. AWIPS-IISubversion Steps for LAM • Commit new version of local app to Subversion trunk • Change status from “in progress” to “testing” • Unit test of migrated local application • Perform a code walkthrough • Add to comment field in Trac as appropriate • Change status from “testing” to “closed” • See Kells’ “Local Application Migration Steps” document for more details

18. Resources

19. AWIPS II Migration Resources NCLADT https://collaborate.nws.noaa.gov/trac/ncladt High level migration info https://collaborate.nws.noaa.gov/trac/ncladt/wiki/HowToLocalAppMigration Training i.e. this (and future) slide packages AWIPS Tech Infusion site (currently being freshened up) View completed local apps in svn Compare AWIPS I version to migrated version ASDT Lead: james.calkins@noaa.gov awips2dev mailing list NWSChat(?) 19 19

20. Moving Forward

21. AWIPS II MigrationWhat can you do? • AWIPS II • Familiarize yourself with AWIPS II on ADAM • Problems? The NCF supports ADAM • Review resources • Use collaboration avenues (wikis, listservers, etc.) • Local application migration • Focus on FBFO apps • Look at completed apps for examples/tips • Get help from the ASDT

22. Coming Up… • Session #2…and beyond… • Subversion demo • Hands-on demo of AWIPS II behind the scenes • Review of an already-migrated local application • Q&A • Suggestion for future sessions? Let us know • ashley.kells@noaa.gov; james.calkins@noaa.gov