anchor.diff:  
   So far so good. Now, send 10 more requests and you will see a response that looks like this as the gold plan rate limit is exceeded:
   
  -----
  -{"type":"Other","failureCode":10005,"responseCode":429,"message":"Rate limit exceeded.","headers":{"entries":[{"X-RateLimit-Remaining":"-1"},{"X-RateLimit-Reset":"50904"},{"X-RateLimit-Limit":"10"}],"empty":false}}
  +[source, json]
  +----
  +{
  +   "type" : "Other",
  +   "headers" : {
  +      "empty" : false,
  +      "entries" : [
  +         {
  +            "X-RateLimit-Remaining" : "-1"
  +         },
  +         {
  +            "X-RateLimit-Reset" : "50904"
  +         },
  +         {
  +            "X-RateLimit-Limit" : "10"
  +         }
  +      ]
  +   },
  +   "failureCode" : 10005,
  +   "message" : "Rate limit exceeded.",
  +   "responseCode" : 429
  +}
   ----
   
   And there it is. Your gold plan has been exceeded. Maybe next time you’ll spend a little more and get the platinum plan!  ;-)
  
positive.code: 
  Remember the URL that we used to access the unmanaged API directly? Well, forget it. In order to access the managed API through the API Gateway acting as a proxy for other API we have to obtain the managed API's URL. In the API Manager UI, header over to the “APIs” tab for the application, select the API and then click select on the “i” character to the right of the API name. This will expose the API Key and the API’s HTTP endpoint in the API Gateway:
  
  image::images/33.png[ExampleImage_33]
  
  image::images/34.png[ExampleImage_34]
  
  In order to be able access the API through the API Gateway, we have to provide the API Key with each request.  combine the API Key and HTTP endpoint. The API Key can be provided either through an HTTP Header (X-API-Key) or a URL query parameter.
  
  
negative.code: 
  This page will be displayed:
  
  image::images/example/3.png[WildFly welcome page]
  
  When you select the Administration Console selection, you will be prompted for the username and password:
  
  image::images/example/4a.png[Prompting for credentials]
  
  Enter the username and password for the user that you defined (for this example, we used the very unimaginative and insecure username “admin”) and you will brought to the WildFly Server Administration Console:
  
  image::images/example/4.png[WildFly administration console]
  
  If you then select the “Deployments” tab at the top of the page, you’ll see the applications deployed to the server. This is where you should see the apiman deployments for the APIs, Gateway, and Management UI:
  
  image::images/example/5.png[WildFly deployments tab]
  
  If you don’t see the apiman deployments, don’t panic, but something went wrong with the installation. The most common reason for the apiman deployments to be missing is that you unzipped the apiman overlay .zip file into a different directory from the WildFly server. Remember, that the reason that the overlay file is named “overlay” is that it must be unzipped over an installed WildFly server. You can confirm that this is what happened by looking in the WildFly server’s deployment directory here:  wildfly-10.0.0.Final/standalone/deployments
  
  