Configuring DDF as a Fanout Proxy

Description

This scenario describes how to configure 

DDF

as a fanout proxy such that only queries and resource retrieval requests are processed and create/update/delete requests are rejected. Additionally, all queries are enterprise queries and no catalog provider needs to be configured.

Steps

1. Start 

   DDF

   following the Starting and Stopping instructions.
2. Reconfigure 

   DDF

   in fanout proxy mode by going to the Features tab in the Admin Console. The Standard Catalog Framework (catalog-core-standardframework feature) should be uninstalled first, then install the Catalog Fanout Framework App (catalog-core-fanoutframework feature), following the instructions in the Installing Features section of the Administrator's Guide.
   
   

   DDF

    is now operating as a fanout proxy. Only queries and resource retrieval requests will be allowed. All queries will be federated. Create, update, and delete requests will throw an UnsupportedOperationException, even if a Catalog Provider was configured previous to the reconfiguration to fanout.
   
   

3. Verify 

   DDF

   is in fanout configuration by going to the Services tab in the Admin Console. In the far right column labeled Bundle, there should be entries near the top called fanout-catalog-framework for the Catalog Framework, Event Processor, and Catalog Plugins, similar to what is depicted below. (Note that service IDs and Bundle IDs will vary.)
   Services in Admin Console for fanout

   Id      Type(s)                                      Bundle
   320     [ddf.catalog.CatalogFramework]               fanout-catalogframework (174)
   318     [ddf.catalog.event.EventProcessor]           fanout-catalogframework (174)
   316     [ddf.catalog.federation.FederationStrategy]  fanout-catalogframework (174)
   319     [ddf.catalog.federation.FederationStrategy]  fanout-catalogframework (174)
   317     [ddf.catalog.plugin.PostIngestPlugin]        fanout-catalogframework (174)