Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Great explanation. Thank you Erik. On Tue, Aug 26, 2014 at 2:01 PM, Magnuson.Erik <Magnuson.Erik@xxxxxxxxx> wrote: > How this works is that unless running in thin client mode, EDEX and > CAVE need to resolve the server names defined in > /awips2/edex/bin/setup.env to addresses that work on the respective hosts: > > > > BROKER_ADDR > > PYPIES_SERVER > > HTTP_SERVER > > JMS_SERVER > > > > These variables are used both by EDEX and transmitted to CAVE at startup. > For example if: > > export PYPIES_SERVER=http://foo.invalid:9582 > > > > then both EDEX and CAVE hosts need to resolve foo.invalid to something > reachable on port 9582. If the internal and external addresses on the EDEX > server are different, then you will need to alias foo.invalid to internal > IP address on the EDEX server OR create a hosts entry on the CAVE client > for foo.invalid to be the external IP of the EDEX. While the Unidata > install automatically sets these variables to the hostname, you can edit > them by hand and restart edex if that’s more convenient. > > > > If you are paranoid, you can also set ‘export DB_ADDR=localhost’ and then > remove non-localhost entries from /awips2/data/pg_hba.conf as CAVE does not > access the db host directly. >
awips2-users archives: