anchor.diff:  section of the User Guide for more information on this.
   
   
  -=== How To:  Use Elasticsearch instead of Infinispan in the API Gateway
  -The apiman quickstart ships by default with an Infinispan based provider for various
  -runtime components in the API Gateway.  This includes, for example, the Rate Limiter
  -component which is used to track limits across a potential cluster of API Gateway
  -nodes (ensuring that the limits are consistent and effective despite traffic being
  -split across API Gateway nodes in a cluster).
  -
  -The following components currently use Infinispan and can be switched to Elasticsearch:
  -
  -* API Gateway Registry (used to store the gateway configuration)
  -* Rate Limiter Component (used to track limits)
  -* Shared State Component (used by policies to share state across multiple requests)
  -
  -Each of these components can be configured separately.  So you can use Infinispan for
  -the last two but Elasticsearch for the first one, for example.
  +=== How To:  Use a standalone Elasticsearch instance/cluster instead of the quickstart instance
  +The apiman quickstart ships by default with an embedded instance of Elasticsearch.  This is
  +suitable for getting up and running quickly, but is not a good long term solution.  Instead,
  +users are encouraged to install a standalone instance of Elasticsearch and point apiman to it.
   
   ==== High Level Overview
   1. Download and install https://www.elastic.co/downloads/elasticsearch[Elasticsearch]
  -2. Make changes to "apiman.properties" to switch from JPA to Elasticsearch
  +2. Make changes to "apiman.properties" to point to your standalone Elasticsearch instance
   3. (Re)start apiman!
   
   ==== Download and install Elasticsearch
  
positive.code: * apiman rdbms datasource (h2)
  * pre-configured *admin* user with password *admin123!*
  * pre-configured h2 database for the API Manager (populated with default values)
  
  For this reason, there is no additional configuration required to run apiman.  Simply start up
  WildFly using the apiman configuration file:
  
  ....
  cd wildfly-8.2.0.Final
  ./bin/standalone.sh -c standalone-apiman.xml
  ....
  
  
negative.code: within the API Manager UI.  The registry contains just the configuration information necessary for
  the API Gateway to properly apply the appropriate policies to all inbound requests.
  
  Out of the box, the API Gateway is configured to use Elasticsearch to store the
  published/registered data.
  
  The configuration of the Registry can be found in the *apiman.properties* file.
  
  See section 4.2 for more information on modifying Elasticsearch settings.
  
  === API Gateway Rate Limiter
  Part of the running apiman system is a "Rate Limiter" component.  This component is used by
  apiman policies to enforce rate limits and uses Elasticsearch to store data.
  
  The configuration of the Rate Limiter component can be found in the *apiman.properties*
  file.
  
  See section 4.2 for more information on modifying Elasticsearch settings.
  
  === API Gateway Shared State
  Part of the running apiman system is a "Shared State" component.  This component is used by
  apiman policies to share interesting state information across multiple requests.  The
  shared state component uses Elasticsearch to store data.
  
  The configuration of the Shared State component can be found in the *apiman.properties*
  file.
  
  See section 4.2 for more information on modifying Elasticsearch settings.
  
  === Gateway API Authentication
  The Gateway's REST API is what the API Manager invokes when publishing services and applications
  