The AsdexDatabase is a listener for PositionMessageList messages from the STDDS SMES data feed. Received messages are a list of PositionMessages which are batched and persisted to a PostgreSQL database at a configurable time interval. The database uses partitioned table to store data. New table partitions are created daily and tables older than a configurable time period will be dropped.
TfmTerminalFlightDatabase
Database project for logging all messages out of the TFMS Terminal Flight SWIM feed
TbfmDatabaseLogger
The TbfmDatabaseLoggeris a consumer of TBFM messages from the TBFM SWIM data feed. Received messages are batched and persisted to a PostgreSQL database at a configurable time interval (default is every 10 seconds). The database uses partitioned table to store data. New table partitions are created daily and tables older than a configurable time period will be dropped.
FuserDataCapture
The FuserDataCapture consumes Fuser produced messages. Received messages may be captured to an XML file, CSV file, or PostgreSQL database.
Messages captured in the database are batched and persisted at a configurable time interval (default is 5 seconds). The database uses partitioned tables to store data. New table partitions are created daily and tables older than a configurable time period will be dropped.
Fuser Processor Components
Component
Description
AsdexXMLProcessor
AsdexProcessor listens for Asdex messages on a JMS topic as provided by the STDDS SMES data feed. It expects to receive flight position messages. Each message is converted into filtered and flattened version with unique identifier and redistributed as PositionMessageList on new topics. The AsdexXMLProcessor is also responsible for retrieving the correct GUFI from the GUFI Service.
TfmFlightXmlProcessor
Processor that connects to the TFMS Flight SWIM data feed and filters / flattens the schema in addition to retrieving the correct GUFI from the GUFI Service.
TfmTerminalFlightProcessor
Processor that connects to the TFMS Terminal Flight SWIM data feed and filters / flattens the schema in addition to retrieving the correct GUFI from the GUFI Service.
TbfmXmlProcessor
TbfmXmlProcessor listens for TBFM messages on a JMS topic as provided by the TBFM SWIM feed. It expects to receive flight specific and position messages. TbfmXmlProcessor provides the option to capture messages before redistribution. The purpose of the TbfmXmlProcessor is to filter and flatten the schema, add additional information into each message, and retrieve the correct GUFI from the GUFI Service.
Other Fuser Service Components
Component
Description
Fuser
The Fuser component listens for incoming data from all of the external interface processor components. The Fuser transforms all data to a common schema, applies filtering, merges to a current flight state, and sends the fused data to STBO.
GufiService
The GUFI Service assigns and manages Globally Unique Flight Identifiers (GUFIs) for all Fuser components. The GUFI is the data element that is used for all flight matching by the Fuser, as there are several external flight data sources coming into the Fuser.
