Because AWIPS II is still in development and not ready for release, this document is intended only as an informational guide and is subject to change at any time.
The AWIPS II EDEX server requires a user account
All AWIPS II packages are installed in the base directory
IPv6 must be enabled for the EDEX server to run properly.
AWIPS II must be installed by
A yum repository file will be provided with AWIPS II. This
>cat awips2.repo [awips2repo] name=AWIPS II Repository baseurl=file:///awips2/repo/13.1.2/ enabled=1 protect=0 gpgcheck=0 proxy=_none_
For the example above,
For a single-server standalone installation, constituting all EDEX server packages installed and running on a single server, (as
yum groupinstall awips2-standalone
A total of 67 packages are installed (64 contain awips2 in their name; 3 have netcdf in their name). You can check the number of packages installed at any time by issuing the command
... ------------------------------------------------------------------------- Total 6.3 GB/s | 206 MB 00:00 Running rpm_check_debug Transaction Test Succeeded Running Transaction ------------------------------------------------------------------------- \| Installing the AWIPS II Python Distribution... ------------------------------------------------------------------------- Installation Root = /awips2/python Installing: awips2-python [#################### ] 1/24
Download the shell script edex and copy to
As root, run
edex setup
[edex] EDEX IP and Hostname Setup
Checking /awips2/data/pg_hba.conf
** Missing 128.117.140
Checking /awips2/edex/bin/setup.env
** Missing /data_store
Checking /awips2/httpd_pypies/etc/httpd/conf/httpd.conf
** Missing Group fxalpha
Do you want to allow these edits? [y/n]y
[edit] 128.117.140.0 added to /awips2/data/pg_hba.conf
File backed up to /awips2/data/
DATA_ARCHIVE_ROOT set to /data_store in /awips2/edex/bin/setup.env
File backed up to /awips2/edex/bin/
[edit] Group fxalpha added to /awips2/httpd_pypies/etc/httpd/conf/httpd.conf
File backed up to /awips2/httpd_pypies/etc/httpd/conf/
[done]
If you attempt to run
To check your EDEX server configuration at any time, issue the
>edex setup [edex] EDEX IP and Hostname Setup Checking /awips2/data/pg_hba.conf [OK] Checking /awips2/edex/bin/setup.env [OK] Checking /awips2/httpd_pypies/etc/httpd/conf/httpd.conf [OK] EDEX correctly configured
Check the status of EDEX services with
>edex status [edex status] Postgres :: not running PyPIES :: not running QPID :: not running EDEXingest :: not running EDEXgrib :: not running EDEXrequest :: not running EDEXdat :: not running
Start all EDEX services with the command
>edex start Starting EDEX PostgreSQL: Starting logging service: [ OK ] Starting httpd: [ OK ] Starting Qpid AMQP daemon: [ OK ] Creating durable queues Creating queue external.dropbox Creating queue Ingest.Grib ... Creating queue Ingest.Satellite Creating queue Ingest.dhr Creating queue dhrProcess Starting EDEX Camel (ingest): OK Starting EDEX Camel (ingestGrib): OK Starting EDEX Camel (request): OK ************************************************** * Waiting for EDEX ESB to become operational * * - This may take a few minutes * * - Do not start CAVE until this is complete * ************************************************** .................................................. .................................................. ......... ************************************************** * EDEX ESB is now operational * * You may now start alertviz and CAVE * **************************************************
If a problem is reported by
service edex_postgres start service httpd-pypies start service qpid start service edex_camel start
To stop all EDEX services:
edex stop Stopping EDEX Camel (ingest): OK Stopping EDEX Camel (ingestGrib): OK Stopping EDEX Camel (ingestDat): OK Stopping EDEX Camel (request): OK Stopping Qpid AMQP daemon: [ OK ] Stopping httpd: [ OK ] Stopping logging service: [ OK ] Stopping EDEX PostgreSQL: server stopped
The LDM is installed by the command
When the package in installed, it should be ready to run "out of the box". Start the LDM with the command
CAVE and Alertviz are installed by a separate group installation package
yum groupinstall awips2-visualize -y
Unlike the EDEX server, CAVE can be run as a user other than
chown -R awips:fxalpha /awips2
Client-only installation (CAVE installed locally and connection to a separate EDEX server) allows for custom owner and group permissions for
chown -R [user]:[group] /awips2
If this is the first time CAVE is run on your system, you will be prompted to connect to an EDEX server. CAVE will not run if you are unable to verify and connect to a server. Upon first startup, the directory
Alertiviz must be started:
/awips2/alertviz/alertviz.sh
Before CAVE can be launched from another terminal:
/awips2/cave/cave.sh
Alertviz will add itself to System Startup Preferences for every user on the CAVE system. Alertviz will then start automatically on login. To disable this on the GNOME or KDE desktop, open
To uninstall the CAVE client group:
yum groupremove awips2-visualize -y
To uninstall all EDEX server components:
yum groupremove awips2-standalone -y
Note that the above command will also remove the CAVE/visualization group if it's installed on the same system as the EDEX server components.
Check if any AWIPS II packages are still installed:
rpm -qa | grep awips2
and optionally remove them manually:
yum remove `rpm -qa | grep awips2 | awk '{ print $1 }'`
If you encounter a problem with any of the EDEX services be sure to check the appropriate logs, which are written with the date or process ID in the filename:
EDEX Ingest logs:
PostgreSQL logs:
Alertviz logs:
CAVE logs:
To list all available AWIPS II installation groups:
yum grouplist | grep AWIPS AWIPS II Backup Database Server AWIPS II Database Server AWIPS II LDM Server AWIPS II Message Broker Server AWIPS II Processing Server AWIPS II Rehost Server AWIPS II Standalone AWIPS II Visualize
Unidata now maintains an AWIPS II support desk which can be reached at