<li><strong>16GB</strong> RAM (32+GB recommended for full IDD processing)</li>
<li><strong>500GB</strong> disk space, more if you build a data archive.</li>
</ul>
</div>
<p>An <strong>SSD is an especially good idea</strong>, mounted to <strong>/awips2/edex/data/hdf5</strong> to contain the decoded data files, or mounted to <strong>/awips2</strong> to contain the entire AWIPS software system.</p>
<p>EDEX <strong>can scale to any system</strong>, either by adjusting the incoming data feeds, or the resources allocated to each data type, but when selecting a server, <strong>more is always better</strong>.</p>
<p><strong>64-bit CentOS/RHEL 6 and 7</strong> are the only supported Linux operating systems. You may have luck with Fedora Core 12 to 14 and Scientific Linux. EDEX is not developed, tested, or supported on Debian, Ubuntu, SUSE, Solaris, OS X, or Windows.</p>
<p>Configure iptables to allow TCP connections on ports 5672, 9581 and 9582</p>
<ul>
<li>
<p><strong>To open ports to all connections</strong></p>
<pre><code>vi /etc/sysconfig/iptables
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 5672 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 9581 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 9582 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
</code></pre>
</li>
<li>
<p><strong>To open ports to specific IP addresses</strong></p>
<pre><code>vi /etc/sysconfig/iptables
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [0:0]
:EXTERNAL - [0:0]
:EDEX - [0:0]
-A INPUT -i lo -j ACCEPT
-A INPUT -p icmp --icmp-type any -j ACCEPT
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -s 128.117.140.0/24 -j EDEX
-A INPUT -s 128.117.156.0/24 -j EDEX
-A INPUT -j EXTERNAL
-A EXTERNAL -j REJECT
-A EDEX -m state --state NEW -p tcp --dport 22 -j ACCEPT
-A EDEX -m state --state NEW -p tcp --dport 5672 -j ACCEPT
-A EDEX -m state --state NEW -p tcp --dport 9581 -j ACCEPT
-A EDEX -m state --state NEW -p tcp --dport 9582 -j ACCEPT
-A EDEX -j REJECT
COMMIT
</code></pre>
</li>
</ul>
<blockquote>
<p>In this example, the IP range <code>128.117.140.0/24</code> will match all 128.117.140.<em> addresses, while <code>128.117.156.0/24</code> will match 128.117.156.</em>.</p>
</blockquote>
<p><strong>Restart iptables</strong></p>
<pre><code>service iptables restart
</code></pre>
<p>For CentOS 7 error <em>Redirecting to /bin/systemctl restart iptables.service
Failed to restart iptables.service: Unit iptables.service failed to load: No such file or directory.</em></p>
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of these two values:
# targeted - Targeted processes are protected,
# mls - Multi Level Security protection.
SELINUXTYPE=targeted
</code></pre>
<divclass="admonition note">
<pclass="admonition-title">Read more about selinux at <ahref="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html">redhat.com</a></p>
</div>
<p><strong>reboot if necessary</strong>, required if iptables was updated.</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 <ahref="">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
<p>Download the script <ahref="http://www.unidata.ucar.edu/software/awips2/installEDEX.sh">installEDEX.sh</a> to setup and run yum to install AWIPS packages:</p>
<pclass="admonition-title">What does <ahref="http://www.unidata.ucar.edu/software/awips2/installEDEX.sh">installEDEX.sh</a> do?</p>
<ol>
<li>Downloads <ahref="http://www.unidata.ucar.edu/software/awips2/doc/awips2.repo">awips2.repo</a> or <ahref="http://www.unidata.ucar.edu/software/awips2/doc/el7.repo">el7.repo</a> to <strong>/etc/yum.repos.d/awips2.repo</strong></li>
<p>The command <strong>edex setup</strong> attempts to add the domain name of your server. </p>
<ul>
<li>
<p><strong>/awips2/edex/bin/setup.env</strong> should contain the fully-qualified domain name, externally resolved, localhost will not work. </p>
<pre><code>export AW_SITE_IDENTIFIER=OAX
export EDEX_SERVER=edex-cloud.unidata.ucar.edu
</code></pre>
</li>
<li>
<p><strong>/awips2/ldm/etc/ldmd.conf</strong> contains the upstream server (default <em>idd.unidata.ucar.edu</em>, which requires you connect form a .edu domain). This file also contains the <strong>edexBridge</strong> hostname (default <em>localhost</em>). </p>
<pre><code>EXEC "pqact -e"
EXEC "edexBridge -s localhost"
</code></pre>
</li>
<li>
<p><strong>/etc/security/limits.conf</strong> defines the number of user processes and files (this step is automatically performed by <strong>installEDEX.sh</strong>). Without these definitions, Qpid is known to crash during periods of high ingest.</p>
<p>EDEX installs its own version of the LDM to the directory <strong>/awips2/ldm</strong>. As with a the default LDM configuration, two files are used to control what IDD feeds are ingested:</p>
<ul>
<li>
<p><strong>/awips2/ldm/etc/ldmd.conf</strong> - specifies an upstream LDM server to request data from, and what feeds to request:</p>
<pclass="admonition-title"><ahref="https://www.unidata.ucar.edu/software/ldm/ldm-current/basics/ldmd.conf.html">read more about ldmd.conf in the LDM User Manual</a></p>
</div>
</li>
<li>
<p><strong>/awips2/ldm/etc/pqact.conf</strong> - specifies the WMO headers and file pattern actions to request:</p>
<pre><code># Redbook graphics
ANY ^([PQ][A-Z0-9]{3,5}) (....) (..)(..)(..) !redbook [^/]*/([^/]*)/([^/]*)/([^/]*)/([0-9]{8})
<pclass="admonition-title"><ahref="https://www.unidata.ucar.edu/software/ldm/ldm-current/basics/pqact.conf.html">read more about pqact.conf in the LDM User Manual</a></p>
</div>
<divclass="admonition tip">
<pclass="admonition-title"><ahref="../../edex/ldm/">see available AWIPS LDM feeds</a></p>
</div>
</li>
</ul>
<hr/>
<h2id="start-and-stop">Start and Stop<aclass="headerlink"href="#start-and-stop"title="Permanent link"></a></h2>
<p>to start all EDEX services, including the LDM:</p>
<pre><code>edex start
Starting EDEX PostgreSQL: [ OK ]
Starting httpd: [ OK ]
Starting QPID [ OK ]
Starting EDEX Camel (request):
Starting EDEX Camel (ingest):
Starting EDEX Camel (ingestGrib):
Starting AWIPS LDM:The product-queue is OK.
</code></pre>
<p>to stop:</p>
<pre><code>edex stop
Stopping EDEX Camel (request):
Stopping EDEX Camel (ingest):
Stopping EDEX Camel (ingestGrib):
Stopping QPID [ OK ]
Stopping httpd: [ OK ]
Stopping EDEX PostgreSQL: [ OK ]
Stopping AWIPS LDM:Stopping the LDM server...
</code></pre>
<p>To manually start, stop, and restart:</p>
<pre><code>service edex_postgres start
service httpd-pypies start
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>
<pre><code>ldmadmin start
</code></pre>
<p>To start <em>all services except the LDM</em> (good for troubleshooting):</p>
<pre><code>edex start base
</code></pre>
<p>To restart EDEX</p>
<pre><code>edex restart
</code></pre>
<hr/>
<h2id="directories-to-know">Directories to know<aclass="headerlink"href="#directories-to-know"title="Permanent link"></a></h2>
<ul>
<li><code>/awips2</code> - Contains all of the installed AWIPS software. </li>
