ESPDS: NOAA/NESDIS Environmental Satellite Processing and Distribution System
DPA: Data Provider Agent
* need to run keygenutil once and then copy keystore files to edex src directories for deployment
* "securityConfiguration" is so ingrained into data delivery that you cannot harvest from open servers (GRADS, THREDDS) without having a security config (which is only used to connect to ESPDS PDA server).
* need to specify opendap/grads server in existing file, and add TDS file for the same with a catalog DOD URL:
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 *:telelpathattack *:* LISTEN 19580/java
tcp 0 0 *:us-cli *:* LISTEN 19580/java
tcp 0 0 *:9581 *:* LISTEN 19580/java
# NCF registry (havester/crawler)
the Harvester only runs at the Central Registry. As a
result, the WFO's no longer need to be concerned with the configuration of the Harvester.
The NCF (Central Registry) handles the maintenance of the Crawler.
/etc/init.d/edex_camel start centralRegistry
# Site (subscribe)
/etc/init.d/edex_camel start registry
Data Delivery has been implemented into the AWIPS(II) baseline to provide access to data that is not resident locally at a Weather Forecast Office, River Forecast Center, or National Center. Data Delivery gives users the ability to create queries (One Time Requests) and
subscriptions to data sets (provided by the NOAA Operational Model Archive and Distribution System (NOMADS) data provider).
## Start and Stop
There are two different scripts to start the registry, and the script that gets executed depends on whether or not you are at the NCF (Central Registry), which runs the Crawler/Harvester, or an intermediary or node registry.
Start the registry for site:
/etc/init.d/edex_camel start registry
Start the registry for the NCF along with the Crawler/Harvester:
/etc/init.d/edex_camel start centralRegistry
## Registry Configuration
In operational use by the NWS, the Data Delivery federation Harvester is only run at the Central Registry. As a result, WFO's no longer need to configure the Harvester, and the NCF (Central Registry) handles the maintenance of the Crawler.
Data Delivery employs HTTPS secure transfers for registry-to-registry and some provider-to-registry communications. This means that Certificates for each registry node that directly connects to another registry node must be loaded into the trust store of each connecting node. This can be accomplished using a new utility located in the `/awips2/edex/conf/security` directory. The tool is called the `keystoreUtil.sh`.
Another configuration file of note new (starting 14.4.1) is the “security.properties”. It is
also located in the “/awips2/edex/conf/resources” directory but under the further
directories of “/site/${SITE}”
Where, ${SITE} is your local WFO/ClusterID. It is written by the “keystoreUtil.sh” and
is read by the running system to gather each federation nodes SSL credentials for
communicating with other nodes. Manual editing of this file should be unnecessary.
Example...
#The following configuration items are used with the wss4j in/out interceptors
