ATD Processing Model (Phase 1)

This image is the Processing Model (Data Flow Diagram or "DFD") for the ATD DaaS example:

Right-click and "Open in New Tab" (Opera users) or "View Image" (Firefox) for larger view.  IE users can save this for a larger view.

DFD of Hotel DaaS Example

Phase 1 for ATD deals with hotel data.

Tan processes are scheduled process. Green process are development-only scripts (like "ATDClearData Process") or proceses run ad hoc ("ATDLoadClientHotel Map").

Several notes identify common code and resources used by all the processes: Connectors, Macros, Lookup Functions.

The data intake processes appear to the left of the MySQL data store. A single Data Integrator process, ATDHotelFilesToMySQL Process, controls the file handling "main loop". The ATD_HOTEL table is loaded with a map (ATDLoadHotel). The ATD_HOTEL_SERVICE table is loaded using a subprocess -- see a Bekwam tutorial on this -- called from ATDHotelFilesToMySQL.

ATDHotelFilesToMySQL will move data files to an archive folder if processing is successful. If not, files are moved to an error folder.

Data publishing processes appear to the right of the MySQL datastore. ATDAllHotelsXML and ATDStatesHotelslXML are maps called from processes ATDAllHotelsXML and ATDStatesHotelsXML, respectively. There is a process called ATDHotelsXMLPublish that will read the output files (XML documents) of the XML-generating processes and publish them to a web server using SFTP.

This post is replicated from http://my.opera.com/walkerca/blog/2010/12/12/atd-processing-model-phase-1.