Basic Concepts
Introductory GFE Structure
GFE is a part of the Common AWIPS Visualization Environment (CAVE). GFE shares a common configuration cache and caveData with CAVE and AlertViz. GFE configuration is split between CAVE (graphics side) and the Environmental Data Exchange Server (EDEX).
EDEX
GFE requires several server processes in order to run properly, and files to configure those server processes. These processes and files are delivered by EDEX. EDEX runs in a clustered environment on multiple AWIPS servers. On a typical baseline system for a WFO, the EDEX cluster consists of the dv3, dv4, and dv5 servers. On a typical baseline system for a NCEP site (or a WFO with a NCEP configuration), the EDEX cluster consists of the dv6, dv7, and dv8 servers in addition to the dv3, dv4, and dv5 servers. On a typical baseline system for a Regional center, the EDEX cluster consists of the dv6 server in addition to the dv3, dv4, and dv5 servers. This environment allows all machines in the cluster to execute GFE processes simultaneously. In order for GFE to launch successfully for a site, the site must be active. An active site is defined as a site with an active GFE server process running on EDEX. EDEX automatically activates GFE for the site EDEX is running. Therefore, if EDEX is running at your site, your site should also be active for GFE. EDEX controls the GFE Server processes through the GFE Server configuration files in the Localization Perspective. Each time a change is made to a GFE Server configuration file, the GFE Server must be restarted. EDEX handles the majority of data retrieval from grid databases.
CAVE
CAVE provides integrated infrastructure for GFE and delivers several GFE-specific files. CAVE controls the display of GFE through GFE configuration files in the Localization Perspective. Every time you make a change to a GFE configuration file, GFE has to be restarted.