anchor.diff:  
   http://www.elastic.co/guide/en/elasticsearch/guide/master/getting-started.html
   
  -TIP: As of apiman 1.1.4.Final, an instance of Elasticsearch is included in the default
  -apiman distribution.  You may use it as your API Manager persistence store.  It is running
  -on port 19200.
  -
   ==== Make changes to "apiman.properties"
  -Once Elasticsearch is running smoothly, you must make some changes to the *apiman.properties*
  -file in order to tell apiman to use ES for the runtime components.
  -
  -First, it's often useful to set a common set of properties for the Elasticsearch
  -host, port, and cluster-name.  This way these properties can be re-used for the
  -configuration of each of the components.
  +Once Elasticsearch is running smoothly, you must make some minor changes to the *apiman.properties*
  +file in order to tell apiman where your Elasticsearch instance is located.
  +
  +There are a set of global properties used for all apiman components that use Elasticsearch to
  +load data.  These properties are:
   
   ----
  -apiman-gateway.es.host=
  -apiman-gateway.es.port=
  -apiman-gateway.es.cluster-name=
  +apiman.es.protocol=http
  +apiman.es.host=localhost
  +apiman.es.port=19200
  +apiman.es.username=
  +apiman.es.password=
   ----
   
  -Make sure you enter appropriate values for the apiman.es.host, apiman.es.port, and apiman.es.cluster-name
  -properties.  These values should reflect the settings of your Elasticsearch installation.
  -
  -Next, each of the components can be configured by changing/adding the following properties
  -in *apiman.properties*.  Make sure any of the properties below which already have values
  -are removed before the ones below are copied in.
  -
  -===== API Gateway Registry
  -Here is how you switch the API Gateway Registry over to Elasticsearch.
  -----
  -apiman-gateway.registry=io.apiman.gateway.engine.es.ESRegistry
  -apiman-gateway.registry.client.type=jest
  -apiman-gateway.registry.client.cluster-name=${apiman-gateway.es.cluster-name}
  -apiman-gateway.registry.client.host=${apiman-gateway.es.host}
  -apiman-gateway.registry.client.port=${apiman-gateway.es.port}
  -----
  -
  -===== Rate Limiter Component
  -Here is how you switch the Rate Limiter Component over to Elasticsearch.
  -----
  -apiman-gateway.components.IRateLimiterComponent=io.apiman.gateway.engine.es.ESRateLimiterComponent
  -apiman-gateway.components.IRateLimiterComponent.client.type=jest
  -apiman-gateway.components.IRateLimiterComponent.client.cluster-name=${apiman-gateway.es.cluster-name}
  -apiman-gateway.components.IRateLimiterComponent.client.host=${apiman-gateway.es.host}
  -apiman-gateway.components.IRateLimiterComponent.client.port=${apiman-gateway.es.port}
  -----
  -
  -===== Shared State Component
  -Here is how you switch the Shared State Component over to Elasticsearch.
  -----
  -apiman-gateway.components.ISharedStateComponent=io.apiman.gateway.engine.es.ESSharedStateComponent
  -apiman-gateway.components.ISharedStateComponent.client.type=jest
  -apiman-gateway.components.ISharedStateComponent.client.cluster-name=${apiman-gateway.es.cluster-name}
  -apiman-gateway.components.ISharedStateComponent.client.host=${apiman-gateway.es.host}
  -apiman-gateway.components.ISharedStateComponent.client.port=${apiman-gateway.es.port}
  -----
  +Make sure you enter appropriate values for this properties - they should reflect the settings 
  +of your Elasticsearch installation.
   
   ==== (Re)start apiman
   If apiman was running, you should stop it now.  Once everything is shutdown, and the changes
  
positive.code: 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.
  
  ==== 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
  3. (Re)start apiman!
  
  ==== Download and install Elasticsearch
  
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
  