From e85e1b75c31beb982a8ca7e0e8e22b79b87483f8 Mon Sep 17 00:00:00 2001
From: srcarter3 <srcarter3@users.noreply.github.com>
Date: Mon, 22 Jun 2020 22:19:47 +0000
Subject: [PATCH] deploy: a575ef29406c5b5e99a35d6e7b34a07acbfd422f

---
 install/install-cave/index.html |  9 ++++++++-
 install/install-edex/index.html | 23 +++++++++++++++--------
 search/search_index.json        | 22 ++++++++++++++++------
 3 files changed, 39 insertions(+), 15 deletions(-)

diff --git a/install/install-cave/index.html b/install/install-cave/index.html
index 1df9c91166..ecec4df32f 100644
--- a/install/install-cave/index.html
+++ b/install/install-cave/index.html
@@ -218,6 +218,8 @@
     
     <input class="md-toggle md-nav__toggle" data-md-toggle="toc" type="checkbox" id="toc">
     
+      
+    
     
       <label class="md-nav__link md-nav__link--active" for="toc">
         Install CAVE
@@ -231,6 +233,8 @@
 <nav class="md-nav md-nav--secondary">
   
   
+    
+  
   
     <label class="md-nav__title" for="toc">Table of contents</label>
     <ul class="md-nav__list" data-md-scrollfix>
@@ -1032,6 +1036,8 @@
 <nav class="md-nav md-nav--secondary">
   
   
+    
+  
   
     <label class="md-nav__title" for="toc">Table of contents</label>
     <ul class="md-nav__list" data-md-scrollfix>
@@ -1095,7 +1101,8 @@
                   <a href="https://github.com/Unidata/awips2/edit/unidata_18.1.1/docs/install/install-cave.md" title="Edit this page" class="md-icon md-content__icon">edit</a>
                 
                 
-                <h2 id="download-and-install-cave">Download and Install CAVE<a class="headerlink" href="#download-and-install-cave" title="Permanent link"></a></h2>
+                <h1 id="install-cave">Install CAVE<a class="headerlink" href="#install-cave" title="Permanent link"></a></h1>
+<h2 id="download-and-install-cave">Download and Install CAVE<a class="headerlink" href="#download-and-install-cave" title="Permanent link"></a></h2>
 <blockquote>
 <p><a href="https://www.unidata.ucar.edu/blogs/news/category/AWIPS">Release 18.1.1-7, March 25, 2019</a></p>
 </blockquote>
diff --git a/install/install-edex/index.html b/install/install-edex/index.html
index c45cfe37a3..c9f54f6683 100644
--- a/install/install-edex/index.html
+++ b/install/install-edex/index.html
@@ -230,6 +230,8 @@
     
     <input class="md-toggle md-nav__toggle" data-md-toggle="toc" type="checkbox" id="toc">
     
+      
+    
     
       <label class="md-nav__link md-nav__link--active" for="toc">
         Install EDEX
@@ -243,6 +245,8 @@
 <nav class="md-nav md-nav--secondary">
   
   
+    
+  
   
     <label class="md-nav__title" for="toc">Table of contents</label>
     <ul class="md-nav__list" data-md-scrollfix>
@@ -1113,6 +1117,8 @@
 <nav class="md-nav md-nav--secondary">
   
   
+    
+  
   
     <label class="md-nav__title" for="toc">Table of contents</label>
     <ul class="md-nav__list" data-md-scrollfix>
@@ -1257,7 +1263,8 @@
                   <a href="https://github.com/Unidata/awips2/edit/unidata_18.1.1/docs/install/install-edex.md" title="Edit this page" class="md-icon md-content__icon">edit</a>
                 
                 
-                <h2 id="download-and-install-edex">Download and Install EDEX<a class="headerlink" href="#download-and-install-edex" title="Permanent link"></a></h2>
+                <h1 id="install-edex">Install EDEX<a class="headerlink" href="#install-edex" title="Permanent link"></a></h1>
+<h2 id="download-and-install-edex">Download and Install EDEX<a class="headerlink" href="#download-and-install-edex" title="Permanent link"></a></h2>
 <blockquote>
 <p><a href="https://www.unidata.ucar.edu/blogs/news/category/AWIPS">Release 18.1.1-7, March 25, 2019</a></p>
 </blockquote>
@@ -1312,7 +1319,7 @@
 </blockquote>
 <h3 id="3-edex-setup">3. EDEX Setup<a class="headerlink" href="#3-edex-setup" title="Permanent link"></a></h3>
 <blockquote>
-<p>The command <code>edex setup</code> will try to determine your fully-qualified domain name and set it in <code>/awips2/edex/bin/setup.env</code>. EDEX Server Administrators should double-check that the addresses and names defined in setup.env are resolvable from both inside and outside the server, and make appropriate edits to <code>/etc/hosts</code> if necessary.  </p>
+<p>The command <code>edex setup</code> will try to determine your fully-qualified domain name and set it in <code>/awips2/edex/bin/setup.env</code>. EDEX Server Administrators should double-check that the addresses and names defined in setup.env are resolvable from both inside and outside the server, and make appropriate edits to <code>/etc/hosts</code> if necessary.</p>
 <p>For example, in the XSEDE Jetstream cloud, the fully-qualified domain name defined in <code>/awips2/edex/bin/setup.env</code></p>
 <pre><code>  export EXT_ADDR=js-196-132.jetstream-cloud.org
   export DB_ADDR=localhost
@@ -1397,7 +1404,7 @@ Failed to restart iptables.service: Unit iptables.service failed to load: No suc
   service qpidd start
   service edex_camel start
 </code></pre>
-<p>The fifth service, <strong>edex_ldm</strong>, does <strong>not run at boot</strong> to prevent filling up disk space if EDEX is not running. </p>
+<p>The fifth service, <strong>edex_ldm</strong>, does <strong>not run at boot</strong> to prevent filling up disk space if EDEX is not running.</p>
 <pre><code>  ldmadmin start
 </code></pre>
 <p>To start <em>all services except the LDM</em> (good for troubleshooting):</p>
@@ -1434,9 +1441,9 @@ SELINUXTYPE=targeted
 </div>
 <hr />
 <h3 id="ssd-mount">SSD Mount<a class="headerlink" href="#ssd-mount" title="Permanent link"></a></h3>
-<p>Though a Solid State Drive is not required, it is <em>strongly encouraged</em> in order to handle the amount of disk IO for real-time IDD feeds.  </p>
+<p>Though a Solid State Drive is not required, it is <em>strongly encouraged</em> in order to handle the amount of disk IO for real-time IDD feeds.</p>
 <p>The simplest configuration would be to mount an 500GB+ SSD to <strong>/awips2</strong> to contain both the installed software (approx. 20GB) and the real-time data (approx. 150GB per day).</p>
-<p>The default <a href="">purge rules</a> are configured such that <strong>/awips2</strong> does not exceed 450GB. <strong>/awips2/data_store</strong> is scoured every hour and should not exceed 50GB. </p>
+<p>The default <a href="">purge rules</a> are configured such that <strong>/awips2</strong> does not exceed 450GB. <strong>/awips2/data_store</strong> is scoured every hour and should not exceed 50GB.</p>
 <p>If you want to increase EDEX data retention you should mount a large disk to <strong>/awips2/edex/data/hdf5</strong> since this will be where the archived processed data exists, and any case studies created.</p>
 <pre><code>    Filesystem      Size  Used Avail Use% Mounted on
     /dev/sda1        30G  2.5G   26G   9% /
@@ -1479,13 +1486,13 @@ NIMAGE  ^(sat[^/]*)/ch[0-9]/([^/]*)/([^/]*)/([^ ]*) ([^/]*)/([^/]*)/([^/]*)/ (T[
 <hr />
 <h3 id="directories-to-know">Directories to Know<a class="headerlink" href="#directories-to-know" title="Permanent link"></a></h3>
 <ul>
-<li><code>/awips2</code> - Contains all of the installed AWIPS software. </li>
+<li><code>/awips2</code> - Contains all of the installed AWIPS software.</li>
 <li><code>/awips2/edex/logs</code> - EDEX logs.</li>
 <li><code>/awips2/httpd_pypies/var/log/httpd</code> - httpd-pypies logs.</li>
 <li><code>/awips2/database/data/pg_log</code> - PostgreSQL logs.</li>
 <li><code>/awips2/qpid/log</code> - Qpid logs.</li>
-<li><code>/awips2/edex/data/hdf5</code> - HDF5 data store. </li>
-<li><code>/awips2/edex/data/utility</code> - Localization store and configuration files. </li>
+<li><code>/awips2/edex/data/hdf5</code> - HDF5 data store.</li>
+<li><code>/awips2/edex/data/utility</code> - Localization store and configuration files.</li>
 <li><code>/awips2/ldm/etc</code> - Location of <strong>ldmd.conf</strong> and <strong>pqact.conf</strong></li>
 <li><code>/awips2/ldm/logs</code> - LDM logs.</li>
 <li><code>/awips2/data_store</code> - Raw data store.</li>
diff --git a/search/search_index.json b/search/search_index.json
index 27de07dd45..a133266a79 100644
--- a/search/search_index.json
+++ b/search/search_index.json
@@ -82,7 +82,12 @@
         },
         {
             "location": "/install/install-cave/",
-            "text": "Download and Install CAVE\n\uf0c1\n\n\n\n\nRelease 18.1.1-7, March 25, 2019\n\n\n\n\nLinux\n\uf0c1\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nawips_install.sh --cave \n  \n       \nFor CentOS/Red Hat 6 and 7. Installs to /awips2/cave and writes files to ~/caveData.\n \nchmod 755 awips_install.sh\nsudo ./awips_install.sh --cave\nRun CAVE from the Linux Desktop menu Applications > Internet > AWIPS CAVE, or from the command line as simply \ncave\n.\n \nSystem Requirements\nx86_64 CentOS/RHEL 6 or 7\nOpenGL 2.0 capable device\n4GB RAM\nLatest NVIDIA driver\napprox. 2GB disk space for data caching (~/caveData)\nYou can reset CAVE at any time by removing the \n~/caveData\n directory (on macOS \n~/Library/caveData\n) and reconnecting to an EDEX server. \n\n\n\n\n\n\n\n\nmacOS\n\uf0c1\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n    Download and install both\nawips-cave.dmg \nawips-python.pkg \n \nSupported Graphics Devices for macOS\nIntel HD Graphics\nIntel Iris\nNVIDIA GeForce\nUnsupported Graphics Devices for macOS\nAMD Radeon R9\nAMD Radeon Pro\nAMD FirePro D300\n \nWrites and syncs files to ~/Library/caveData.\n \nawips-python.pkg\n is not a prerequisite, and CAVE will still run and display data without it, but to use any derived parameter functions such as wind barbs/arrows and grid parameters on various vertical coordinates, jep must be installed in some way (it is assumed in /Library/Python/2.7/site-packages/jep/)\n\n\n\n\n\n\n\n\nWindows\n\uf0c1\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n \n\n\nMethod 1: Install Directly on Windows\n \n \nawips-cave.msi \nWrites files to \n~/caveData\n (in your user home directory)\n \nRequires \nPython 3\n, \nNumpy\n, and \nJep\n be installed\n \nRequires \nPYTHONHOME\n be defined\n \nIn addition to the application directory, the MSI installer will attempt to copy the \ngridslice\n shared library to \n$PYTHONHOME/Dlls\n.  If the \n$PYTHONHOME\n environmental variable is not defined, \ngridslice\n will not be installed. You can always rerun the installer after defining \n$PYTHONHOME\n and then check that the file \ngridslice.pyd\n is installed in \n$PYTHONHOME/Dlls\n.\n \nCAVE will still run without gridslice, but certain bundles which use derived parameters, such as \nisentropic analyses\n, will not load. \n\n\n\n\n\n\n\n\nWindows-Specific Instructions\n\n\n\n\n\n1) Download and install \nMiniconda Python 3.7 for Windows\n\uf0c1\nAllow Miniconda3 to set \nPATH\n and other environment variables.\nEnsure that \nPYTHONHOME\n is set to the Miniconda3 location.\nIf \nPYTHONHOME\n is not set, the \ngridslice\n Python module will not be installed or available.\n2) Install dependent Python packages\npip install numpy==1.15.1 jep==3.8.2\n3) Run \nawips-cave.msi \n\uf0c1\n\n  \n**NOTE:\n It has been noted that these instructions may result in the failed installation of jep and/or other required python components.  We are working on a solution to install the python dependencies properly.  If this failure occurs, then numerous products will not render properly.  At this time we offer a second option below for Windows users -- download a pre-packaged Linux VM which contains CAVE.  We're sorry for the inconvenience and appreciate your patience.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n \n\n\nMethod 2: Install Linux VM one Windows\n \n \nunidata_cave.zip \nRequires \nVMWare Workstation Player\n to be installed (free software)\nOnce zipped file is downloaded, unzip the folder by right-clicking and selecting \"Extract All\".  All files will be extracted into their own folder.\nOpen VMWare Player and go to Player >> File... >> Open, and then find the folder that was created from extracting the zipped file. There should be one file called \"CentOS 7 - Unidata CAVE\".  Select that and it'll add a new option available in the right hand side VMWare Menu. Run that new option, if it asks if it's been moved or copied, select copied.\nThe user is named awips, the password is awips. The root password is unidataAWIPS.  There should be a CAVE application icon on the desktop that will run CAVE. It should also run from the commandline with the command \"cave\".\n\n\n\n\n\n\n\n\nAWIPS Data in the Cloud\n\uf0c1\n\n\nUnidata and XSEDE Jetstream have partnered to offer a EDEX data server in the cloud, open to the Unidata university community.  Select the server in the Connectivity Preferences dialog, or enter \nedex-cloud.unidata.ucar.edu\n (without \nhttp://\n before, or \n:9581/services\n after).\n\n\n\n\n\n\ncaveData Directory\n\uf0c1\n\n\nAfter connecting to an EDEX server, you will have a local directory named \ncaveData\n which contains files synced from EDEX as well as a client-side cache for data and map resources.\n\n\nYou can reset CAVE by removing the \ncaveData\n directory and reconnecting to an EDEX server. Your local files have been removed, but if you are re-connecting to an EDEX server you have used before, the remote files will sync again to your local \n~/caveData\n (bundles, colormaps, etc.).\n\n\n\n\nLinux: \n/home/<user>/caveData\n\n\nmacOS: \n/Users/<user>/Library/caveData\n\n\nWindows: \nC:\\Users\\<user>\\caveData",
+            "text": "Install CAVE\n\uf0c1\n\n\nDownload and Install CAVE\n\uf0c1\n\n\n\n\nRelease 18.1.1-7, March 25, 2019\n\n\n\n\nLinux\n\uf0c1\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nawips_install.sh --cave \n  \n       \nFor CentOS/Red Hat 6 and 7. Installs to /awips2/cave and writes files to ~/caveData.\n \nchmod 755 awips_install.sh\nsudo ./awips_install.sh --cave\nRun CAVE from the Linux Desktop menu Applications > Internet > AWIPS CAVE, or from the command line as simply \ncave\n.\n \nSystem Requirements\nx86_64 CentOS/RHEL 6 or 7\nOpenGL 2.0 capable device\n4GB RAM\nLatest NVIDIA driver\napprox. 2GB disk space for data caching (~/caveData)\nYou can reset CAVE at any time by removing the \n~/caveData\n directory (on macOS \n~/Library/caveData\n) and reconnecting to an EDEX server. \n\n\n\n\n\n\n\n\nmacOS\n\uf0c1\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n    Download and install both\nawips-cave.dmg \nawips-python.pkg \n \nSupported Graphics Devices for macOS\nIntel HD Graphics\nIntel Iris\nNVIDIA GeForce\nUnsupported Graphics Devices for macOS\nAMD Radeon R9\nAMD Radeon Pro\nAMD FirePro D300\n \nWrites and syncs files to ~/Library/caveData.\n \nawips-python.pkg\n is not a prerequisite, and CAVE will still run and display data without it, but to use any derived parameter functions such as wind barbs/arrows and grid parameters on various vertical coordinates, jep must be installed in some way (it is assumed in /Library/Python/2.7/site-packages/jep/)\n\n\n\n\n\n\n\n\nWindows\n\uf0c1\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n \n\n\nMethod 1: Install Directly on Windows\n \n \nawips-cave.msi \nWrites files to \n~/caveData\n (in your user home directory)\n \nRequires \nPython 3\n, \nNumpy\n, and \nJep\n be installed\n \nRequires \nPYTHONHOME\n be defined\n \nIn addition to the application directory, the MSI installer will attempt to copy the \ngridslice\n shared library to \n$PYTHONHOME/Dlls\n.  If the \n$PYTHONHOME\n environmental variable is not defined, \ngridslice\n will not be installed. You can always rerun the installer after defining \n$PYTHONHOME\n and then check that the file \ngridslice.pyd\n is installed in \n$PYTHONHOME/Dlls\n.\n \nCAVE will still run without gridslice, but certain bundles which use derived parameters, such as \nisentropic analyses\n, will not load. \n\n\n\n\n\n\n\n\nWindows-Specific Instructions\n\n\n\n\n\n1) Download and install \nMiniconda Python 3.7 for Windows\n\uf0c1\nAllow Miniconda3 to set \nPATH\n and other environment variables.\nEnsure that \nPYTHONHOME\n is set to the Miniconda3 location.\nIf \nPYTHONHOME\n is not set, the \ngridslice\n Python module will not be installed or available.\n2) Install dependent Python packages\npip install numpy==1.15.1 jep==3.8.2\n3) Run \nawips-cave.msi \n\uf0c1\n\n  \n**NOTE:\n It has been noted that these instructions may result in the failed installation of jep and/or other required python components.  We are working on a solution to install the python dependencies properly.  If this failure occurs, then numerous products will not render properly.  At this time we offer a second option below for Windows users -- download a pre-packaged Linux VM which contains CAVE.  We're sorry for the inconvenience and appreciate your patience.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n \n\n\nMethod 2: Install Linux VM one Windows\n \n \nunidata_cave.zip \nRequires \nVMWare Workstation Player\n to be installed (free software)\nOnce zipped file is downloaded, unzip the folder by right-clicking and selecting \"Extract All\".  All files will be extracted into their own folder.\nOpen VMWare Player and go to Player >> File... >> Open, and then find the folder that was created from extracting the zipped file. There should be one file called \"CentOS 7 - Unidata CAVE\".  Select that and it'll add a new option available in the right hand side VMWare Menu. Run that new option, if it asks if it's been moved or copied, select copied.\nThe user is named awips, the password is awips. The root password is unidataAWIPS.  There should be a CAVE application icon on the desktop that will run CAVE. It should also run from the commandline with the command \"cave\".\n\n\n\n\n\n\n\n\nAWIPS Data in the Cloud\n\uf0c1\n\n\nUnidata and XSEDE Jetstream have partnered to offer a EDEX data server in the cloud, open to the Unidata university community.  Select the server in the Connectivity Preferences dialog, or enter \nedex-cloud.unidata.ucar.edu\n (without \nhttp://\n before, or \n:9581/services\n after).\n\n\n\n\n\n\ncaveData Directory\n\uf0c1\n\n\nAfter connecting to an EDEX server, you will have a local directory named \ncaveData\n which contains files synced from EDEX as well as a client-side cache for data and map resources.\n\n\nYou can reset CAVE by removing the \ncaveData\n directory and reconnecting to an EDEX server. Your local files have been removed, but if you are re-connecting to an EDEX server you have used before, the remote files will sync again to your local \n~/caveData\n (bundles, colormaps, etc.).\n\n\n\n\nLinux: \n/home/<user>/caveData\n\n\nmacOS: \n/Users/<user>/Library/caveData\n\n\nWindows: \nC:\\Users\\<user>\\caveData",
+            "title": "Install CAVE"
+        },
+        {
+            "location": "/install/install-cave/#install-cave",
+            "text": "",
             "title": "Install CAVE"
         },
         {
@@ -117,7 +122,12 @@
         },
         {
             "location": "/install/install-edex/",
-            "text": "Download and Install EDEX\n\uf0c1\n\n\n\n\nRelease 18.1.1-7, March 25, 2019\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n Linux  \n\n\nawips_install.sh --edex \n  \n       \nInstalls to /awips2/ directories.\n \nchmod 755 awips_install.sh\nsudo ./awips_install.sh --edex\nStart and Stop:\nedex start\nedex stop\nSystem Requirements\nx86_64 CentOS/RHEL 6 or 7\n16+ CPU cores (each CPU core is one more decoder which can run in parallel)\n24GB RAM\n700GB+ disk space\nA \nSolid State Drive (SSD)\n is highly recommended\n \nAn \nSSD\n should be mounted either to \n/awips2\n (to contain the entire EDEX system) or to \n/awips2/edex/data/hdf5\n (to contain the large files in the decoded data store). EDEX can scale to any system by adjusting the incoming LDM data feeds or adjusting the resources (CPU threads) allocated to each data type.\n64-bit CentOS/RHEL 6 and 7\n are the only supported operating systems for EDEX. You may have luck with Fedora Core 12 to 14 and Scientific Linux.\nEDEX is not supported on Debian, Ubuntu, SUSE, Solaris, OS X, or Windows.\n\n\n\n\n\n\n\n\n\n\nRead More: Distributed EDEX, Installing Across Multiple Machines\n\uf0c1\n\n\n\n\n\n\nLinux One-Time Setup\n\uf0c1\n\n\nAll of these command should be run as \nroot\n\n\n1. Create AWIPS User\n\uf0c1\n\n\n\n\nCreate user awips and group fxalpha\n\n\n  groupadd fxalpha && useradd -G fxalpha awips\n\n\n\nor if the awips account already exists:\n\n\n  groupadd fxalpha && usermod -G fxalpha awips\n\n\n\n\n\n2. Install EDEX\n\uf0c1\n\n\n\n\nDownload and run \nsudo ./awips_install.sh --edex \n\n\n  wget https://www.unidata.ucar.edu/software/awips2/awips_install.sh\n  chmod 755 awips_install.sh\n  sudo ./awips_install.sh --edex\n\n\n\n/usr/bin/edex setup\n\n\n\n\nawips_install.sh --edex\n will perform the following steps (it's always a good idea to review downloaded shell scripts):\n\n\n\n\nSaves the appropriate Yum repo file to \n/etc/yum.repos.d/awips2.repo\n\n\nIncreases process and file limits for the the \nawips\n account in \n/etc/security/limits.conf\n\n\nCreates \n/awips2/data_store\n if it does not exist already\n\n\nRuns \nyum groupinstall awips2-server\n\n\nAttempts to configure the EDEX hostname defined in \n/awips2/edex/bin/setup.env\n\n\nAlerts the user if the \nawips\n account does not exist (the RPMs will still install)\n\n\n\n\n\n\n\n\n3. EDEX Setup\n\uf0c1\n\n\n\n\nThe command \nedex setup\n will try to determine your fully-qualified domain name and set it in \n/awips2/edex/bin/setup.env\n. EDEX Server Administrators should double-check that the addresses and names defined in setup.env are resolvable from both inside and outside the server, and make appropriate edits to \n/etc/hosts\n if necessary.  \n\n\nFor example, in the XSEDE Jetstream cloud, the fully-qualified domain name defined in \n/awips2/edex/bin/setup.env\n\n\n  export EXT_ADDR=js-196-132.jetstream-cloud.org\n  export DB_ADDR=localhost\n  export DB_PORT=5432\n  export BROKER_ADDR=localhost\n  export PYPIES_SERVER=http://${EXT_ADDR}:9582\n\n\n\nis directed within to localhost in \n/etc/hosts\n\n\n  127.0.0.1   localhost localhost.localdomain js-196-132.jetstream-cloud.org\n\n\n\n\n\n4. Configure iptables\n\uf0c1\n\n\n\n\nConfigure iptables to allow TCP connections on ports 9581 and 9582 if you want to serve data to CAVE clients and the Python API.\n\n\nIf you are running a Registry (Data Delivery) server, you will also want to open port \n9588\n.\n\n\n\n\n\n\nTo open ports to all connections\n\n\n  vi /etc/sysconfig/iptables\n\n  *filter\n  :INPUT ACCEPT [0:0]\n  :FORWARD ACCEPT [0:0]\n  :OUTPUT ACCEPT [0:0]\n  -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT\n  -A INPUT -p icmp -j ACCEPT\n  -A INPUT -i lo -j ACCEPT\n  -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT\n  -A INPUT -m state --state NEW -m tcp -p tcp --dport 9581 -j ACCEPT\n  -A INPUT -m state --state NEW -m tcp -p tcp --dport 9582 -j ACCEPT\n  #-A INPUT -m state --state NEW -m tcp -p tcp --dport 9588 -j ACCEPT # for registry/dd\n  -A INPUT -j REJECT --reject-with icmp-host-prohibited\n  -A FORWARD -j REJECT --reject-with icmp-host-prohibited\n\n\n\nCOMMIT\n\n\n\n\n\n\nTo open ports to specific IP addresses\n\n\n\n\n\n\nIn this example, the IP range \n128.117.140.0/24\n will match all 128.117.140.\n addresses, while \n128.117.156.0/24\n will match 128.117.156.\n.\n\n\n      vi /etc/sysconfig/iptables\n\n      *filter\n      :INPUT DROP [0:0]\n      :FORWARD DROP [0:0]\n      :OUTPUT ACCEPT [0:0]\n      :EXTERNAL - [0:0]\n      :EDEX - [0:0]\n      -A INPUT -i lo -j ACCEPT\n      -A INPUT -p icmp --icmp-type any -j ACCEPT\n      -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT\n      -A INPUT -s 128.117.140.0/24 -j EDEX\n      -A INPUT -s 128.117.156.0/24 -j EDEX\n      -A INPUT -j EXTERNAL\n      -A EXTERNAL -j REJECT\n      -A EDEX -m state --state NEW -p tcp --dport 22 -j ACCEPT\n      -A EDEX -m state --state NEW -p tcp --dport 9581 -j ACCEPT\n      -A EDEX -m state --state NEW -p tcp --dport 9582 -j ACCEPT\n      #-A EDEX -m state --state NEW -p tcp --dport 9588 -j ACCEPT # for registry/dd\n      -A EDEX -j REJECT\n      COMMIT\n\n\n\nRestart iptables\n\n\n  service iptables restart\n\n\n\nFor CentOS 7 error \nRedirecting to /bin/systemctl restart  iptables.service\nFailed to restart iptables.service: Unit iptables.service failed to load: No such file or directory.\n\n\nThe solution is:\n\n\n  yum install iptables-services\n  systemctl enable iptables\n  service iptables restart\n\n\n\n\n\n5. Start EDEX\n\uf0c1\n\n\n\n\n  edex start\n\n\n\nTo manually start, stop, and restart:\n\n\n  service edex_postgres start\n  service httpd-pypies start\n  service qpidd start\n  service edex_camel start\n\n\n\nThe fifth service, \nedex_ldm\n, does \nnot run at boot\n to prevent filling up disk space if EDEX is not running. \n\n\n  ldmadmin start\n\n\n\nTo start \nall services except the LDM\n (good for troubleshooting):\n\n\n  edex start base\n\n\n\nTo restart EDEX\n\n\n  edex restart\n\n\n\n\n\n\n\nAdditional Steps\n\uf0c1\n\n\n/etc/security/limits.conf\n\uf0c1\n\n\n/etc/security/limits.conf\n defines the number of user processes and files (this step is automatically performed by \n./awips_install.sh --edex\n). Without these definitions, Qpid is known to crash during periods of high ingest.\n\n\nawips soft nproc 65536\nawips soft nofile 65536\n\n\n\n\n\nEnsure SELinux is Disabled\n\uf0c1\n\n\nvi /etc/sysconfig/selinux\n\n# This file controls the state of SELinux on the system.\n# SELINUX= can take one of these three values:\n#     enforcing - SELinux security policy is enforced.\n#     permissive - SELinux prints warnings instead of enforcing.\n#     disabled - No SELinux policy is loaded.\nSELINUX=disabled\n# SELINUXTYPE= can take one of these two values:\n#     targeted - Targeted processes are protected,\n#     mls - Multi Level Security protection.\nSELINUXTYPE=targeted\n\n\n\n\n\nRead more about selinux at \nredhat.com\n\n\n\n\n\n\nSSD Mount\n\uf0c1\n\n\nThough a Solid State Drive is not required, it is \nstrongly encouraged\n in order to handle the amount of disk IO for real-time IDD feeds.  \n\n\nThe simplest configuration would be to mount an 500GB+ SSD to \n/awips2\n to contain both the installed software (approx. 20GB) and the real-time data (approx. 150GB per day).\n\n\nThe default \npurge rules\n are configured such that \n/awips2\n does not exceed 450GB. \n/awips2/data_store\n is scoured every hour and should not exceed 50GB. \n\n\nIf you want to increase EDEX data retention you should mount a large disk to \n/awips2/edex/data/hdf5\n since this will be where the archived processed data exists, and any case studies created.\n\n\n    Filesystem      Size  Used Avail Use% Mounted on\n    /dev/sda1        30G  2.5G   26G   9% /\n    tmpfs            28G     0   28G   0% /dev/shm\n    /dev/sdc1       788G   81G  667G  11% /awips2\n    /dev/sdb1       788G   41G  708G  10% /awips2/edex/data/hdf5\n\n\n\n\n\nConfigure LDM Feeds\n\uf0c1\n\n\nEDEX installs its own version of the LDM to the directory \n/awips2/ldm\n.  As with a the default LDM configuration, two files are used to control what IDD feeds are ingested:\n\n\n\n\n\n\n/awips2/ldm/etc/ldmd.conf\n - specifies an upstream LDM server to request data from, and what feeds to request:\n\n\nREQUEST NEXRAD3 \"./p(DHR|DPR|DSP|DTA|DAA|DVL|EET|HHC|N0Q|N0S|N0U|OHA|NVW|NTV|NST).\" idd.unidata.ucar.edu\nREQUEST FNEXRAD|IDS|DDPLUS|UNIWISC \".*\" idd.unidata.ucar.edu\nREQUEST NGRID \".*\" idd.unidata.ucar.edu\nREQUEST NOTHER \"^TIP... KNES.*\" idd.unidata.ucar.edu\n\n\n\n\n\nread more about ldmd.conf in the LDM User Manual\n\n\n\n\n\n\n\n\n/awips2/ldm/etc/pqact.conf\n - specifies the WMO headers and file pattern actions to request:\n\n\n# Redbook graphics\nANY     ^([PQ][A-Z0-9]{3,5}) (....) (..)(..)(..) !redbook [^/]*/([^/]*)/([^/]*)/([^/]*)/([0-9]{8})\n        FILE    -overwrite -close -edex /awips2/data_store/redbook/\\8/\\4\\5Z_\\8_\\7_\\6-\\1_\\2_(seq).rb.%Y%m%d%H\n# NOAAPORT GINI images\nNIMAGE  ^(sat[^/]*)/ch[0-9]/([^/]*)/([^/]*)/([^ ]*) ([^/]*)/([^/]*)/([^/]*)/ (T[^ ]*) ([^ ]*) (..)(..)(..)\n        FILE    -overwrite -close -edex /awips2/data_store/sat/\\(11)\\(12)Z_\\3_\\7_\\6-\\8_\\9_(seq).satz.%Y%m%d%H\n\n\n\n\n\nread more about pqact.conf in the LDM User Manual\n\n\n\n\n\n\nsee available AWIPS LDM feeds\n\n\n\n\n\n\n\n\n\n\nDirectories to Know\n\uf0c1\n\n\n\n\n/awips2\n - Contains all of the installed AWIPS software. \n\n\n/awips2/edex/logs\n - EDEX logs.\n\n\n/awips2/httpd_pypies/var/log/httpd\n - httpd-pypies logs.\n\n\n/awips2/database/data/pg_log\n - PostgreSQL logs.\n\n\n/awips2/qpid/log\n - Qpid logs.\n\n\n/awips2/edex/data/hdf5\n - HDF5 data store. \n\n\n/awips2/edex/data/utility\n - Localization store and configuration files. \n\n\n/awips2/ldm/etc\n - Location of \nldmd.conf\n and \npqact.conf\n\n\n/awips2/ldm/logs\n - LDM logs.\n\n\n/awips2/data_store\n - Raw data store.\n\n\n/awips2/data_store/ingest\n - Manual data ingest endpoint.\n\n\n\n\n\n\nWhat Version is my EDEX?\n\uf0c1\n\n\nrpm -qa | grep awips2-edex",
+            "text": "Install EDEX\n\uf0c1\n\n\nDownload and Install EDEX\n\uf0c1\n\n\n\n\nRelease 18.1.1-7, March 25, 2019\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n Linux  \n\n\nawips_install.sh --edex \n  \n       \nInstalls to /awips2/ directories.\n \nchmod 755 awips_install.sh\nsudo ./awips_install.sh --edex\nStart and Stop:\nedex start\nedex stop\nSystem Requirements\nx86_64 CentOS/RHEL 6 or 7\n16+ CPU cores (each CPU core is one more decoder which can run in parallel)\n24GB RAM\n700GB+ disk space\nA \nSolid State Drive (SSD)\n is highly recommended\n \nAn \nSSD\n should be mounted either to \n/awips2\n (to contain the entire EDEX system) or to \n/awips2/edex/data/hdf5\n (to contain the large files in the decoded data store). EDEX can scale to any system by adjusting the incoming LDM data feeds or adjusting the resources (CPU threads) allocated to each data type.\n64-bit CentOS/RHEL 6 and 7\n are the only supported operating systems for EDEX. You may have luck with Fedora Core 12 to 14 and Scientific Linux.\nEDEX is not supported on Debian, Ubuntu, SUSE, Solaris, OS X, or Windows.\n\n\n\n\n\n\n\n\n\n\nRead More: Distributed EDEX, Installing Across Multiple Machines\n\uf0c1\n\n\n\n\n\n\nLinux One-Time Setup\n\uf0c1\n\n\nAll of these command should be run as \nroot\n\n\n1. Create AWIPS User\n\uf0c1\n\n\n\n\nCreate user awips and group fxalpha\n\n\n  groupadd fxalpha && useradd -G fxalpha awips\n\n\n\nor if the awips account already exists:\n\n\n  groupadd fxalpha && usermod -G fxalpha awips\n\n\n\n\n\n2. Install EDEX\n\uf0c1\n\n\n\n\nDownload and run \nsudo ./awips_install.sh --edex \n\n\n  wget https://www.unidata.ucar.edu/software/awips2/awips_install.sh\n  chmod 755 awips_install.sh\n  sudo ./awips_install.sh --edex\n\n\n\n/usr/bin/edex setup\n\n\n\n\nawips_install.sh --edex\n will perform the following steps (it's always a good idea to review downloaded shell scripts):\n\n\n\n\nSaves the appropriate Yum repo file to \n/etc/yum.repos.d/awips2.repo\n\n\nIncreases process and file limits for the the \nawips\n account in \n/etc/security/limits.conf\n\n\nCreates \n/awips2/data_store\n if it does not exist already\n\n\nRuns \nyum groupinstall awips2-server\n\n\nAttempts to configure the EDEX hostname defined in \n/awips2/edex/bin/setup.env\n\n\nAlerts the user if the \nawips\n account does not exist (the RPMs will still install)\n\n\n\n\n\n\n\n\n3. EDEX Setup\n\uf0c1\n\n\n\n\nThe command \nedex setup\n will try to determine your fully-qualified domain name and set it in \n/awips2/edex/bin/setup.env\n. EDEX Server Administrators should double-check that the addresses and names defined in setup.env are resolvable from both inside and outside the server, and make appropriate edits to \n/etc/hosts\n if necessary.\n\n\nFor example, in the XSEDE Jetstream cloud, the fully-qualified domain name defined in \n/awips2/edex/bin/setup.env\n\n\n  export EXT_ADDR=js-196-132.jetstream-cloud.org\n  export DB_ADDR=localhost\n  export DB_PORT=5432\n  export BROKER_ADDR=localhost\n  export PYPIES_SERVER=http://${EXT_ADDR}:9582\n\n\n\nis directed within to localhost in \n/etc/hosts\n\n\n  127.0.0.1   localhost localhost.localdomain js-196-132.jetstream-cloud.org\n\n\n\n\n\n4. Configure iptables\n\uf0c1\n\n\n\n\nConfigure iptables to allow TCP connections on ports 9581 and 9582 if you want to serve data to CAVE clients and the Python API.\n\n\nIf you are running a Registry (Data Delivery) server, you will also want to open port \n9588\n.\n\n\n\n\n\n\nTo open ports to all connections\n\n\n  vi /etc/sysconfig/iptables\n\n  *filter\n  :INPUT ACCEPT [0:0]\n  :FORWARD ACCEPT [0:0]\n  :OUTPUT ACCEPT [0:0]\n  -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT\n  -A INPUT -p icmp -j ACCEPT\n  -A INPUT -i lo -j ACCEPT\n  -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT\n  -A INPUT -m state --state NEW -m tcp -p tcp --dport 9581 -j ACCEPT\n  -A INPUT -m state --state NEW -m tcp -p tcp --dport 9582 -j ACCEPT\n  #-A INPUT -m state --state NEW -m tcp -p tcp --dport 9588 -j ACCEPT # for registry/dd\n  -A INPUT -j REJECT --reject-with icmp-host-prohibited\n  -A FORWARD -j REJECT --reject-with icmp-host-prohibited\n\n\n\nCOMMIT\n\n\n\n\n\n\nTo open ports to specific IP addresses\n\n\n\n\n\n\nIn this example, the IP range \n128.117.140.0/24\n will match all 128.117.140.\n addresses, while \n128.117.156.0/24\n will match 128.117.156.\n.\n\n\n      vi /etc/sysconfig/iptables\n\n      *filter\n      :INPUT DROP [0:0]\n      :FORWARD DROP [0:0]\n      :OUTPUT ACCEPT [0:0]\n      :EXTERNAL - [0:0]\n      :EDEX - [0:0]\n      -A INPUT -i lo -j ACCEPT\n      -A INPUT -p icmp --icmp-type any -j ACCEPT\n      -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT\n      -A INPUT -s 128.117.140.0/24 -j EDEX\n      -A INPUT -s 128.117.156.0/24 -j EDEX\n      -A INPUT -j EXTERNAL\n      -A EXTERNAL -j REJECT\n      -A EDEX -m state --state NEW -p tcp --dport 22 -j ACCEPT\n      -A EDEX -m state --state NEW -p tcp --dport 9581 -j ACCEPT\n      -A EDEX -m state --state NEW -p tcp --dport 9582 -j ACCEPT\n      #-A EDEX -m state --state NEW -p tcp --dport 9588 -j ACCEPT # for registry/dd\n      -A EDEX -j REJECT\n      COMMIT\n\n\n\nRestart iptables\n\n\n  service iptables restart\n\n\n\nFor CentOS 7 error \nRedirecting to /bin/systemctl restart  iptables.service\nFailed to restart iptables.service: Unit iptables.service failed to load: No such file or directory.\n\n\nThe solution is:\n\n\n  yum install iptables-services\n  systemctl enable iptables\n  service iptables restart\n\n\n\n\n\n5. Start EDEX\n\uf0c1\n\n\n\n\n  edex start\n\n\n\nTo manually start, stop, and restart:\n\n\n  service edex_postgres start\n  service httpd-pypies start\n  service qpidd start\n  service edex_camel start\n\n\n\nThe fifth service, \nedex_ldm\n, does \nnot run at boot\n to prevent filling up disk space if EDEX is not running.\n\n\n  ldmadmin start\n\n\n\nTo start \nall services except the LDM\n (good for troubleshooting):\n\n\n  edex start base\n\n\n\nTo restart EDEX\n\n\n  edex restart\n\n\n\n\n\n\n\nAdditional Steps\n\uf0c1\n\n\n/etc/security/limits.conf\n\uf0c1\n\n\n/etc/security/limits.conf\n defines the number of user processes and files (this step is automatically performed by \n./awips_install.sh --edex\n). Without these definitions, Qpid is known to crash during periods of high ingest.\n\n\nawips soft nproc 65536\nawips soft nofile 65536\n\n\n\n\n\nEnsure SELinux is Disabled\n\uf0c1\n\n\nvi /etc/sysconfig/selinux\n\n# This file controls the state of SELinux on the system.\n# SELINUX= can take one of these three values:\n#     enforcing - SELinux security policy is enforced.\n#     permissive - SELinux prints warnings instead of enforcing.\n#     disabled - No SELinux policy is loaded.\nSELINUX=disabled\n# SELINUXTYPE= can take one of these two values:\n#     targeted - Targeted processes are protected,\n#     mls - Multi Level Security protection.\nSELINUXTYPE=targeted\n\n\n\n\n\nRead more about selinux at \nredhat.com\n\n\n\n\n\n\nSSD Mount\n\uf0c1\n\n\nThough a Solid State Drive is not required, it is \nstrongly encouraged\n in order to handle the amount of disk IO for real-time IDD feeds.\n\n\nThe simplest configuration would be to mount an 500GB+ SSD to \n/awips2\n to contain both the installed software (approx. 20GB) and the real-time data (approx. 150GB per day).\n\n\nThe default \npurge rules\n are configured such that \n/awips2\n does not exceed 450GB. \n/awips2/data_store\n is scoured every hour and should not exceed 50GB.\n\n\nIf you want to increase EDEX data retention you should mount a large disk to \n/awips2/edex/data/hdf5\n since this will be where the archived processed data exists, and any case studies created.\n\n\n    Filesystem      Size  Used Avail Use% Mounted on\n    /dev/sda1        30G  2.5G   26G   9% /\n    tmpfs            28G     0   28G   0% /dev/shm\n    /dev/sdc1       788G   81G  667G  11% /awips2\n    /dev/sdb1       788G   41G  708G  10% /awips2/edex/data/hdf5\n\n\n\n\n\nConfigure LDM Feeds\n\uf0c1\n\n\nEDEX installs its own version of the LDM to the directory \n/awips2/ldm\n.  As with a the default LDM configuration, two files are used to control what IDD feeds are ingested:\n\n\n\n\n\n\n/awips2/ldm/etc/ldmd.conf\n - specifies an upstream LDM server to request data from, and what feeds to request:\n\n\nREQUEST NEXRAD3 \"./p(DHR|DPR|DSP|DTA|DAA|DVL|EET|HHC|N0Q|N0S|N0U|OHA|NVW|NTV|NST).\" idd.unidata.ucar.edu\nREQUEST FNEXRAD|IDS|DDPLUS|UNIWISC \".*\" idd.unidata.ucar.edu\nREQUEST NGRID \".*\" idd.unidata.ucar.edu\nREQUEST NOTHER \"^TIP... KNES.*\" idd.unidata.ucar.edu\n\n\n\n\n\nread more about ldmd.conf in the LDM User Manual\n\n\n\n\n\n\n\n\n/awips2/ldm/etc/pqact.conf\n - specifies the WMO headers and file pattern actions to request:\n\n\n# Redbook graphics\nANY     ^([PQ][A-Z0-9]{3,5}) (....) (..)(..)(..) !redbook [^/]*/([^/]*)/([^/]*)/([^/]*)/([0-9]{8})\n        FILE    -overwrite -close -edex /awips2/data_store/redbook/\\8/\\4\\5Z_\\8_\\7_\\6-\\1_\\2_(seq).rb.%Y%m%d%H\n# NOAAPORT GINI images\nNIMAGE  ^(sat[^/]*)/ch[0-9]/([^/]*)/([^/]*)/([^ ]*) ([^/]*)/([^/]*)/([^/]*)/ (T[^ ]*) ([^ ]*) (..)(..)(..)\n        FILE    -overwrite -close -edex /awips2/data_store/sat/\\(11)\\(12)Z_\\3_\\7_\\6-\\8_\\9_(seq).satz.%Y%m%d%H\n\n\n\n\n\nread more about pqact.conf in the LDM User Manual\n\n\n\n\n\n\nsee available AWIPS LDM feeds\n\n\n\n\n\n\n\n\n\n\nDirectories to Know\n\uf0c1\n\n\n\n\n/awips2\n - Contains all of the installed AWIPS software.\n\n\n/awips2/edex/logs\n - EDEX logs.\n\n\n/awips2/httpd_pypies/var/log/httpd\n - httpd-pypies logs.\n\n\n/awips2/database/data/pg_log\n - PostgreSQL logs.\n\n\n/awips2/qpid/log\n - Qpid logs.\n\n\n/awips2/edex/data/hdf5\n - HDF5 data store.\n\n\n/awips2/edex/data/utility\n - Localization store and configuration files.\n\n\n/awips2/ldm/etc\n - Location of \nldmd.conf\n and \npqact.conf\n\n\n/awips2/ldm/logs\n - LDM logs.\n\n\n/awips2/data_store\n - Raw data store.\n\n\n/awips2/data_store/ingest\n - Manual data ingest endpoint.\n\n\n\n\n\n\nWhat Version is my EDEX?\n\uf0c1\n\n\nrpm -qa | grep awips2-edex",
+            "title": "Install EDEX"
+        },
+        {
+            "location": "/install/install-edex/#install-edex",
+            "text": "",
             "title": "Install EDEX"
         },
         {
@@ -147,7 +157,7 @@
         },
         {
             "location": "/install/install-edex/#3-edex-setup",
-            "text": "The command  edex setup  will try to determine your fully-qualified domain name and set it in  /awips2/edex/bin/setup.env . EDEX Server Administrators should double-check that the addresses and names defined in setup.env are resolvable from both inside and outside the server, and make appropriate edits to  /etc/hosts  if necessary.    For example, in the XSEDE Jetstream cloud, the fully-qualified domain name defined in  /awips2/edex/bin/setup.env    export EXT_ADDR=js-196-132.jetstream-cloud.org\n  export DB_ADDR=localhost\n  export DB_PORT=5432\n  export BROKER_ADDR=localhost\n  export PYPIES_SERVER=http://${EXT_ADDR}:9582  is directed within to localhost in  /etc/hosts    127.0.0.1   localhost localhost.localdomain js-196-132.jetstream-cloud.org",
+            "text": "The command  edex setup  will try to determine your fully-qualified domain name and set it in  /awips2/edex/bin/setup.env . EDEX Server Administrators should double-check that the addresses and names defined in setup.env are resolvable from both inside and outside the server, and make appropriate edits to  /etc/hosts  if necessary.  For example, in the XSEDE Jetstream cloud, the fully-qualified domain name defined in  /awips2/edex/bin/setup.env    export EXT_ADDR=js-196-132.jetstream-cloud.org\n  export DB_ADDR=localhost\n  export DB_PORT=5432\n  export BROKER_ADDR=localhost\n  export PYPIES_SERVER=http://${EXT_ADDR}:9582  is directed within to localhost in  /etc/hosts    127.0.0.1   localhost localhost.localdomain js-196-132.jetstream-cloud.org",
             "title": "3. EDEX Setup"
         },
         {
@@ -157,7 +167,7 @@
         },
         {
             "location": "/install/install-edex/#5-start-edex",
-            "text": "edex start  To manually start, stop, and restart:    service edex_postgres start\n  service httpd-pypies start\n  service qpidd start\n  service edex_camel start  The fifth service,  edex_ldm , does  not run at boot  to prevent filling up disk space if EDEX is not running.     ldmadmin start  To start  all services except the LDM  (good for troubleshooting):    edex start base  To restart EDEX    edex restart",
+            "text": "edex start  To manually start, stop, and restart:    service edex_postgres start\n  service httpd-pypies start\n  service qpidd start\n  service edex_camel start  The fifth service,  edex_ldm , does  not run at boot  to prevent filling up disk space if EDEX is not running.    ldmadmin start  To start  all services except the LDM  (good for troubleshooting):    edex start base  To restart EDEX    edex restart",
             "title": "5. Start EDEX"
         },
         {
@@ -177,7 +187,7 @@
         },
         {
             "location": "/install/install-edex/#ssd-mount",
-            "text": "Though a Solid State Drive is not required, it is  strongly encouraged  in order to handle the amount of disk IO for real-time IDD feeds.    The simplest configuration would be to mount an 500GB+ SSD to  /awips2  to contain both the installed software (approx. 20GB) and the real-time data (approx. 150GB per day).  The default  purge rules  are configured such that  /awips2  does not exceed 450GB.  /awips2/data_store  is scoured every hour and should not exceed 50GB.   If you want to increase EDEX data retention you should mount a large disk to  /awips2/edex/data/hdf5  since this will be where the archived processed data exists, and any case studies created.      Filesystem      Size  Used Avail Use% Mounted on\n    /dev/sda1        30G  2.5G   26G   9% /\n    tmpfs            28G     0   28G   0% /dev/shm\n    /dev/sdc1       788G   81G  667G  11% /awips2\n    /dev/sdb1       788G   41G  708G  10% /awips2/edex/data/hdf5",
+            "text": "Though a Solid State Drive is not required, it is  strongly encouraged  in order to handle the amount of disk IO for real-time IDD feeds.  The simplest configuration would be to mount an 500GB+ SSD to  /awips2  to contain both the installed software (approx. 20GB) and the real-time data (approx. 150GB per day).  The default  purge rules  are configured such that  /awips2  does not exceed 450GB.  /awips2/data_store  is scoured every hour and should not exceed 50GB.  If you want to increase EDEX data retention you should mount a large disk to  /awips2/edex/data/hdf5  since this will be where the archived processed data exists, and any case studies created.      Filesystem      Size  Used Avail Use% Mounted on\n    /dev/sda1        30G  2.5G   26G   9% /\n    tmpfs            28G     0   28G   0% /dev/shm\n    /dev/sdc1       788G   81G  667G  11% /awips2\n    /dev/sdb1       788G   41G  708G  10% /awips2/edex/data/hdf5",
             "title": "SSD Mount"
         },
         {
@@ -187,7 +197,7 @@
         },
         {
             "location": "/install/install-edex/#directories-to-know",
-            "text": "/awips2  - Contains all of the installed AWIPS software.   /awips2/edex/logs  - EDEX logs.  /awips2/httpd_pypies/var/log/httpd  - httpd-pypies logs.  /awips2/database/data/pg_log  - PostgreSQL logs.  /awips2/qpid/log  - Qpid logs.  /awips2/edex/data/hdf5  - HDF5 data store.   /awips2/edex/data/utility  - Localization store and configuration files.   /awips2/ldm/etc  - Location of  ldmd.conf  and  pqact.conf  /awips2/ldm/logs  - LDM logs.  /awips2/data_store  - Raw data store.  /awips2/data_store/ingest  - Manual data ingest endpoint.",
+            "text": "/awips2  - Contains all of the installed AWIPS software.  /awips2/edex/logs  - EDEX logs.  /awips2/httpd_pypies/var/log/httpd  - httpd-pypies logs.  /awips2/database/data/pg_log  - PostgreSQL logs.  /awips2/qpid/log  - Qpid logs.  /awips2/edex/data/hdf5  - HDF5 data store.  /awips2/edex/data/utility  - Localization store and configuration files.  /awips2/ldm/etc  - Location of  ldmd.conf  and  pqact.conf  /awips2/ldm/logs  - LDM logs.  /awips2/data_store  - Raw data store.  /awips2/data_store/ingest  - Manual data ingest endpoint.",
             "title": "Directories to Know"
         },
         {