ECHO Technical Interchange Meeting 2013 Timothy Goff 1 Raytheon EED Program | ECHO Technical Interchange 2013

Support multi format metadata for SMAP. Leverage ECHO REST API More efficient – less lag time between ECS updates and ECHO updates. Simplify BMGT system Recent changes to ECS have rendered some of BMGT’s complexity unnecessary. Sybase to Postgresql transition Simplify Database interaction and avoid transitioning current highly complex stored procs to postgresql 2 Raytheon EED Program | ECHO Technical Interchange 2013

REST API ISO Support for SMAP Exports no longer packaged – more responsive synchronous upload Short form verifications handled locally, rather than remotely. DAAC Hosted Browse (See next slide) 3 Raytheon EED Program | ECHO Technical Interchange 2013

Design Considerations: Location/technology Datapool vs new location FTP vs HTTP File format JPG vs HDF Other browse formats Availability ECHO has different availability requirements than DAAC Hidden granules (e.g. AST_L1A) Browse not on public datapool Discontinue export of browse metadata Send URLs only (as OnlineResourceUrl) Simplifies BMGT processing of events 4 Raytheon EED Program | ECHO Technical Interchange 2013

Dispatcher server polls frequently to pick up export queue entries. Entries are added by BMGT Drivers (one for each export type). Dispatcher requests metadata from Generator, sends it to Exporter where it is HTTP PUT/DELETEd to ECHO. Response is processed by Response Handler BMGT keeps a pool of HTTPS connections to ECHO which are reused, reducing overhead. 5 Raytheon EED Program | ECHO Technical Interchange 2013

Updated GUI provides monitoring capabilities Also, interface to initiate manual/verification export. Plan to maintain similar command line interface for Manual/Verification as well. Can be called via cron. Dispatcher and Event (Automatic) Driver run continuously as daemons with little user interaction. Polling can be suspended/resumed via GUI. 6 Raytheon EED Program | ECHO Technical Interchange 2013

Must cut-over to new BMGT upon 8.2 install. 8.1 BMGT will not work with 8.2/postgresql. All data exported in 8.1 BMGT will be maintained after cut-over. No need to re export. Need to coordinate with ECHO to modify provider to REST/multiformat during 8.2 installation downtime. 8.1 BMGT will need to be quiesced before 8.2 install. Will need to record end of 8.1 export so that 8.2 BMGT knows where to start looking for new events when it comes up. Will develop plan to transition existing granules to DAAC Hosted Browse. 7 Raytheon EED Program | ECHO Technical Interchange 2013