anchor.diff:  WARNING: Please make sure to use your appropriate values for the host and port.
   
   ==== Configuring Keycloak Authentication for the Gateway API
  -The API Gateway has a REST based configuration API which the API Manager uses when publishing APIs to 
  -it.  This API is protected by Keycloak authentication.  The configuration included in the apiman quickstart 
  -overlay ZIP assumes that the keycloak server is local, so you'll need to modify the *standalone-apiman.xml* 
  -file to point to the remote Keycloak 
  +The API Gateway has a REST based configuration API which the API Manager uses when publishing APIs to
  +it.  This API is protected by Keycloak authentication.  The configuration included in the apiman quickstart
  +overlay ZIP assumes that the Keycloak server is local, so you'll need to modify the *standalone-apiman.xml*
  +file to point to the remote Keycloak
   instance.
   
   Here is the relevant portion of the *standalone-apiman.xml* file that you must change:
  
positive.code: Change the value of that property to the appropriate dialect for your database.
  
  ==== Point the API Manager to the API Gateway
  Now that both your API Manager and API Gateway are running, you need to hook them up.  This just means 
  telling API Manager where the gateway lives.  There is an admin UI page in apiman that will let you do 
  this.  Simply navigate here:
  
  https://api-manager-host.org:8443/apimanui/api-manager/admin/gateways
  
negative.code: * Managing shared state across a cluster
  * Storing metrics to share with the API Manager  (analytics)
  
  In order to configure the gateway properly, you will need to configure the location of the Elasticsearch
  instance.  To do this, modify these properties in the *apiman.properties* file:
  
      apiman.es.protocol=http
  