anchor.diff:  
   What happens first is that the authentication policy is applied and a login dialog is then displayed:
   
  -![ExampleImage_35](images/35.png)
  +image::images/35.png[ExampleImage_35]
   
   Enter the username and password (user1/password) that we defined when we created the authentication policy to access the API. The fact that you are seeing this dialog confirms that you are accessing the managed API and are not accessing the API directly.
   
  
positive.code: 
  API Metrics can be accessed in the Management UI and through the REST API. The metrics are displayed visually in the Management UI, for example:
  
  ![Image_7](images/apiman_007.jpg)
  
  == Section 4 - Consuming APIs
  === Invoking Managed APIs
  From a client app’s perspective, the only difference between accessing a managed API and another API is the URL of the API’s endpoint. As we mentioned earlier in this crash course, a managed apiman endpoint takes this form:
  
  http://gatewayhostname:port/apiman-gateway/{organizationId}/{API ID}/{API version}/
  
  In addition, if the API is not Public, then the managed API endpoint must include a Client App’s API Key, either as a query parameter in the URL or as an HTTP header.  For example:
  
  http://localhost:8080/apiman-gateway/ACMEServices/echo/1.0?apikey=c374c202-d4b3-444206e3d +
  Don’t panic! You don’t have to memorize the endpoint string. As we’ll see in a bit, the endpoint string is provided to you by apiman.
  
  === Managing Client Applications and Contracts
  Public APIs can be consumed by any client. APIs that are not public can only be consumed by client applications that exist in an apiman organization and are registered with apiman.
  
negative.code: 
  This page will be displayed:
  
  image::images/3.png[ExampleImage_3]
  
  When you select the Administration Console selection, you will be prompted for the username and password:
  
  image::images/4a.png[ExampleImage_4a]
  
  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/4.png[ExampleImage_4]
  
  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/5.png[ExampleImage_5]
  
  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
  
  