This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
> Is there any installation guides on how to install and configure AWIPS? It seems you found the installation guide and copied the installation instructions to your email. So I'm confused why you're asking for the installation guide here. > I created a Windows VM and installed CAVE but I cannot connect to : I get > an error when I try to connect (see attached screen shot) There's probably a firewall application blocking outgoing connections on certain ports. > I also created a Red Hat Linux 6 64-bit VM and am trying to install EDEX > on that but am also getting some errors. Do I have to create certain > partitions in the original installation of Linux for EDEX to work? As > root do I need to complete all of the following to get it up and running > on the Linux VM http://unidata.github.io/awips2/docs/install/install-edex.html > Is this the proper way that I should be installing the software? Yes. selinux must be disabled. The iptables config isn't required to get EDEX running, but is required for clients to be able to connect. There needs to be a directory /awips2/data_store, which is created by the script installEDEX.sh, which can downloaded from our website and the AWIPS user manual site on github pages. > CAVE on the Windows 7 VM and EDEX on RHEL 6 64-bit VM? Our edex-cloud.unidata.ucar.edu server is open to the public, so you can at least test your CAVE connection to that server first. Ticket Details =================== Ticket ID: GXU-309465 Department: Support AWIPS Priority: Normal Status: Open =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.