diff --git a/_blog-src/Gemfile b/_blog-src/Gemfile
index e8cbba4c2..31bb5c545 100644
--- a/_blog-src/Gemfile
+++ b/_blog-src/Gemfile
@@ -5,3 +5,4 @@ gem "asciidoctor", "1.5.2"
 gem "jekyll-asciidoc", "1.0.0"
 gem "asciidoctor-diagram", "1.3.0.preview.4"
 gem "coderay"
+gem "jekyll-sitemap", "0.9.0"
diff --git a/_blog-src/Gemfile.lock b/_blog-src/Gemfile.lock
index 0bdc27c96..a1e2a8a55 100644
--- a/_blog-src/Gemfile.lock
+++ b/_blog-src/Gemfile.lock
@@ -42,6 +42,7 @@ GEM
     jekyll-paginate (1.1.0)
     jekyll-sass-converter (1.3.0)
       sass (~> 3.2)
+    jekyll-sitemap (0.9.0)
     jekyll-watch (1.2.1)
       listen (~> 2.7)
     kramdown (1.7.0)
@@ -78,3 +79,7 @@ DEPENDENCIES
   coderay
   jekyll (= 2.5.3)
   jekyll-asciidoc (= 1.0.0)
+  jekyll-sitemap (= 0.9.0)
+
+BUNDLED WITH
+   1.11.2
diff --git a/_blog-src/_config.yml b/_blog-src/_config.yml
index d45a712b7..be3af552c 100644
--- a/_blog-src/_config.yml
+++ b/_blog-src/_config.yml
@@ -1,5 +1,5 @@
 # Site settings
-title: apiman blog
+title: apiman Blog | Open Source API Management
 email: apiman-user@lists.jboss.org
 description: > # this means to ignore newlines until "baseurl:"
   The apiman project brings an open source development methodology to
@@ -22,6 +22,7 @@ destination: ../blog
 excerpt_separator: <!--more-->
 
 gems:
+  - jekyll-sitemap
   - jekyll-asciidoc
   - asciidoctor-diagram
 
diff --git a/_blog-src/_includes/footer.html b/_blog-src/_includes/footer.html
index 9643e4313..99251da07 100644
--- a/_blog-src/_includes/footer.html
+++ b/_blog-src/_includes/footer.html
@@ -6,13 +6,13 @@
                 <div class="textwidget">
                     <p>
                         Copyright &copy; 2016 Red Hat, Inc. All rights reserved.<br>
-                        apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License, v2.0</a>.<br> 
+                        apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="nofollow" target="_blank">Apache License, v2.0</a>.<br>
                         <a href="disclosure.html">Open Source Disclosure</a>
                     </p>
                 </div>
             </div>
             <div class="widget col-sm-6 col-md-6 widget_text" style="text-align: right">
-                <a href="http://www.redhat.com"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png"></a>
+                <a href="http://www.redhat.com" rel="nofollow" target="_blank"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png" alt="Red Hat"></a>
             </div>
         </div>
         <nav class="clearfix"></nav>
diff --git a/_blog-src/_includes/head.html b/_blog-src/_includes/head.html
index 21bc91bce..cc529043b 100644
--- a/_blog-src/_includes/head.html
+++ b/_blog-src/_includes/head.html
@@ -2,8 +2,9 @@
   <meta charset="utf-8">
   <meta http-equiv="X-UA-Compatible" content="IE=edge">
   <meta name="viewport" content="width=device-width, initial-scale=1">
+    <meta name="msvalidate.01" content="C3BF2C67B92C75F2DEAA096973652038" />
   <link rel="shortcut icon" href="http://www.apiman.io/latest/resources/images/favicon.ico">
-  <title>{% if page.title %}{{ page.title }}{% else %}{{ site.title }}{% endif %}</title>
+  <title>{% if page.title %}{{ page.title }} | apiman Open Source API Management{% else %}{{ site.title }}{% endif %}</title>
   <meta name="description" content="{% if page.excerpt %}{{ page.excerpt | strip_html | strip_newlines | truncate: 160 }}{% else %}{{ site.description }}{% endif %}">
 
   <link href="http://www.apiman.io/latest/resources/bootstrap-3.3.0/css/bootstrap.min.css" rel="stylesheet">
diff --git a/_blog-src/_includes/header.html b/_blog-src/_includes/header.html
index 818aa9cb4..f362598c6 100644
--- a/_blog-src/_includes/header.html
+++ b/_blog-src/_includes/header.html
@@ -16,7 +16,7 @@
         <li class="top-menu-item menu-item"><a href="http://www.apiman.io/latest/roadmap.html">Roadmap</a></li>
         <li class="top-menu-item menu-item active"><a href="http://www.apiman.io/blog/">Blog</a></li>
         <li class="top-menu-item menu-item dropdown">
-            <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Get Involved<b class="caret"></b></a>
+            <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Get Involved<b class="caret"></b></a>
             <ul class="dropdown-menu">
                 <li class="menu-item">
                     <a href="https://issues.jboss.org/browse/APIMAN">Report a Bug</a>
@@ -25,10 +25,10 @@
                     <a href="http://www.apiman.io/latest/chat.html">Chat on IRC</a>
                 </li>
                 <li class="menu-item">
-                    <a href="https://twitter.com/apiman_io">Twitter Feed</a>
+                    <a href="https://twitter.com/apiman_io" rel="nofollow" target="_blank">Twitter Feed</a>
                 </li>
                 <li class="menu-item">
-                    <a href="https://lists.jboss.org/mailman/listinfo/apiman-user">Mailing List</a>
+                    <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="nofollow" target="_blank">Mailing List</a>
                 </li>
                 <li class="divider"></li>
                 <li class="menu-item">
@@ -37,7 +37,7 @@
             </ul>
         </li>
         <li class="top-menu-item menu-item dropdown">
-            <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Learn More<b class="caret"></b></a>
+            <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Learn More<b class="caret"></b></a>
             <ul class="dropdown-menu">
                 <li class="menu-item">
                     <a href="http://www.apiman.io/latest/tutorials.html">Tutorials &amp; Walkthroughs</a>
diff --git a/_blog-src/_layouts/default.html b/_blog-src/_layouts/default.html
index d55228e51..9f822b405 100644
--- a/_blog-src/_layouts/default.html
+++ b/_blog-src/_layouts/default.html
@@ -3,8 +3,8 @@
   {% include head.html %}
   <body class="blog">
     <div id="rhbar">
-      <a class="jbdevlogo" href="http://www.jboss.org/projects/about"></a>
-      <a class="rhlogo" href="http://www.redhat.com/"></a>
+      <a class="jbdevlogo" href="http://www.jboss.org/projects/about" rel="nofollow" target="_blank"></a>
+      <a class="rhlogo" href="http://www.redhat.com/" rel="nofollow" target="_blank"></a>
     </div>
     {% include header.html %}
 
diff --git a/_blog-src/_posts/2016-01-11-release-1.2.markdown b/_blog-src/_posts/2016-01-11-release-1.2.markdown
index 38e5936c4..871e87788 100644
--- a/_blog-src/_posts/2016-01-11-release-1.2.markdown
+++ b/_blog-src/_posts/2016-01-11-release-1.2.markdown
@@ -1,6 +1,6 @@
 ---
 layout: post
-title:  "Finall!  Apiman 1.2.0.Final is released!"
+title:  "Final!  Apiman 1.2.0.Final is released!"
 date:   2016-01-11 09:30:00
 author: eric_wittmann
 categories: apiman
diff --git a/index.html b/index.html
index 70e0e11f2..8840ef3b7 100644
--- a/index.html
+++ b/index.html
@@ -1,6 +1,6 @@
 <html> 
   <head>
-    <title>apiman</title>
+    <title>apiman | Open Source API Management</title>
     <META http-equiv="refresh" content="0;URL=latest"> 
   </head> 
   <body bgcolor="#ffffff"> 
diff --git a/latest/api-manager-restdocs.html b/latest/api-manager-restdocs.html
index 9de010958..b52d55777 100644
--- a/latest/api-manager-restdocs.html
+++ b/latest/api-manager-restdocs.html
@@ -5,7 +5,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge">
     <meta name="viewport" content="width=device-width, initial-scale=1">
     <link rel="shortcut icon" href="resources/images/favicon.ico">
-    <title>apiman :: API Manager REST Services</title>
+    <title>API Manager REST Services Docs | apiman Open Source API Management</title>
 
     <link href="resources/bootstrap-3.3.0/css/bootstrap.min.css" rel="stylesheet">
     <link href="resources/patternfly-1.0.5/css/patternfly.min.css" rel="stylesheet">
@@ -43,8 +43,8 @@
   </head>
   <body class="">
     <div id="rhbar">
-      <a class="jbdevlogo" href="http://www.jboss.org/projects/about"></a>
-      <a class="rhlogo" href="http://www.redhat.com/"></a>
+      <a class="jbdevlogo" href="http://www.jboss.org/projects/about" rel="nofollow" target="_blank"></a>
+      <a class="rhlogo" href="http://www.redhat.com/" rel="nofollow" target="_blank"></a>
     </div>
     <nav id="top-nav" class="navbar navbar-inverse" role="navigation">
       <div class="container">
@@ -67,16 +67,16 @@
                 <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Get Involved<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
-                        <a href="https://issues.jboss.org/browse/APIMAN">Report a Bug</a>
+                        <a href="https://issues.jboss.org/browse/APIMAN" rel="nofollow" target="_blank">Report a Bug</a>
                     </li>
                     <li class="menu-item">
                         <a href="chat.html">Chat on IRC</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://twitter.com/apiman_io">Twitter Feed</a>
+                        <a href="https://twitter.com/apiman_io" rel="nofollow" target="_blank">Twitter Feed</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user">Mailing List</a>
+                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="nofollow" target="_blank">Mailing List</a>
                     </li>
                     <li class="divider"></li>
                     <li class="menu-item">
@@ -85,7 +85,7 @@
                 </ul>
             </li>
             <li class="top-menu-item menu-item dropdown active">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Learn More<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Learn More<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
                         <a href="tutorials.html">Tutorials &amp; Walkthroughs</a>
@@ -139,14 +139,14 @@
                         <div class="textwidget">
                             <p>
                                 Copyright © 2015 Red Hat, Inc. All rights reserved.<br>
-                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License, v2.0</a>.<br> 
+                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="nofollow" target="_blank">Apache License, v2.0</a>.<br>
                                 <a href="disclosure.html">Open Source Disclosure</a>
                             </p>
                         </div>
                     </div>
                     <div class="widget col-sm-6 col-md-6 widget_text" style="text-align: right">
                         
-                        <a href="http://www.redhat.com"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png"></a>
+                        <a href="http://www.redhat.com" rel="nofollow" target="_blank"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png" alt="Red Hat"></a>
                     </div>
                 </div>
                 <nav class="clearfix"></nav>
diff --git a/latest/apidoc/manager/index.html b/latest/apidoc/manager/index.html
index 9bae910bb..b1d9626a6 100644
--- a/latest/apidoc/manager/index.html
+++ b/latest/apidoc/manager/index.html
@@ -8,25 +8,24 @@
 
     <title ng-bind-template="{{projectTitle}}"></title>
 
-<link type="text/css" rel="stylesheet" href="css/normalize.css" />
-<link type="text/css" rel="stylesheet" href="lib/angular-ui/css/angular-ui.css" />
-<link type="text/css" rel="stylesheet" href="css/bootstrap-combined.min.css" />
-<link type="text/css" rel="stylesheet" href="css/fonts.css" />
-<link type="text/css" rel="stylesheet" href="css/style.css" />
-<link type="text/css" rel="stylesheet" href="css/introstyle.css" />
-<link type="text/css" rel="stylesheet" href="lib/font-awesome/css/font-awesome.css" />
-<script type="text/javascript" src="lib/jquery/js/jquery.js"></script>
-<script type="text/javascript" src="lib/angular/js/angular.js"></script>
-<script type="text/javascript" src="lib/angular-bootstrap/js/ui-bootstrap.js"></script>
-<script type="text/javascript" src="lib/angular-sanitize/js/angular-sanitize.js"></script>
-<script type="text/javascript" src="lib/angular-ui/js/angular-ui.js"></script>
-<script type="text/javascript" src="lib/bootstrap/js/bootstrap.js"></script>
-<script type="text/javascript" src="lib/underscore/js/underscore.js"></script>
-<script type="text/javascript" src="lib/lunr/js/lunr.js"></script>
-<script type="text/javascript" src="js/output.js"></script>
+    <link type="text/css" rel="stylesheet" href="css/normalize.css"/>
+    <link type="text/css" rel="stylesheet" href="lib/angular-ui/css/angular-ui.css"/>
+    <link type="text/css" rel="stylesheet" href="css/bootstrap-combined.min.css"/>
+    <link type="text/css" rel="stylesheet" href="css/fonts.css"/>
+    <link type="text/css" rel="stylesheet" href="css/style.css"/>
+    <link type="text/css" rel="stylesheet" href="css/introstyle.css"/>
+    <link type="text/css" rel="stylesheet" href="lib/font-awesome/css/font-awesome.css"/>
+    <script type="text/javascript" src="lib/jquery/js/jquery.js"></script>
+    <script type="text/javascript" src="lib/angular/js/angular.js"></script>
+    <script type="text/javascript" src="lib/angular-bootstrap/js/ui-bootstrap.js"></script>
+    <script type="text/javascript" src="lib/angular-sanitize/js/angular-sanitize.js"></script>
+    <script type="text/javascript" src="lib/angular-ui/js/angular-ui.js"></script>
+    <script type="text/javascript" src="lib/bootstrap/js/bootstrap.js"></script>
+    <script type="text/javascript" src="lib/underscore/js/underscore.js"></script>
+    <script type="text/javascript" src="lib/lunr/js/lunr.js"></script>
+    <script type="text/javascript" src="js/output.js"></script>
     <!--[if IE 7]>
-    <link rel="stylesheet" href="lib/font-awesome/css/font-awesome-ie7.min.css">
-    <![endif]-->
+    <link rel="stylesheet" href="lib/font-awesome/css/font-awesome-ie7.min.css"><![endif]-->
 
     <style>
         [ng-cloak] {
@@ -45,29 +44,29 @@
              (c) 2010-2014 Google, Inc. http://angularjs.org
              License: MIT
              */
-            (function () {
+            (function() {
                 'use strict';
                 function d(a) {
-                    return function () {
+                    return function() {
                         var c = arguments[0], b, c = "[" + (a ? a + ":" : "") + c + "] http://errors.angularjs.org/1.2.6/" + (a ? a + "/" : "") + c;
                         for (b = 1; b < arguments.length; b++)c = c + (1 == b ? "?" : "&") + "p" + (b - 1) + "=" + encodeURIComponent("function" == typeof arguments[b] ? arguments[b].toString().replace(/ \{[\s\S]*$/, "") : "undefined" == typeof arguments[b] ? "undefined" : "string" != typeof arguments[b] ? JSON.stringify(arguments[b]) : arguments[b]);
                         return Error(c)
                     }
                 }
 
-                (function (a) {
+                (function(a) {
                     var c = d("$injector"), b = d("ng");
                     a = a.angular ||
-                    (a.angular = {});
+                            (a.angular = {});
                     a.$$minErr = a.$$minErr || d;
-                    return a.module || (a.module = function () {
+                    return a.module || (a.module = function() {
                                 var a = {};
-                                return function (e, d, f) {
+                                return function(e, d, f) {
                                     if ("hasOwnProperty" === e)throw b("badname", "module");
                                     d && a.hasOwnProperty(e) && (a[e] = null);
-                                    return a[e] || (a[e] = function () {
+                                    return a[e] || (a[e] = function() {
                                                 function a(c, d, e) {
-                                                    return function () {
+                                                    return function() {
                                                         b[e || "push"]([c, d, arguments]);
                                                         return g
                                                     }
@@ -90,7 +89,7 @@
                                                     controller: a("$controllerProvider", "register"),
                                                     directive: a("$compileProvider", "directive"),
                                                     config: k,
-                                                    run: function (a) {
+                                                    run: function(a) {
                                                         h.push(a);
                                                         return this
                                                     }
@@ -110,16 +109,16 @@
              * (c) Dustin Diaz 2013
              * License: MIT
              */
-            (function (e, t, n) {
+            (function(e, t, n) {
                 typeof module != "undefined" && module.exports ? module.exports = n() : typeof define == "function" && define.amd ? define(n) : t[e] = n()
-            })("$script", this, function () {
+            })("$script", this, function() {
                 function v(e, t) {
                     for (var n = 0, r = e.length; n < r; ++n)if (!t(e[n]))return f;
                     return 1
                 }
 
                 function m(e, t) {
-                    v(e, function (e) {
+                    v(e, function(e) {
                         return !t(e)
                     })
                 }
@@ -138,8 +137,8 @@
 
                     e = e[l] ? e : [e];
                     var f = t && t.call, c = f ? t : a, h = f ? e.join("") : t, p = e.length;
-                    return setTimeout(function () {
-                        m(e, function (e) {
+                    return setTimeout(function() {
+                        m(e, function(e) {
                             if (e === null)return b();
                             if (u[e])return h && (i[h] = 1), u[e] == 2 && b();
                             u[e] = 1, h && (i[h] = 1), y(!n.test(e) && o ? o + e + ".js" : e, b)
@@ -149,7 +148,7 @@
 
                 function y(n, r) {
                     var i = e.createElement("script"), s = f;
-                    i.onload = i.onerror = i[d] = function () {
+                    i.onload = i.onerror = i[d] = function() {
                         if (i[h] && !/^c|loade/.test(i[h]) || s)return;
                         i.onload = i[d] = null, s = 1, u[n] = 2, r()
                     }, i.async = 1, i.src = n, t.insertBefore(i, t.firstChild)
@@ -158,34 +157,34 @@
                 var e = document, t = e.getElementsByTagName("head")[0], n = /^https?:\/\//, r = {}, i = {}, s = {}, o, u = {}, a = "string", f = !1, l = "push", c = "DOMContentLoaded", h = "readyState", p = "addEventListener", d = "onreadystatechange";
                 return !e[h] && e[p] && (e[p](c, function b() {
                     e.removeEventListener(c, b, f), e[h] = "complete"
-                }, f), e[h] = "loading"), g.get = y, g.order = function (e, t, n) {
+                }, f), e[h] = "loading"), g.get = y, g.order = function(e, t, n) {
                     (function r(i) {
                         i = e.shift(), e.length ? g(i, r) : g(i, t, n)
                     })()
-                }, g.path = function (e) {
+                }, g.path = function(e) {
                     o = e
-                }, g.ready = function (e, t, n) {
+                }, g.ready = function(e, t, n) {
                     e = e[l] ? e : [e];
                     var i = [];
-                    return !m(e, function (e) {
+                    return !m(e, function(e) {
                         r[e] || i[l](e)
-                    }) && v(e, function (e) {
+                    }) && v(e, function(e) {
                         return r[e]
-                    }) ? t() : !function (e) {
+                    }) ? t() : !function(e) {
                         s[e] = s[e] || [], s[e][l](t), n && n(i)
                     }(e.join("|")), g
-                }, g.done = function (e) {
+                }, g.done = function(e) {
                     g([null], e)
                 }, g
             })
             // wait until input script is loaded
             $script([
                 'input/input.js'
-            ], function () {
+            ], function() {
                 // when all is done, execute bootstrap angular application
-                angular.element(document).ready(function () {
+                angular.element(document).ready(function() {
                     //give browser a chance to render the loading message
-                    setTimeout(function () {
+                    setTimeout(function() {
                         angular.bootstrap(document, ['miredot']);
                     }, 250);
                 });
@@ -265,31 +264,24 @@
                 <div ng-show="navigationView == 'search'">
                     <div id="searchform">
                         <form>
-                            <label for="keywordInput" class="searchLabel">
-                                URL contains...
-                            </label>
-                            <input id="keywordInput" type="text" class="input-medium search-query searchInput"
-                                   style="margin-bottom: 15px"
-                                   ng-model="searchQuery.url">
-
-                            <label for="urlInput" class="searchLabel">
-                                URL matches...
-                            </label>
-                            <input id="urlInput" type="text" class="input-medium search-query searchInput"
-                                   style="display: block; margin-bottom: 15px"
-                                   placeholder="{{baseUrl.value + '...' }}"
-                                   ng-model="searchByExample">
-
-                            <label for="fullTextSearch" class="searchLabel">
-                                Full text search
-                            </label>
-                            <input id="fullTextSearch" type="text" class="input-medium search-query searchInput"
-                                   style="margin-bottom: 15px"
-                                   ng-change="doFullTextSearch()" ng-model="fullTextSearch">
-
-                            <label class="searchLabel">
-                                Http method
-                            </label>
+                            <label for="keywordInput" class="searchLabel"> URL contains... </label> <input
+                                id="keywordInput" type="text" class="input-medium search-query searchInput"
+                                style="margin-bottom: 15px"
+                                ng-model="searchQuery.url">
+
+                            <label for="urlInput" class="searchLabel"> URL matches... </label> <input id="urlInput"
+                                                                                                      type="text"
+                                                                                                      class="input-medium search-query searchInput"
+                                                                                                      style="display: block; margin-bottom: 15px"
+                                                                                                      placeholder="{{baseUrl.value + '...' }}"
+                                                                                                      ng-model="searchByExample">
+
+                            <label for="fullTextSearch" class="searchLabel"> Full text search </label> <input
+                                id="fullTextSearch" type="text" class="input-medium search-query searchInput"
+                                style="margin-bottom: 15px"
+                                ng-change="doFullTextSearch()" ng-model="fullTextSearch">
+
+                            <label class="searchLabel"> Http method </label>
 
                             <div class="tagInput">
                                 <span ng-repeat="method in httpMethods" set-text="method"
@@ -298,9 +290,7 @@
                                       ng-click="toggleSearchQueryHttp(method)"></span>
                             </div>
 
-                            <label class="searchLabel" set-if="serviceTags.length > 0">
-                                Tags
-                            </label>
+                            <label class="searchLabel" set-if="serviceTags.length > 0"> Tags </label>
 
                             <div class="tagInput">
                                 <div class="tag"
@@ -308,8 +298,8 @@
                                      ng-click="tag.selected = ! tag.selected"
                                      ng-class="{tagSelected: tag.selected}">
                                     <i class="icon-circle"
-                                       style="color: #eee; text-shadow: 0 0 -1px rgba(0,0,0,0.3);"></i>
-                                    <span set-text="'&nbsp;' + tag.name"></span>
+                                       style="color: #eee; text-shadow: 0 0 -1px rgba(0,0,0,0.3);"></i> <span
+                                        set-text="'&nbsp;' + tag.name"></span>
                                 </div>
                             </div>
                         </form>
@@ -328,8 +318,7 @@
                                             <span class="httpMethod small" set-class="interface.http"
                                                   set-text="interface.http"></span>
                                         </div>
-                                        <span set-text="interface.url" class="result"></span>
-                                    </a>
+                                        <span set-text="interface.url" class="result"></span> </a>
                                 </div>
                             </li>
                         </ul>
@@ -352,9 +341,8 @@
                                 <!--<a href="#interfaces" target="_self" ng-class="{activeView: view=='interfaces'}">Interfaces</a>-->
                                 <!--</li>-->
                                 <li set-if="processErrors.length > 0 || projectWarnings.length > 0">
-                                    <a href="#home" target="_self" ng-class="{hidden: view!='warnings'}">
-                                        <span class="icon-circle-arrow-left"></span> Back
-                                    </a>
+                                    <a href="#home" target="_self" ng-class="{hidden: view!='warnings'}"> <span
+                                            class="icon-circle-arrow-left"></span> Back </a>
                                 </li>
                                 <li set-if="processErrors.length > 0 || projectWarnings.length > 0">
                                     <a href="#warnings" target="_self"
@@ -365,7 +353,7 @@
 
                             <div class="pull-right" style="margin-right: 20px;"
                                  ng-if="licenseType == 'FREE' || !hideLogoOnTop">
-                                <a href="http://www.miredot.com" target="_blank"><img src="img/miredot_mini_title.png"></a>
+                                <a href="http://www.miredot.com"  rel="nofollow" target="_blank"><img src="img/miredot_mini_title.png" alt="Miredot"></a>
                                 <i class="icon-exclamation-sign failedIcon"
                                    set-if="!validLicense && !!licenseErrorMessage" set-title="licenseErrorMessage"></i>
                             </div>
@@ -375,14 +363,13 @@
                     <div class="row">
                         <div class="col-lg-12">
                             <div class="notice freeversion" set-if="validLicense && licenseType == 'FREE'">
-                                <i class="icon-info-sign" title="Free version"></i>
-                                Notice: This documentation was generated by the free version of MireDot.
-                                As such, not all features are supported.
-                                <span set-html="visitWebsiteForProVersion"></span>
+                                <i class="icon-info-sign" title="Free version"></i> Notice: This documentation was
+                                generated by the free version of MireDot. As such, not all features are supported. <span
+                                    set-html="visitWebsiteForProVersion"></span>
                             </div>
                             <div class="notice invalidlicense" set-if="!validLicense">
-                                <i class="icon-exclamation-sign" title="Invalid key"></i>
-                                <span set-html="licenseErrorMessage"></span>
+                                <i class="icon-exclamation-sign" title="Invalid key"></i> <span
+                                    set-html="licenseErrorMessage"></span>
                             </div>
                         </div>
                     </div>
@@ -430,8 +417,8 @@
                                         <div class="tag" ng-repeat="tag in interface.tags | arraySort"
                                              ng-class="{tagSelected: isServiceTagSelected(tag)}">
                                             <i class="icon-circle"
-                                               style="color: #eee; text-shadow: 0 0 -1px rgba(0,0,0,0.3);"></i>
-                                            <span set-text="'&nbsp;' + tag"></span>
+                                               style="color: #eee; text-shadow: 0 0 -1px rgba(0,0,0,0.3);"></i> <span
+                                                set-text="'&nbsp;' + tag"></span>
                                         </div>
                                     </div>
 
@@ -459,7 +446,7 @@
                                         focus-when="editingBaseUrl == true"
                                         on-blur="editingBaseUrl = false"
                                         on-enter="editingBaseUrl = false"
-                                        /><!--
+                                /><!--
                                  --><span class="methodUrl" set-html="interface.url | formatUrlParams"></span>
                                 </div>
 
@@ -477,8 +464,8 @@
                                             </div>
                                             <div class="rolesWrapper">
                                                 <span class="icon-male" style="position: relative;"
-                                                      title="Roles allowed"></span>&nbsp;&nbsp;
-                                                <span ng-repeat-start="role in interface.rolesAllowed" ng-repeat-end>{{role}}{{$last ? '' : ', '}}</span>
+                                                      title="Roles allowed"></span>&nbsp;&nbsp; <span
+                                                    ng-repeat-start="role in interface.rolesAllowed" ng-repeat-end>{{role}}{{$last ? '' : ', '}}</span>
                                             </div>
                                         </div>
                                     </div>
@@ -524,8 +511,8 @@ <h4>Body</h4>
                                                 <div class="mediaTypeContainer">
                                                     <div class="mediaType">
                                                         <span set-if="interface.consumes.length > 0"
-                                                              set-text="interface.consumes"></span>
-                                                        <span set-if="interface.consumes.length == 0">no type</span>
+                                                              set-text="interface.consumes"></span> <span
+                                                            set-if="interface.consumes.length == 0">no type</span>
                                                     </div>
                                                 </div>
                                                 <div set-if="interface.compressed" class="gzip"></div>
@@ -564,7 +551,8 @@ <h4>Returns</h4>
                                                     <tr ng-repeat="responseHeader in interface.responseHeaders.headers">
                                                         <td>
                                                             <span class="parameterContainer">
-                                                                <span class="parameterName" set-text="responseHeader.fieldName"></span>
+                                                                <span class="parameterName"
+                                                                      set-text="responseHeader.fieldName"></span>
                                                             </span>
                                                         </td>
                                                         <td>
@@ -575,7 +563,8 @@ <h4>Returns</h4>
                                                     <tr ng-repeat="responseHeader in interface.responseHeaders.customHeaders">
                                                         <td>
                                                             <span class="parameterContainer">
-                                                                <span class="parameterName" set-text="responseHeader.fieldName"></span>
+                                                                <span class="parameterName"
+                                                                      set-text="responseHeader.fieldName"></span>
                                                             </span>
                                                         </td>
                                                         <td>
@@ -592,8 +581,8 @@ <h4>Returns</h4>
                                                 <div class="mediaTypeContainer">
                                                     <div class="mediaType">
                                                         <span set-if="interface.produces.length > 0"
-                                                              set-text="interface.produces"></span>
-                                                        <span set-if="interface.produces.length == 0">no type</span>
+                                                              set-text="interface.produces"></span> <span
+                                                            set-if="interface.produces.length == 0">no type</span>
                                                     </div>
                                                 </div>
                                                 <div set-if="interface.compressed" class="gzip"></div>
@@ -618,13 +607,15 @@ <h4>Returns</h4>
                                         </div>
                                     </div>
 
-                                    <div class="httpHeaderContainer" set-if="interface.responseHttpHeaders.length > 0 || interface.responseCustomHeaders.length > 0">
+                                    <div class="httpHeaderContainer"
+                                         set-if="interface.responseHttpHeaders.length > 0 || interface.responseCustomHeaders.length > 0">
                                         <h4>Response Headers</h4>
                                         <table class="methodParams">
                                             <tr ng-repeat="responseHeader in interface.responseHttpHeaders">
                                                 <td>
                                                     <span class="parameterContainer">
-                                                        <span class="parameterName" set-text="responseHeader.fieldName"></span>
+                                                        <span class="parameterName"
+                                                              set-text="responseHeader.fieldName"></span>
                                                     </span>
                                                 </td>
                                                 <td>
@@ -635,7 +626,8 @@ <h4>Response Headers</h4>
                                             <tr ng-repeat="responseHeader in interface.responseCustomHeaders">
                                                 <td>
                                                     <span class="parameterContainer">
-                                                        <span class="parameterName" set-text="responseHeader.fieldName"></span>
+                                                        <span class="parameterName"
+                                                              set-text="responseHeader.fieldName"></span>
                                                     </span>
                                                 </td>
                                                 <td>
@@ -657,7 +649,8 @@ <h4>Status codes</h4>
                                                                      class3xx: statusCode.httpCode >= 300 && statusCode.httpCode < 400,
                                                                      class4xx: statusCode.httpCode >= 400 && statusCode.httpCode < 500,
                                                                      class5xx: statusCode.httpCode >= 500">
-                                                        <span class="parameterName statusCode" set-text="statusCode.httpCode">
+                                                        <span class="parameterName statusCode"
+                                                              set-text="statusCode.httpCode">
                                                         </span>
                                                         <span class="parameterName statusCodeDescription"
                                                               set-text="statusCodes[statusCode.httpCode]">
@@ -695,21 +688,18 @@ <h3>
 
                                     <p>
                                         MireDot believes that the Java methods below correspond to REST interfaces, but
-                                        somehow had problems
-                                        parsing/processing these interfaces and therefore excluded them from the
-                                        generated documentation. We
-                                        would very much appreciate it if you would
-                                        <a href="mailto:&#109;&#105;&#114;&#101;&#100;&#111;&#116;&#64;&#113;&#109;&#105;&#110;&#111;&#46;&#99;&#111;&#109;">send
-                                            us</a>
-                                        the interfaces (not the implementations) and the
-                                        types used (returntype, parameters). This will allow us to further improve
-                                        MireDot and better document
+                                        somehow had problems parsing/processing these interfaces and therefore excluded
+                                        them from the generated documentation. We would very much appreciate it if you
+                                        would <a
+                                            href="mailto:&#109;&#105;&#114;&#101;&#100;&#111;&#116;&#64;&#113;&#109;&#105;&#110;&#111;&#46;&#99;&#111;&#109;">send
+                                        us</a> the interfaces (not the implementations) and the types used (returntype,
+                                        parameters). This will allow us to further improve MireDot and better document
                                         your interfaces in the future.
                                     </p>
                                     <ul class="warningsListContent">
                                         <li ng-repeat="processError in processErrors">
-                                            <i class="icon-question-sign" title="Not Documented"></i>
-                                            <span set-text="processError.class + '.' + processError.method"></span>
+                                            <i class="icon-question-sign" title="Not Documented"></i> <span
+                                                set-text="processError.class + '.' + processError.method"></span>
                                         </li>
                                     </ul>
                                 </li>
@@ -718,10 +708,8 @@ <h3>
 
                         <p>
                             Below is a list of potential problems detected by MireDot. They can be severe or not. Some
-                            of them wil result
-                            in low quality documentation, some are real implementation issues. With each warning, the
-                            Java method
-                            causing the problem is documented.
+                            of them wil result in low quality documentation, some are real implementation issues. With
+                            each warning, the Java method causing the problem is documented.
                         </p>
 
                         <ul class="warningsList">
@@ -734,12 +722,12 @@ <h3>
                                 <ul class="warningsListContent" set-if="validLicense && licenseType == 'PRO'">
                                     <li ng-repeat="projectWarning in projectWarningsOfType">
                                         <i set-if="projectWarning.failedBuild" class="icon-exclamation-sign failedIcon"
-                                           title="Failed Build"></i>
-                                        <i set-if="!projectWarning.failedBuild" class="icon-warning-sign warningIcon"
-                                           title="Warning"></i>
-                                        <a set-href="'#' + projectWarning.interface"
-                                           set-text="getInterfaceByHash(projectWarning.interface).url"
-                                           target="_self"></a>
+                                           title="Failed Build"></i> <i set-if="!projectWarning.failedBuild"
+                                                                        class="icon-warning-sign warningIcon"
+                                                                        title="Warning"></i> <a
+                                            set-href="'#' + projectWarning.interface"
+                                            set-text="getInterfaceByHash(projectWarning.interface).url"
+                                            target="_self"></a>
 
                                         <p>
                                             <b>method</b>: <span
@@ -750,19 +738,17 @@ <h3>
                                 </ul>
 
                                 <div set-if="validLicense && licenseType == 'FREE'">
-                                    <i class="icon-exclamation-sign licenseIcon" title="Free version"></i>
-                                    <strong>
-                                        <ng-pluralize count="projectWarningsOfType.length"
-                                                      when="{'one': 'One issue', 'other': '{} issues'}">
-                                        </ng-pluralize>
-                                    </strong>
+                                    <i class="icon-exclamation-sign licenseIcon" title="Free version"></i> <strong>
+                                    <ng-pluralize count="projectWarningsOfType.length"
+                                                  when="{'one': 'One issue', 'other': '{} issues'}">
+                                    </ng-pluralize>
+                                </strong>
                                     <ng-pluralize count="projectWarningsOfType.length"
                                                   when="{'one': 'is', 'other': 'are'}">
                                     </ng-pluralize>
                                     not shown here because this documentation was generated by the free version of
-                                    MireDot.
-                                    As such, not all features are supported.
-                                    <span set-html="visitWebsiteForProVersion"></span>
+                                    MireDot. As such, not all features are supported. <span
+                                        set-html="visitWebsiteForProVersion"></span>
                                 </div>
                             </li>
                         </ul>
@@ -774,9 +760,9 @@ <h3>
             <div id="footer">
                 <div style="padding-top: 10px; padding-bottom: 10px; text-align: center;">
                     <p class="muted" style="font-size: 12px; margin: 0;">
-                        <span set-text="dateOfGeneration"></span> - REST documentation generated by
-                        <a href="http://www.miredot.com" target="_blank"><img src="img/miredot_mini.png"
-                                                                              style="vertical-align: text-bottom;"></a>
+                        <span set-text="dateOfGeneration"></span> - REST documentation generated by <a
+                            href="http://www.miredot.com" rel="nofollow" target="_blank"><img src="img/miredot_mini.png"
+                                                                                              style="vertical-align: text-bottom;"></a>
                         version {{miredotVersion}}{{versionCheckResult}}
                     </p>
                 </div>
diff --git a/latest/chat.html b/latest/chat.html
index dad147a6a..43c1bd9f5 100644
--- a/latest/chat.html
+++ b/latest/chat.html
@@ -5,7 +5,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge">
     <meta name="viewport" content="width=device-width, initial-scale=1">
     <link rel="shortcut icon" href="resources/images/favicon.ico">
-    <title>apiman :: chat</title>
+    <title>apiman Chat | apiman Open Source API Management</title>
 
     <link href="resources/bootstrap-3.3.0/css/bootstrap.min.css" rel="stylesheet">
     <link href="resources/patternfly-1.0.5/css/patternfly.min.css" rel="stylesheet">
@@ -35,8 +35,8 @@
   </head>
   <body class="chat">
     <div id="rhbar">
-      <a class="jbdevlogo" href="http://www.jboss.org/projects/about"></a>
-      <a class="rhlogo" href="http://www.redhat.com/"></a>
+      <a class="jbdevlogo" href="http://www.jboss.org/projects/about" rel="nofollow" target="_blank"></a>
+      <a class="rhlogo" href="http://www.redhat.com/" rel="nofollow" target="_blank"></a>
     </div>
     <nav id="top-nav" class="navbar navbar-inverse" role="navigation">
       <div class="container">
@@ -56,19 +56,19 @@
             <li class="top-menu-item menu-item"><a href="roadmap.html">Roadmap</a></li>
             <li class="top-menu-item menu-item"><a href="/blog">Blog</a></li>
             <li class="top-menu-item menu-item dropdown active">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Get Involved<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Get Involved<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
-                        <a href="https://issues.jboss.org/browse/APIMAN">Report a Bug</a>
+                        <a href="https://issues.jboss.org/browse/APIMAN" rel="nofollow" target="_blank">Report a Bug</a>
                     </li>
                     <li class="menu-item">
                         <a href="chat.html">Chat on IRC</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://twitter.com/apiman_io">Twitter Feed</a>
+                        <a href="https://twitter.com/apiman_io" rel="nofollow" target="_blank">Twitter Feed</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user">Mailing List</a>
+                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="nofollow" target="_blank">Mailing List</a>
                     </li>
                     <li class="divider"></li>
                     <li class="menu-item">
@@ -77,7 +77,7 @@
                 </ul>
             </li>
             <li class="top-menu-item menu-item dropdown">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Learn More<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" rel="nofollow" target="_blank" class="dropdown-toggle" data-toggle="dropdown">Learn More<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
                         <a href="tutorials.html">Tutorials &amp; Walkthroughs</a>
@@ -123,12 +123,12 @@
                 <h1 class="section-header">Chat on IRC</h1>
                 <p>Please feel free to join us in our IRC channel: irc.freenode.net's #apiman.</p>
                 <p>We're almost always around and this is where most of the real-time discussions about the project take place.</p>
-                <p>You can easily <a href="http://webchat.freenode.net/">connect to freenode</a> using the webchat client, or else use your favorite IRC client (recommendations below)</p>
+                <p>You can easily <a href="http://webchat.freenode.net/" rel="nofollow" target="_blank">connect to freenode</a> using the webchat client, or else use your favorite IRC client (recommendations below)</p>
                 <h3>IRC Client Recommendations</h3>
                 <ul>
-                    <li>Linux: <a href="http://www.xchat.org/">XChat</a></li>
-                    <li>Windows: <a href="http://hexchat.github.io/">HexChat</a>, <a href="http://www.hydrairc.com/">HydraIrc</a></li>
-                    <li>Mac: <a href="http://colloquy.info/">Colloquy</a></li>
+                    <li>Linux: <a href="http://www.xchat.org/" rel="nofollow" target="_blank">XChat</a></li>
+                    <li>Windows: <a href="http://hexchat.github.io/" rel="nofollow" target="_blank">HexChat</a>, <a href="http://www.hydrairc.com/" rel="nofollow" target="_blank">HydraIrc</a></li>
+                    <li>Mac: <a href="http://colloquy.info/" rel="nofollow" target="_blank">Colloquy</a></li>
                 </ul>
             </div>
         </div>
@@ -141,14 +141,14 @@ <h3>IRC Client Recommendations</h3>
                         <div class="textwidget">
                             <p>
                                 Copyright © 2015 Red Hat, Inc. All rights reserved.<br>
-                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License, v2.0</a>.<br>
+                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="nofollow" target="_blank">Apache License, v2.0</a>.<br>
                                 <a href="disclosure.html">Open Source Disclosure</a>
                             </p>
                         </div>
                     </div>
                     <div class="widget col-sm-6 col-md-6 widget_text" style="text-align: right">
                         
-                        <a href="http://www.redhat.com"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png"></a>
+                        <a href="http://www.redhat.com" rel="nofollow" target="_blank"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png" alt="Red Hat"></a>
                     </div>
                 </div>
                 <nav class="clearfix"></nav>
diff --git a/latest/contributors.html b/latest/contributors.html
index 19e64dd5c..5cb9319b2 100644
--- a/latest/contributors.html
+++ b/latest/contributors.html
@@ -5,7 +5,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge">
     <meta name="viewport" content="width=device-width, initial-scale=1">
     <link rel="shortcut icon" href="resources/images/favicon.ico">
-    <title>apiman :: contributors</title>
+    <title>Contributors | apiman Open Source API Management</title>
 
     <link href="resources/bootstrap-3.3.0/css/bootstrap.min.css" rel="stylesheet">
     <link href="resources/patternfly-1.0.5/css/patternfly.min.css" rel="stylesheet">
@@ -35,8 +35,8 @@
   </head>
   <body class="contributors">
     <div id="rhbar">
-      <a class="jbdevlogo" href="http://www.jboss.org/projects/about"></a>
-      <a class="rhlogo" href="http://www.redhat.com/"></a>
+      <a class="jbdevlogo" href="http://www.jboss.org/projects/about" rel="nofollow" target="_blank"></a>
+      <a class="rhlogo" href="http://www.redhat.com/" rel="nofollow" target="_blank"></a>
     </div>
     <nav id="top-nav" class="navbar navbar-inverse" role="navigation">
       <div class="container">
@@ -56,19 +56,19 @@
             <li class="top-menu-item menu-item"><a href="roadmap.html">Roadmap</a></li>
             <li class="top-menu-item menu-item"><a href="/blog">Blog</a></li>
             <li class="top-menu-item menu-item dropdown active">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Get Involved<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Get Involved<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
-                        <a href="https://issues.jboss.org/browse/APIMAN">Report a Bug</a>
+                        <a href="https://issues.jboss.org/browse/APIMAN" rel="nofollow" target="_blank">Report a Bug</a>
                     </li>
                     <li class="menu-item">
                         <a href="chat.html">Chat on IRC</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://twitter.com/apiman_io">Twitter Feed</a>
+                        <a href="https://twitter.com/apiman_io" rel="nofollow" target="_blank">Twitter Feed</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user">Mailing List</a>
+                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="nofollow" target="_blank">Mailing List</a>
                     </li>
                     <li class="divider"></li>
                     <li class="menu-item">
@@ -77,7 +77,7 @@
                 </ul>
             </li>
             <li class="top-menu-item menu-item dropdown">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Learn More<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Learn More<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
                         <a href="tutorials.html">Tutorials &amp; Walkthroughs</a>
@@ -132,21 +132,22 @@ <h1 class="section-header">Contributors to apiman</h1>
                 </p>
                 <p>
                     If we missed anyone, or if you are on the list but would like a link added to your
-                    name, please submit a pull request for the <a href="https://github.com/apiman/apiman.github.io/blob/master/latest/contributors.html">apiman project site</a>!
+                    name, please submit a pull request for the <a href="https://github.com/apiman/apiman.github.io/blob/master/latest/contributors.html" rel="nofollow" target="_blank">apiman project site</a>!
                 </p>
                 <h3>Contributor List</h3>
                 <ul>
-                    <li><a href="https://github.com/sbunciak">Bunciak, Stefan</a></li>
+                    <li><a href="https://github.com/sbunciak" rel="nofollow" target="_blank">Bunciak, Stefan</a></li>
                     <li>Cechacek, Jakub</li>
-                    <li><a href="https://github.com/objectiser">Brown, Gary</a></li>
+                    <li><a href="https://github.com/objectiser" rel="nofollow" target="_blank">Brown, Gary</a></li>
                     <li>DiMaggio, Len</li>
                     <li>Gaisford, Brandon</li>
                     <li>Kieling, Alexandre</li>
-                    <li><a href="https://github.com/brmeyer">Meyer, Brett</a></li>
+                    <li><a href="https://github.com/brmeyer" rel="nofollow" target="_blank">Meyer, Brett</a></li>
                     <li>Morales, Jorge</li>
-                    <li><a href="https://github.com/msavy">Savy, Marc</a></li>
-                    <li><a href="https://github.com/KurtStam">Stam, Kurt</a></li>
-                    <li><a href="https://github.com/EricWittmann">Wittmann, Eric</a></li>
+                    <li><a href="https://github.com/msavy" rel="nofollow" target="_blank">Savy, Marc</a></li>
+                    <li><a href="https://github.com/KurtStam" rel="nofollow" target="_blank">Stam, Kurt</a></li>
+                    <li><a href="https://github.com/EricWittmann" rel="nofollow" target="_blank">Wittmann, Eric</a></li>
+                    <li><a href="https://github.com/kahboom" rel="nofollow" target="_blank">Yordán, Rachel</a></li>
                 </ul>
             </div>
         </div>
@@ -159,14 +160,14 @@ <h3>Contributor List</h3>
                         <div class="textwidget">
                             <p>
                                 Copyright © 2015 Red Hat, Inc. All rights reserved.<br>
-                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License, v2.0</a>.<br>
+                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="nofollow" target="_blank">Apache License, v2.0</a>.<br>
                                 <a href="disclosure.html">Open Source Disclosure</a>
                             </p>
                         </div>
                     </div>
                     <div class="widget col-sm-6 col-md-6 widget_text" style="text-align: right">
                         
-                        <a href="http://www.redhat.com"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png"></a>
+                        <a href="http://www.redhat.com" rel="nofollow" target="_blank"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png" alt="Red Hat"></a>
                     </div>
                 </div>
                 <nav class="clearfix"></nav>
diff --git a/latest/developer-guide.html b/latest/developer-guide.html
index ab4f6a581..574f7da14 100644
--- a/latest/developer-guide.html
+++ b/latest/developer-guide.html
@@ -50,8 +50,8 @@
   </head>
   <body class="developer-guide guide">
     <div id="rhbar">
-      <a class="jbdevlogo" href="http://www.jboss.org/projects/about"></a>
-      <a class="rhlogo" href="http://www.redhat.com/"></a>
+      <a class="jbdevlogo" href="http://www.jboss.org/projects/about" rel="nofollow" target="_blank"></a>
+      <a class="rhlogo" href="http://www.redhat.com/" rel="nofollow" target="_blank"></a>
     </div>
     <nav id="top-nav" class="navbar navbar-inverse" role="navigation">
       <div class="container">
@@ -74,16 +74,16 @@
                 <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Get Involved<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
-                        <a href="https://issues.jboss.org/browse/APIMAN">Report a Bug</a>
+                        <a href="https://issues.jboss.org/browse/APIMAN" rel="nofollow" target="_blank">Report a Bug</a>
                     </li>
                     <li class="menu-item">
                         <a href="chat.html">Chat on IRC</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://twitter.com/apiman_io">Twitter Feed</a>
+                        <a href="https://twitter.com/apiman_io" rel="nofollow" target="_blank">Twitter Feed</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user">Mailing List</a>
+                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="nofollow" target="_blank">Mailing List</a>
                     </li>
                     <li class="divider"></li>
                     <li class="menu-item">
@@ -92,7 +92,7 @@
                 </ul>
             </li>
             <li class="top-menu-item menu-item dropdown active">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Learn More<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Learn More<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
                         <a href="tutorials.html">Tutorials &amp; Walkthroughs</a>
@@ -147,14 +147,14 @@
                         <div class="textwidget">
                             <p>
                                 Copyright © 2015 Red Hat, Inc. All rights reserved.<br>
-                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License, v2.0</a>.<br> 
+                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="nofollow" target="_blank">Apache License, v2.0</a>.<br>
                                 <a href="disclosure.html">Open Source Disclosure</a>
                             </p>
                         </div>
                     </div>
                     <div class="widget col-sm-6 col-md-6 widget_text" style="text-align: right">
                         
-                        <a href="http://www.redhat.com"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png"></a>
+                        <a href="http://www.redhat.com" rel="nofollow" target="_blank"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png" alt="Red Hat"></a>
                     </div>
                 </div>
                 <nav class="clearfix"></nav>
@@ -163,4 +163,4 @@
     </div>
 
   </body>
-</html>
\ No newline at end of file
+</html>
diff --git a/latest/developer-guide/index.html b/latest/developer-guide/index.html
index d1b22d9e6..d7b3e5b45 100644
--- a/latest/developer-guide/index.html
+++ b/latest/developer-guide/index.html
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html
   PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><title xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory">apiman - Developer Guide</title><link rel="stylesheet" href="css/jbossorg.css" type="text/css"/><meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" name="generator" content="DocBook XSL-NS Stylesheets V1.74.0"/><meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" http-equiv="Content-Type" content="text/html; charset=UTF-8"/></head><body><div class="book" lang="en-US"><div class="titlepage"><div><p xmlns:d="http://docbook.org/ns/docbook" id="title"><a href="http://www.jboss.org" class="site_href"><strong>JBoss.org</strong></a><a href="http://docs.jboss.org/" class="doc_href"><strong>Community Documentation</strong></a></p><div><h1 class="title"><a id="d0e3"/>apiman - Developer Guide</h1></div></div><hr/></div><div class="toc"><dl><dt><span class="chapter"><a href="#_introduction">1. Introduction</a></span></dt><dt><span class="chapter"><a href="#_developer_resources">2. Developer Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#_source_code">2.1. Source Code</a></span></dt><dt><span class="section"><a href="#_issue_tracking">2.2. Issue Tracking</a></span></dt><dt><span class="section"><a href="#_development_tools">2.3. Development Tools</a></span></dt><dt><span class="section"><a href="#_building_the_project">2.4. Building the Project</a></span></dt><dt><span class="section"><a href="#_setting_up_a_development_environment">2.5. Setting up a Development Environment</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_architecture">3. Architecture</a></span></dt><dt><span class="chapter"><a href="#_plugins">4. Plugins</a></span></dt><dd><dl><dt><span class="section"><a href="#_creating_a_plugin">4.1. Creating a Plugin</a></span></dt><dd><dl><dt><span class="section"><a href="#_the_plugin_specification_file">4.1.1. The Plugin Specification File</a></span></dt><dt><span class="section"><a href="#_using_maven_to_create_a_plugin">4.1.2. Using Maven to Create a Plugin</a></span></dt><dt><span class="section"><a href="#_making_your_plugin_available_to_apiman">4.1.3. Making Your Plugin Available to apiman</a></span></dt></dl></dd><dt><span class="section"><a href="#_contributing_a_policy">4.2. Contributing a Policy</a></span></dt><dd><dl><dt><span class="section"><a href="#_policy_implementation">4.2.1. Policy Implementation</a></span></dt><dt><span class="section"><a href="#_policy_definition">4.2.2. Policy Definition</a></span></dt><dt><span class="section"><a href="#_policy_configuration_form">4.2.3. Policy Configuration Form</a></span></dt></dl></dd><dt><span class="section"><a href="#_testing_a_plugin_policy">4.3. Testing a Plugin Policy</a></span></dt><dd><dl><dt><span class="section"><a href="#_import_the_framework_maven_dependency">4.3.1. Import the Framework (Maven Dependency)</a></span></dt><dt><span class="section"><a href="#_create_and_annotate_a_junit_test_case">4.3.2. Create and Annotate a JUnit Test Case</a></span></dt><dt><span class="section"><a href="#_providing_a_custom_back_end_api_mock">4.3.3. Providing a Custom Back-End API Mock</a></span></dt></dl></dd><dt><span class="section"><a href="#_contributing_a_core_component">4.4. Contributing a Core Component</a></span></dt><dd><dl><dt><span class="section"><a href="#_implementing_a_custom_core_component">4.4.1. Implementing a Custom Core Component</a></span></dt><dt><span class="section"><a href="#_enabling_your_custom_component">4.4.2. Enabling Your Custom Component</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#_gateway_implementations">5. Gateway Implementations</a></span></dt><dd><dl><dt><span class="section"><a href="#_implementing_iapimanbuffer">5.1. Implementing IApimanBuffer</a></span></dt><dt><span class="section"><a href="#_executing_apiman_core">5.2. Executing apiman-core</a></span></dt><dd><dl><dt><span class="section"><a href="#_streaming_data">5.2.1. Streaming data</a></span></dt><dt><span class="section"><a href="#_handling_results">5.2.2. Handling results</a></span></dt><dt><span class="section"><a href="#_handling_failures">5.2.3. Handling Failures</a></span></dt></dl></dd><dt><span class="section"><a href="#_creating_an_api_connector">5.3. Creating an API Connector</a></span></dt><dd><dl><dt><span class="section"><a href="#_connector_basics">5.3.1. Connector basics</a></span></dt><dt><span class="section"><a href="#_creating_the_iapiconnection">5.3.2. Creating the IApiConnection</a></span></dt><dt><span class="section"><a href="#_creating_the_iapiconnectionresponse">5.3.3. Creating the IApiConnectionResponse</a></span></dt><dt><span class="section"><a href="#_implementation_strategies">5.3.4. Implementation strategies</a></span></dt></dl></dd></dl></dd></dl></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_introduction"/>Chapter 1. Introduction</h2></div></div></div><p>Are you interested in contributing to the development of apiman?  Maybe you want to embed the
+<html xmlns="http://www.w3.org/1999/xhtml"><head><title xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory">Developer Guide | apiman Open Source API Management</title><link rel="stylesheet" href="css/jbossorg.css" type="text/css"/><meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" name="generator" content="DocBook XSL-NS Stylesheets V1.74.0"/><meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" http-equiv="Content-Type" content="text/html; charset=UTF-8"/></head><body><div class="book" lang="en-US"><div class="titlepage"><div><p xmlns:d="http://docbook.org/ns/docbook" id="title"><a href="http://www.jboss.org" class="site_href"><strong>JBoss.org</strong></a><a href="http://docs.jboss.org/" class="doc_href"><strong>Community Documentation</strong></a></p><div><h1 class="title"><a id="d0e3"/>apiman - Developer Guide</h1></div></div><hr/></div><div class="toc"><dl><dt><span class="chapter"><a href="#_introduction">1. Introduction</a></span></dt><dt><span class="chapter"><a href="#_developer_resources">2. Developer Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#_source_code">2.1. Source Code</a></span></dt><dt><span class="section"><a href="#_issue_tracking">2.2. Issue Tracking</a></span></dt><dt><span class="section"><a href="#_development_tools">2.3. Development Tools</a></span></dt><dt><span class="section"><a href="#_building_the_project">2.4. Building the Project</a></span></dt><dt><span class="section"><a href="#_setting_up_a_development_environment">2.5. Setting up a Development Environment</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_architecture">3. Architecture</a></span></dt><dt><span class="chapter"><a href="#_plugins">4. Plugins</a></span></dt><dd><dl><dt><span class="section"><a href="#_creating_a_plugin">4.1. Creating a Plugin</a></span></dt><dd><dl><dt><span class="section"><a href="#_the_plugin_specification_file">4.1.1. The Plugin Specification File</a></span></dt><dt><span class="section"><a href="#_using_maven_to_create_a_plugin">4.1.2. Using Maven to Create a Plugin</a></span></dt><dt><span class="section"><a href="#_making_your_plugin_available_to_apiman">4.1.3. Making Your Plugin Available to apiman</a></span></dt></dl></dd><dt><span class="section"><a href="#_contributing_a_policy">4.2. Contributing a Policy</a></span></dt><dd><dl><dt><span class="section"><a href="#_policy_implementation">4.2.1. Policy Implementation</a></span></dt><dt><span class="section"><a href="#_policy_definition">4.2.2. Policy Definition</a></span></dt><dt><span class="section"><a href="#_policy_configuration_form">4.2.3. Policy Configuration Form</a></span></dt></dl></dd><dt><span class="section"><a href="#_testing_a_plugin_policy">4.3. Testing a Plugin Policy</a></span></dt><dd><dl><dt><span class="section"><a href="#_import_the_framework_maven_dependency">4.3.1. Import the Framework (Maven Dependency)</a></span></dt><dt><span class="section"><a href="#_create_and_annotate_a_junit_test_case">4.3.2. Create and Annotate a JUnit Test Case</a></span></dt><dt><span class="section"><a href="#_providing_a_custom_back_end_api_mock">4.3.3. Providing a Custom Back-End API Mock</a></span></dt></dl></dd><dt><span class="section"><a href="#_contributing_a_core_component">4.4. Contributing a Core Component</a></span></dt><dd><dl><dt><span class="section"><a href="#_implementing_a_custom_core_component">4.4.1. Implementing a Custom Core Component</a></span></dt><dt><span class="section"><a href="#_enabling_your_custom_component">4.4.2. Enabling Your Custom Component</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#_gateway_implementations">5. Gateway Implementations</a></span></dt><dd><dl><dt><span class="section"><a href="#_implementing_iapimanbuffer">5.1. Implementing IApimanBuffer</a></span></dt><dt><span class="section"><a href="#_executing_apiman_core">5.2. Executing apiman-core</a></span></dt><dd><dl><dt><span class="section"><a href="#_streaming_data">5.2.1. Streaming data</a></span></dt><dt><span class="section"><a href="#_handling_results">5.2.2. Handling results</a></span></dt><dt><span class="section"><a href="#_handling_failures">5.2.3. Handling Failures</a></span></dt></dl></dd><dt><span class="section"><a href="#_creating_an_api_connector">5.3. Creating an API Connector</a></span></dt><dd><dl><dt><span class="section"><a href="#_connector_basics">5.3.1. Connector basics</a></span></dt><dt><span class="section"><a href="#_creating_the_iapiconnection">5.3.2. Creating the IApiConnection</a></span></dt><dt><span class="section"><a href="#_creating_the_iapiconnectionresponse">5.3.3. Creating the IApiConnectionResponse</a></span></dt><dt><span class="section"><a href="#_implementation_strategies">5.3.4. Implementation strategies</a></span></dt></dl></dd></dl></dd></dl></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_introduction"/>Chapter 1. Introduction</h2></div></div></div><p>Are you interested in contributing to the development of apiman?  Maybe you want to embed the
 project in your own solution?  In either case this is the guide for you.</p></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_developer_resources"/>Chapter 2. Developer Resources</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#_source_code">2.1. Source Code</a></span></dt><dt><span class="section"><a href="#_issue_tracking">2.2. Issue Tracking</a></span></dt><dt><span class="section"><a href="#_development_tools">2.3. Development Tools</a></span></dt><dt><span class="section"><a href="#_building_the_project">2.4. Building the Project</a></span></dt><dt><span class="section"><a href="#_setting_up_a_development_environment">2.5. Setting up a Development Environment</a></span></dt></dl></div><p>This section describes a number of resources that are useful if you wish to contribute
 code to apiman.  It is likely also a good starting point for those wishing to provide
 functionality by implementing a plugin, although more information about plugins can
 be found in the <span class="emphasis"><em>Plugins</em></span> section.</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_source_code"/>2.1. Source Code</h2></div></div></div><p>The apiman source code is located in github here:</p><p><a class="ulink" href="https://github.com/apiman/apiman">https://github.com/apiman/apiman</a></p><p>Source code for the apiman project web site is here:</p><p><a class="ulink" href="https://github.com/apiman/apiman.github.io">https://github.com/apiman/apiman.github.io</a></p><p>The docker files are currently here:</p><p><a class="ulink" href="https://github.com/apiman/apiman-docker">https://github.com/apiman/apiman-docker</a></p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_issue_tracking"/>2.2. Issue Tracking</h2></div></div></div><p>The apiman project uses JIRA to track issues such as bugs and feature requests.  It’s a good place to start
-if you’re trying to figure out how to get involved!</p><p><a class="ulink" href="https://issues.jboss.org/browse/APIMAN">https://issues.jboss.org/browse/APIMAN</a></p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_development_tools"/>2.3. Development Tools</h2></div></div></div><p>We’re rather IDE agnostic, so contributors should feel free to use whatever tools they feel most
+if you’re trying to figure out how to get involved!</p><p><a class="ulink" href="https://issues.jboss.org/browse/APIMAN" rel="nofollow">https://issues.jboss.org/browse/APIMAN</a></p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_development_tools"/>2.3. Development Tools</h2></div></div></div><p>We’re rather IDE agnostic, so contributors should feel free to use whatever tools they feel most
 comfortable with.  At the time of this writing, the core apiman developers primarily use Eclipse
 Kepler.</p><p><a class="ulink" href="http://www.eclipse.org/downloads/">http://www.eclipse.org/downloads/</a></p><p>The core apiman project is built using maven.  Currently we recommend at least version 3.0.3.</p><p><a class="ulink" href="http://maven.apache.org/download.cgi">http://maven.apache.org/download.cgi</a></p><p>And of course you’ll need to have git installed if you want to check out the code from github.</p><p><a class="ulink" href="http://git-scm.com/">http://git-scm.com/</a></p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_building_the_project"/>2.4. Building the Project</h2></div></div></div><p>Building apiman should be a simple matter of doing a standard Maven build:</p><pre class="literallayout">mvn clean install</pre><p>This will do a full build of apiman and execute all unit tests.  However,
 the result will not include a ready-to-run version of apiman.  For that, you
diff --git a/latest/disclosure.html b/latest/disclosure.html
index 9c7eb2e55..c639d2d10 100644
--- a/latest/disclosure.html
+++ b/latest/disclosure.html
@@ -5,7 +5,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge">
     <meta name="viewport" content="width=device-width, initial-scale=1">
     <link rel="shortcut icon" href="resources/images/favicon.ico">
-    <title>apiman :: disclosure</title>
+    <title>Disclosure | apiman Open Source API Management</title>
 
     <link href="resources/bootstrap-3.3.0/css/bootstrap.min.css" rel="stylesheet">
     <link href="resources/patternfly-1.0.5/css/patternfly.min.css" rel="stylesheet">
@@ -35,8 +35,8 @@
   </head>
   <body class="disclosure">
     <div id="rhbar">
-      <a class="jbdevlogo" href="http://www.jboss.org/projects/about"></a>
-      <a class="rhlogo" href="http://www.redhat.com/"></a>
+      <a class="jbdevlogo" href="http://www.jboss.org/projects/about" rel="nofollow" target="_blank"></a>
+      <a class="rhlogo" href="http://www.redhat.com/" rel="nofollow" target="_blank"></a>
     </div>
     <nav id="top-nav" class="navbar navbar-inverse" role="navigation">
       <div class="container">
@@ -56,19 +56,19 @@
             <li class="top-menu-item menu-item"><a href="roadmap.html">Roadmap</a></li>
             <li class="top-menu-item menu-item"><a href="/blog">Blog</a></li>
             <li class="top-menu-item menu-item dropdown">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Get Involved<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Get Involved<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
-                        <a href="https://issues.jboss.org/browse/APIMAN">Report a Bug</a>
+                        <a href="https://issues.jboss.org/browse/APIMAN" rel="nofollow" target="_blank">Report a Bug</a>
                     </li>
                     <li class="menu-item">
                         <a href="chat.html">Chat on IRC</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://twitter.com/apiman_io">Twitter Feed</a>
+                        <a href="https://twitter.com/apiman_io" rel="nofollow" target="_blank">Twitter Feed</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user">Mailing List</a>
+                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="nofollow" target="_blank">Mailing List</a>
                     </li>
                     <li class="divider"></li>
                     <li class="menu-item">
@@ -77,7 +77,7 @@
                 </ul>
             </li>
             <li class="top-menu-item menu-item dropdown">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Learn More<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Learn More<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
                         <a href="tutorials.html">Tutorials &amp; Walkthroughs</a>
@@ -125,7 +125,7 @@ <h1 class="section-header">Disclosure</h1>
 <p>We'd like to make clear how this project works and who holds what responsibilities. We want everyone involved to
 understand how decisions are made and where they can contribute. If you feel this page does not reflect the current
 state of project ownership and responsibilities, please contact the team on <a href="chat.html">IRC</a>
-or the <a href="https://lists.jboss.org/mailman/listinfo/apiman-user">Mailing List</a>.</p>
+or the <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="nofollow" target="_blank">Mailing List</a>.</p>
 
 <h2>Stewardship</h2>
 
@@ -139,11 +139,11 @@ <h2>Requirement Definition</h2>
 <p>The requirements and roadmap for apiman are driven by Red Hat and by the community. Typically, when a major release
 is being planned, the project lead will take input from both Red Hat and the community, and evaluate what can be done in
 the necessary time. This will define what features will be addressed in a given release. The project lead will then
-publish the roadmap in the project <a href="https://issues.jboss.org">Issue Tracker (JIRA)</a>.</p>
+publish the roadmap in the project <a href="https://issues.jboss.org" rel="nofollow" target="_blank">Issue Tracker (JIRA)</a>.</p>
 
 <p>The best way for you to suggest requirements for a future release of apiman is to enter a feature request in
-<a href="https://issues.jboss.org/browse/APIMAN">JIRA</a>. Lobbying for features using the voting functionality in
-<a href="https://issues.jboss.org">JIRA</a>, and sending email to the <a href="#">mailing list</a>
+<a href="https://issues.jboss.org/browse/APIMAN" rel="nofollow" target="_blank">JIRA</a>. Lobbying for features using the voting functionality in
+<a href="https://issues.jboss.org" rel="nofollow" target="_blank">JIRA</a>, and sending email to the <a href="#">mailing list</a>
 are all great ways to express interest as well.  Of course, contributing is the single most expedient way 
 to get a capability into a particular release.</p>
 
@@ -167,14 +167,14 @@ <h2>Contribution</h2>
                         <div class="textwidget">
                             <p>
                                 Copyright © 2015 Red Hat, Inc. All rights reserved.<br>
-                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License, v2.0</a>.<br> 
+                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="nofollow" target="_blank">Apache License, v2.0</a>.<br>
                                 <a href="disclosure.html">Open Source Disclosure</a>
                             </p>
                         </div>
                     </div>
                     <div class="widget col-sm-6 col-md-6 widget_text" style="text-align: right">
                         
-                        <a href="http://www.redhat.com"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png"></a>
+                        <a href="http://www.redhat.com" rel="nofollow" target="_blank"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png" alt="Red Hat"></a>
                     </div>
                 </div>
                 <nav class="clearfix"></nav>
diff --git a/latest/download.html b/latest/download.html
index 468af7c7b..9530ad664 100644
--- a/latest/download.html
+++ b/latest/download.html
@@ -5,7 +5,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge">
     <meta name="viewport" content="width=device-width, initial-scale=1">
     <link rel="shortcut icon" href="resources/images/favicon.ico">
-    <title>apiman :: download</title>
+    <title>Download | apiman Open Source API Management</title>
 
     <link href="resources/bootstrap-3.3.0/css/bootstrap.min.css" rel="stylesheet">
     <link href="resources/patternfly-1.0.5/css/patternfly.min.css" rel="stylesheet">
@@ -35,8 +35,8 @@
   </head>
   <body class="download">
     <div id="rhbar">
-      <a class="jbdevlogo" href="http://www.jboss.org/projects/about"></a>
-      <a class="rhlogo" href="http://www.redhat.com/"></a>
+      <a class="jbdevlogo" href="http://www.jboss.org/projects/about" rel="nofollow" target="_blank"></a>
+      <a class="rhlogo" href="http://www.redhat.com/" rel="nofollow" target="_blank"></a>
     </div>
     <nav id="top-nav" class="navbar navbar-inverse" role="navigation">
       <div class="container">
@@ -56,19 +56,19 @@
             <li class="top-menu-item menu-item"><a href="roadmap.html">Roadmap</a></li>
             <li class="top-menu-item menu-item"><a href="/blog">Blog</a></li>
             <li class="top-menu-item menu-item dropdown">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Get Involved<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Get Involved<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
-                        <a href="https://issues.jboss.org/browse/APIMAN">Report a Bug</a>
+                        <a href="https://issues.jboss.org/browse/APIMAN" rel="nofollow" target="_blank">Report a Bug</a>
                     </li>
                     <li class="menu-item">
                         <a href="chat.html">Chat on IRC</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://twitter.com/apiman_io">Twitter Feed</a>
+                        <a href="https://twitter.com/apiman_io" rel="nofollow" target="_blank">Twitter Feed</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user">Mailing List</a>
+                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="nofollow" target="_blank">Mailing List</a>
                     </li>
                     <li class="divider"></li>
                     <li class="menu-item">
@@ -77,7 +77,7 @@
                 </ul>
             </li>
             <li class="top-menu-item menu-item dropdown">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Learn More<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Learn More<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
                         <a href="tutorials.html">Tutorials &amp; Walkthroughs</a>
@@ -127,8 +127,8 @@ <h1 class="section-header">Getting Started</h1>
             <div class="col-lg-7">
                 <h3>Download</h3>
                 <ul>
-                  <li><a href="http://wildfly.org/">WildFly</a> <a onclick="ga('send', 'event', 'download', 'click', 'download-wf9', 1)" href="http://download.jboss.org/wildfly/9.0.2.Final/wildfly-9.0.2.Final.zip">9.0.2.Final</a></li>
-                  <li>apiman <a onclick="ga('send', 'event', 'download', 'click', 'download-apiman-wf9-overlay', 1)" href="http://downloads.jboss.org/apiman/1.2.1.Final/apiman-distro-wildfly9-1.2.1.Final-overlay.zip">1.2.1.Final</a> overlay for WildFly 9</li>
+                  <li><a href="http://wildfly.org/" rel="nofollow" target="_blank">WildFly</a> <a onclick="ga('send', 'event', 'download', 'click', 'download-wf9', 1)" href="http://download.jboss.org/wildfly/9.0.2.Final/wildfly-9.0.2.Final.zip" rel="nofollow" target="_blank">9.0.2.Final</a></li>
+                  <li>apiman <a onclick="ga('send', 'event', 'download', 'click', 'download-apiman-wf9-overlay', 1)" href="http://downloads.jboss.org/apiman/1.2.1.Final/apiman-distro-wildfly9-1.2.1.Final-overlay.zip" rel="nofollow" target="_blank">1.2.1.Final</a> overlay for WildFly 9</li>
                 </ul>
                 
                 <h3>Install</h3>
@@ -141,7 +141,7 @@ <h3>Run</h3>
                 <ol>
                   <li>Start WildFly 9 using the "standalone-apiman.xml" configuration</li>
                   <li>
-                    Point your browser at the <a href="http://localhost:8080/apimanui/">apiman UI</a> and login with admin/admin123!
+                    Point your browser at the <a href="http://localhost:8080/apimanui/" rel="nofollow" target="_blank">apiman UI</a> and login with admin/admin123!
                     <div class="alert alert-info" style="margin-top: 5px;">
                        <span class="pficon pficon-info"></span>
                        We strongly recommend you change the admin password(s) by <a href="http://localhost:8080/auth/admin/">logging in to keycloak</a>!
@@ -179,7 +179,7 @@ <h1 class="section-header">Getting Started (Docker)</h1>
             <div class="col-lg-7">
                 <h3>Download</h3>
                 <ul>
-                  <li>Use docker to pull the "<a href="https://registry.hub.docker.com/u/jboss/apiman-wildfly/">apiman WildFly 9</a>" docker image:  <strong>jboss/apiman-wildfly</strong></li>
+                  <li>Use docker to pull the "<a href="https://registry.hub.docker.com/u/jboss/apiman-wildfly/" rel="nofollow" target="_blank">apiman WildFly 9</a>" docker image:  <strong>jboss/apiman-wildfly</strong></li>
                 </ul>
                 <h3>Run</h3>
                 <ul>
@@ -201,7 +201,7 @@ <h3>Configure</h3>
                 <h3>More Info</h3>
                 <p>
                   For more information on apiman docker support, including how to extend the image for your own
-                  uses, <a href="https://registry.hub.docker.com/u/jboss/apiman-wildfly/">click here</a>!
+                  uses, <a href="https://registry.hub.docker.com/u/jboss/apiman-wildfly/" rel="nofollow" target="_blank">click here</a>!
                 </p>
             </div>
 
@@ -222,15 +222,15 @@ <h3>Or simply try this...</h3>
                     <div class="widget col-sm-6 col-md-6 widget_text">
                         <div class="textwidget">
                             <p>
-                                Copyright © 2015 Red Hat, Inc. All rights reserved.<br>
-                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License, v2.0</a>.<br> 
+                                Copyright © 2016 Red Hat, Inc. All rights reserved.<br>
+                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="nofollow" target="_blank">Apache License, v2.0</a>.<br>
                                 <a href="disclosure.html">Open Source Disclosure</a>
                             </p>
                         </div>
                     </div>
                     <div class="widget col-sm-6 col-md-6 widget_text" style="text-align: right">
                         
-                        <a href="http://www.redhat.com"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png"></a>
+                        <a href="http://www.redhat.com" rel="nofollow" target="_blank"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png" alt="Red Hat"></a>
                     </div>
                 </div>
                 <nav class="clearfix"></nav>
@@ -239,4 +239,4 @@ <h3>Or simply try this...</h3>
     </div>
 
   </body>
-</html>
\ No newline at end of file
+</html>
diff --git a/latest/index.html b/latest/index.html
index ebf20af7b..152aa00ca 100644
--- a/latest/index.html
+++ b/latest/index.html
@@ -5,7 +5,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge">
     <meta name="viewport" content="width=device-width, initial-scale=1">
     <link rel="shortcut icon" href="resources/images/favicon.ico">
-    <title>apiman</title>
+    <title>apiman | Open Source API Management</title>
 
     <link href="resources/bootstrap-3.3.0/css/bootstrap.min.css" rel="stylesheet">
     <link href="resources/patternfly-1.0.5/css/patternfly.min.css" rel="stylesheet">
@@ -35,8 +35,8 @@
   </head>
   <body class="overview">
     <div id="rhbar">
-      <a class="jbdevlogo" href="http://www.jboss.org/projects/about"></a>
-      <a class="rhlogo" href="http://www.redhat.com/"></a>
+      <a class="jbdevlogo" href="http://www.jboss.org/projects/about" rel="nofollow" target="_blank"></a>
+      <a class="rhlogo" href="http://www.redhat.com/" rel="nofollow" target="_blank"></a>
     </div>
     <nav id="top-nav" class="navbar navbar-inverse" role="navigation">
       <div class="container">
@@ -56,19 +56,19 @@
             <li class="top-menu-item menu-item"><a href="roadmap.html">Roadmap</a></li>
             <li class="top-menu-item menu-item"><a href="/blog">Blog</a></li>
             <li class="top-menu-item menu-item dropdown">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Get Involved<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Get Involved<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
-                        <a href="https://issues.jboss.org/browse/APIMAN">Report a Bug</a>
+                        <a href="https://issues.jboss.org/browse/APIMAN" rel="nofollow" target="_blank">Report a Bug</a>
                     </li>
                     <li class="menu-item">
                         <a href="chat.html">Chat on IRC</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://twitter.com/apiman_io">Twitter Feed</a>
+                        <a href="https://twitter.com/apiman_io" rel="nofollow" target="_blank">Twitter Feed</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user">Mailing List</a>
+                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="nofollow" target="_blank">Mailing List</a>
                     </li>
                     <li class="divider"></li>
                     <li class="menu-item">
@@ -77,7 +77,7 @@
                 </ul>
             </li>
             <li class="top-menu-item menu-item dropdown">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Learn More<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Learn More<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
                         <a href="tutorials.html">Tutorials &amp; Walkthroughs</a>
@@ -129,8 +129,8 @@ <h1>Open Source API Management</h1>
                           coupling a rich API design &amp; configuration layer with a blazingly fast runtime.
                         </p>
                         <ul>
-                            <li><a class="btn btn-lg btn-primary" href="download.html">Get Started Now</a> <span style="padding-left: 10px;">(Version <a href="https://github.com/apiman/apiman/tree/apiman-1.2.1.Final">1.2.1.Final</a>)</span></li>
-                            <li><img class="icon16" src="resources/images/github-logo.png"></img><span class="icon16-label">Clone or Fork <a href="http://github.com/apiman/apiman">apiman on GitHub</a></span></li>
+                            <li><a class="btn btn-lg btn-primary" href="download.html">Get Started Now</a> <span style="padding-left: 10px;">(Version <a href="https://github.com/apiman/apiman/tree/apiman-1.2.1.Final" rel="nofollow" target="_blank">1.2.1.Final</a>)</span></li>
+                            <li><img class="icon16" src="resources/images/github-logo.png" alt="GitHub"></img><span class="icon16-label">Clone or Fork <a href="http://github.com/apiman/apiman" rel="nofollow" target="_blank">apiman on GitHub</a></span></li>
                         </ul>
                     </div>
                 </div>
@@ -157,7 +157,7 @@ <h3>Easily Embeddable</h3>
             </div>
             <div class="col-lg-3 fitem">
               <h3>Fully Asynchronous</h3>
-              <p>The runtime engine's API is fully asynchronous and is designed to run equally well in both a standard J2EE environment and newer async runtimes like <a href="http://vertx.io/">Vert.x</a>.</p>
+              <p>The runtime engine's API is fully asynchronous and is designed to run equally well in both a standard J2EE environment and newer async runtimes like <a href="http://vertx.io/" rel="nofollow" target="_blank">Vert.x</a>.</p>
             </div>
         </div>
 
@@ -180,7 +180,7 @@ <h3>Billing and Metrics</h3>
             </div>
             <div class="col-md-5">
               <h1 class="section-header">Project News</h1>
-              <a class="twitter-timeline" data-dnt="true" href="https://twitter.com/apiman_io" data-widget-id="509405794580697089" data-chrome="noheader nofooter noborders noscrollbar transparent">Tweets by @apiman_io</a>
+              <a class="twitter-timeline" data-dnt="true" href="https://twitter.com/apiman_io" data-widget-id="509405794580697089"  rel="nofollow" target="_blank" data-chrome="noheader nofooter noborders noscrollbar transparent">Tweets by @apiman_io</a>
               <script>!function(d,s,id){
                     var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';
                     if(!d.getElementById(id)){
@@ -199,15 +199,15 @@ <h1 class="section-header">Project News</h1>
                     <div class="widget col-sm-6 col-md-6 widget_text">
                         <div class="textwidget">
                             <p>
-                                Copyright © 2015 Red Hat, Inc. All rights reserved.<br>
-                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License, v2.0</a>.<br> 
+                                Copyright © 2016 Red Hat, Inc. All rights reserved.<br>
+                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="nofollow" target="_blank">Apache License, v2.0</a>.<br>
                                 <a href="disclosure.html">Open Source Disclosure</a>
                             </p>
                         </div>
                     </div>
                     <div class="widget col-sm-6 col-md-6 widget_text" style="text-align: right">
                         
-                        <a href="http://www.redhat.com"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png"></a>
+                        <a href="http://www.redhat.com" rel="nofollow" target="_blank"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png" alt="Red Hat"></a>
                     </div>
                 </div>
                 <nav class="clearfix"></nav>
@@ -216,4 +216,4 @@ <h1 class="section-header">Project News</h1>
     </div>
 
   </body>
-</html>
\ No newline at end of file
+</html>
diff --git a/latest/installation-guide.html b/latest/installation-guide.html
index 819a2c889..8e4b2d238 100644
--- a/latest/installation-guide.html
+++ b/latest/installation-guide.html
@@ -5,7 +5,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge">
     <meta name="viewport" content="width=device-width, initial-scale=1">
     <link rel="shortcut icon" href="resources/images/favicon.ico">
-    <title>apiman :: installation guide</title>
+    <title>Installation Guide | apiman Open Source API Management</title>
 
     <link href="resources/bootstrap-3.3.0/css/bootstrap.min.css" rel="stylesheet">
     <link href="resources/patternfly-1.0.5/css/patternfly.min.css" rel="stylesheet">
@@ -50,8 +50,8 @@
   </head>
   <body class="installation-guide guide">
     <div id="rhbar">
-      <a class="jbdevlogo" href="http://www.jboss.org/projects/about"></a>
-      <a class="rhlogo" href="http://www.redhat.com/"></a>
+      <a class="jbdevlogo" href="http://www.jboss.org/projects/about" rel="nofollow" target="_blank"></a>
+      <a class="rhlogo" href="http://www.redhat.com/" rel="nofollow" target="_blank"></a>
     </div>
     <nav id="top-nav" class="navbar navbar-inverse" role="navigation">
       <div class="container">
@@ -71,19 +71,19 @@
             <li class="top-menu-item menu-item"><a href="roadmap.html">Roadmap</a></li>
             <li class="top-menu-item menu-item"><a href="/blog">Blog</a></li>
             <li class="top-menu-item menu-item dropdown">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Get Involved<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Get Involved<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
-                        <a href="https://issues.jboss.org/browse/APIMAN">Report a Bug</a>
+                        <a href="https://issues.jboss.org/browse/APIMAN" rel="nofollow" target="_blank">Report a Bug</a>
                     </li>
                     <li class="menu-item">
                         <a href="chat.html">Chat on IRC</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://twitter.com/apiman_io">Twitter Feed</a>
+                        <a href="https://twitter.com/apiman_io" rel="nofollow" target="_blank">Twitter Feed</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user">Mailing List</a>
+                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="nofollow" target="_blank">Mailing List</a>
                     </li>
                     <li class="divider"></li>
                     <li class="menu-item">
@@ -92,7 +92,7 @@
                 </ul>
             </li>
             <li class="top-menu-item menu-item dropdown active">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Learn More<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Learn More<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
                         <a href="tutorials.html">Tutorials &amp; Walkthroughs</a>
@@ -154,7 +154,7 @@
                     </div>
                     <div class="widget col-sm-6 col-md-6 widget_text" style="text-align: right">
                         
-                        <a href="http://www.redhat.com"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png"></a>
+                        <a href="http://www.redhat.com" rel="nofollow" target="_blank"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png" alt="Red Hat"></a>
                     </div>
                 </div>
                 <nav class="clearfix"></nav>
diff --git a/latest/production-guide.html b/latest/production-guide.html
index 0fca64a02..e8eb00e48 100644
--- a/latest/production-guide.html
+++ b/latest/production-guide.html
@@ -5,7 +5,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge">
     <meta name="viewport" content="width=device-width, initial-scale=1">
     <link rel="shortcut icon" href="resources/images/favicon.ico">
-    <title>apiman :: production guide</title>
+    <title>Production Guide | apiman Open Source API Management</title>
 
     <link href="resources/bootstrap-3.3.0/css/bootstrap.min.css" rel="stylesheet">
     <link href="resources/patternfly-1.0.5/css/patternfly.min.css" rel="stylesheet">
@@ -50,8 +50,8 @@
   </head>
   <body class="production-guide guide">
     <div id="rhbar">
-      <a class="jbdevlogo" href="http://www.jboss.org/projects/about"></a>
-      <a class="rhlogo" href="http://www.redhat.com/"></a>
+      <a class="jbdevlogo" href="http://www.jboss.org/projects/about" rel="nofollow" target="_blank"></a>
+      <a class="rhlogo" href="http://www.redhat.com/" rel="nofollow" target="_blank"></a>
     </div>
     <nav id="top-nav" class="navbar navbar-inverse" role="navigation">
       <div class="container">
@@ -71,19 +71,19 @@
             <li class="top-menu-item menu-item"><a href="roadmap.html">Roadmap</a></li>
             <li class="top-menu-item menu-item"><a href="/blog">Blog</a></li>
             <li class="top-menu-item menu-item dropdown">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Get Involved<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Get Involved<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
-                        <a href="https://issues.jboss.org/browse/APIMAN">Report a Bug</a>
+                        <a href="https://issues.jboss.org/browse/APIMAN" rel="nofollow" target="_blank">Report a Bug</a>
                     </li>
                     <li class="menu-item">
                         <a href="chat.html">Chat on IRC</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://twitter.com/apiman_io">Twitter Feed</a>
+                        <a href="https://twitter.com/apiman_io" rel="nofollow" target="_blank">Twitter Feed</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user">Mailing List</a>
+                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="nofollow" target="_blank">Mailing List</a>
                     </li>
                     <li class="divider"></li>
                     <li class="menu-item">
@@ -92,7 +92,7 @@
                 </ul>
             </li>
             <li class="top-menu-item menu-item dropdown active">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Learn More<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Learn More<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
                         <a href="tutorials.html">Tutorials &amp; Walkthroughs</a>
@@ -146,15 +146,15 @@
                     <div class="widget col-sm-6 col-md-6 widget_text">
                         <div class="textwidget">
                             <p>
-                                Copyright © 2015 Red Hat, Inc. All rights reserved.<br>
-                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License, v2.0</a>.<br> 
+                                Copyright © 2016 Red Hat, Inc. All rights reserved.<br>
+                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="nofollow" target="_blank">Apache License, v2.0</a>.<br>
                                 <a href="disclosure.html">Open Source Disclosure</a>
                             </p>
                         </div>
                     </div>
                     <div class="widget col-sm-6 col-md-6 widget_text" style="text-align: right">
                         
-                        <a href="http://www.redhat.com"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png"></a>
+                        <a href="http://www.redhat.com" rel="nofollow" target="_blank"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png" alt="Red Hat"></a>
                     </div>
                 </div>
                 <nav class="clearfix"></nav>
diff --git a/latest/production-guide/index.html b/latest/production-guide/index.html
index 22ef831fa..ffc739fd1 100644
--- a/latest/production-guide/index.html
+++ b/latest/production-guide/index.html
@@ -1,52 +1,52 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><title xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory">Guide - Deploying for Production</title><link rel="stylesheet" href="css/jbossorg.css" type="text/css"/><meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" name="generator" content="DocBook XSL-NS Stylesheets V1.74.0"/><meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" http-equiv="Content-Type" content="text/html; charset=UTF-8"/></head><body><div class="book" lang="en-US"><div class="titlepage"><div><p xmlns:d="http://docbook.org/ns/docbook" id="title"><a href="http://www.jboss.org" class="site_href"><strong>JBoss.org</strong></a><a href="http://docs.jboss.org/" class="doc_href"><strong>Community Documentation</strong></a></p><div><h1 class="title"><a id="d0e3"/>Guide - Deploying for Production</h1></div><div><h2 class="subtitle">apiman 1.2.1.Final</h2></div></div><hr/></div><div class="toc"><dl><dt><span class="chapter"><a href="#_deployment_tooling_for_apiman">1. Deployment Tooling for apiman</a></span></dt><dt><span class="chapter"><a href="#_architecture_summary">2. Architecture Summary</a></span></dt><dt><span class="chapter"><a href="#_database">3. Database</a></span></dt><dt><span class="chapter"><a href="#_elasticsearch">4. Elasticsearch</a></span></dt><dt><span class="chapter"><a href="#_keycloak">5. Keycloak</a></span></dt><dt><span class="chapter"><a href="#_api_gateway">6. API Gateway</a></span></dt><dd><dl><dt><span class="section"><a href="#_installing_the_api_gateway">6.1. Installing the API Gateway</a></span></dt><dt><span class="section"><a href="#_configuring_the_api_gateway">6.2. Configuring the API Gateway</a></span></dt><dd><dl><dt><span class="section"><a href="#_disabling_the_keycloak_server">6.2.1. Disabling the Keycloak Server</a></span></dt><dt><span class="section"><a href="#_setting_the_api_gateway_public_endpoint">6.2.2. Setting the API Gateway Public Endpoint</a></span></dt><dt><span class="section"><a href="#_configuring_keycloak_authentication_for_the_gateway_api">6.2.3. Configuring Keycloak Authentication for the Gateway API</a></span></dt><dt><span class="section"><a href="#_pointing_the_api_gateway_to_a_remote_elasticsearch">6.2.4. Pointing the API Gateway to a Remote Elasticsearch</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#_api_manager">7. API Manager</a></span></dt><dd><dl><dt><span class="section"><a href="#_installing_the_api_manager">7.1. Installing the API Manager</a></span></dt><dt><span class="section"><a href="#_configuring_the_api_manager">7.2. Configuring the API Manager</a></span></dt><dd><dl><dt><span class="section"><a href="#_disabling_the_keycloak_server_2">7.2.1. Disabling the Keycloak Server</a></span></dt><dt><span class="section"><a href="#_connecting_to_the_database">7.2.2. Connecting to the Database</a></span></dt><dt><span class="section"><a href="#_point_the_api_manager_to_the_api_gateway">7.2.3. Point the API Manager to the API Gateway</a></span></dt><dt><span class="section"><a href="#_configuring_keycloak_authentication_for_the_manager_api_and_ui">7.2.4. Configuring Keycloak Authentication for the Manager API and UI</a></span></dt><dt><span class="section"><a href="#_pointing_the_api_manager_to_a_remote_elasticsearch">7.2.5. Pointing the API Manager to a Remote Elasticsearch</a></span></dt></dl></dd></dl></dd></dl></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_deployment_tooling_for_apiman"/>Chapter 1. Deployment Tooling for apiman</h2></div></div></div><p>This guide should serve as a guide to manually deploy apiman into production.  However, we also offer a
-simple shell script that can do much of the work for you.  It will likely always be a work in progress,
-so many production deployers may not feel comfortable using it.  However, it can currently install the
-following components:</p><div class="itemizedlist"><ul><li>Elasticsearch (1.x)</li><li>Keycloak (1.7.0)</li><li>API Manager</li><li>API Gateway</li></ul></div><p>You can find the apiman production deployer here:</p><p><a class="ulink" href="https://github.com/apiman/apiman-deployer/tree/apiman-1.2.1.Final">https://github.com/apiman/apiman-deployer/tree/apiman-1.2.1.Final</a></p><p>Simply download that script and run it on each of the machines you wish to install the various apiman
-components!</p></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_architecture_summary"/>Chapter 2. Architecture Summary</h2></div></div></div><p>Before we get started, it may be useful to know the overall architecture of apiman.  Let’s start with a
-picture!</p><h5 xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="formalpara">Architecture of apiman</h5><p class="formalpara"><span class="inlinemediaobject"><img src="images/images/apiman-architecture.png" alt="Architecture of apiman"/></span></p><p>The apiman solution is made up of a number of pieces, including:</p><div class="itemizedlist"><ul><li>Keycloak Authentication Server</li><li>Relational Database</li><li>Elasticsearch Datastore</li><li>apiman API Gateway</li><li>apiman API Manager</li></ul></div><p>The image above should give you an idea of how they all fit together.</p></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_database"/>Chapter 3. Database</h2></div></div></div><p>You have a number of persistence options in both Keycloak and apiman, but this guide will focus on using an
-RDBMS instead of other options (e.g. Elasticsearch for apiman or mongodb for KC).</p><p>On a separate server, install a production ready database such as mysql, mariadb, or postresql.  You will
-want to create two schemas/databases:</p><div class="itemizedlist"><ul><li>keycloak</li><li>apiman</li></ul></div><p>Make sure your DB is accessible remotely and enable whatever security options you need (SSL, users/passwords).
-We recommend using two different users and permissioning them appropriately (e.g. create a "sa_apiman" account
-and a "sa_keycloak" account).</p><p>After creating the ‘apiman' database, you can initialize it using the appropriate DDL for the database you
-selected.  We currently support mysql5/mariadb and postgresql.  The DDLs for these databases can be found in
-the quickstart/overlay ZIP file, or you can grab them directly from github.  For example:</p><p><a class="ulink" href="https://github.com/apiman/apiman/tree/master/distro/data/src/main/resources/ddls">https://github.com/apiman/apiman/tree/master/distro/data/src/main/resources/ddls</a></p><p>Make sure you grab the right one for whichever version of apiman you are going to be installing (<span class="strong"><strong>hint</strong></span>: use
-the appropriate github tag).</p></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_elasticsearch"/>Chapter 4. Elasticsearch</h2></div></div></div><p>If you wish to enable metrics in apiman (who doesn’t?) you’ll need to install Elasticsearch.  This is
-because the API Gateway stores all metrics information in Elasticsearch (by default), and the API Manager
-queries that data to present analytics information in the UI.</p><p>Please see the Elasticsearch documentation for how to install and configure it in production.  Ultimately you
-will need Elasticsearch running in a well known and accessible location.  We also recommend you enable
-authentication (e.g. via Shield) and SSL.</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>The data in Elasticsearch is not backed up or stored in some other location - Elasticsearch is being
-used as the primary/canonical data store for the metrics information.  You may wish to configure backup
-procedures</p></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_keycloak"/>Chapter 5. Keycloak</h2></div></div></div><p>In production, it is typically useful to deploy Keycloak server as a standalone solution.  For more
-specific information about how to configure a standalone Keycloak server, see the Keycloak documentation:</p><p><a class="ulink" href="http://keycloak.github.io/docs/userguide/html/server-installation.html">http://keycloak.github.io/docs/userguide/html/server-installation.html</a></p><p>Once Keycloak is installed as a standalone server, you must configure the ‘apiman' realm.  This realm will
-be used for authentication into each of the apiman components (API Manager REST services, API Manager UI,
-API Gateway REST services, etc).</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>You can configure additional Keycloak Realms for use when using the apiman "Keycloak OAuth2 Policy".</p></div><p>Fortunately, apiman comes with a realm file you can import.  Simply log into your keycloak server and then
-create the apiman realm using this file:</p><p><a class="ulink" href="https://github.com/apiman/apiman/blob/master/distro/data/src/main/resources/data/apiman-realm.json">https://github.com/apiman/apiman/blob/master/distro/data/src/main/resources/data/apiman-realm.json</a></p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>The realm file contains some credentials/secrets that you may want to modify.  The defaults are obviously not secure.</p></div><p>Once you have created the apiman realm, you must use the keycloak UI to add your API Manager UI as a valid
-redirect URL for the ‘apimanui' client.  To do this, log into the keycloak admin console and choose the
-<span class="strong"><strong>apiman</strong></span> realm.  Next click "clients" in the left navigation, and choose <span class="strong"><strong>apimanui</strong></span> in the resulting list.
-From there you can add public URL if your API Manager UI to the list of "<span class="strong"><strong><span class="emphasis"><em>Valid Redirect URIs</em></span></strong></span>".  It might
-be something like:</p><pre class="literallayout">https://apimanager.mycompany.org:8443/apimanui/*</pre><p>That will allow users of the API Manager UI to actually log in and be properly redirected back to the
-application!</p></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_api_gateway"/>Chapter 6. API Gateway</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#_installing_the_api_gateway">6.1. Installing the API Gateway</a></span></dt><dt><span class="section"><a href="#_configuring_the_api_gateway">6.2. Configuring the API Gateway</a></span></dt><dd><dl><dt><span class="section"><a href="#_disabling_the_keycloak_server">6.2.1. Disabling the Keycloak Server</a></span></dt><dt><span class="section"><a href="#_setting_the_api_gateway_public_endpoint">6.2.2. Setting the API Gateway Public Endpoint</a></span></dt><dt><span class="section"><a href="#_configuring_keycloak_authentication_for_the_gateway_api">6.2.3. Configuring Keycloak Authentication for the Gateway API</a></span></dt><dt><span class="section"><a href="#_pointing_the_api_gateway_to_a_remote_elasticsearch">6.2.4. Pointing the API Gateway to a Remote Elasticsearch</a></span></dt></dl></dd></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_installing_the_api_gateway"/>6.1. Installing the API Gateway</h2></div></div></div><p>The easiest way to install just the API Gateway is to download and install the apiman quickstart overlay
-and then remove the extraneous components.  Follow that up with some modification of the apiman.properties
-configuration file and you’ll be Gatewaying in no time!</p><p>Here are the steps you should take to install a standalone API Gateway:</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="orderedlist"><ol><li>Download and unpack WildFly</li><li>Download apiman</li><li>Unpack apiman into WildFly</li><li>Remove unused apiman deployments from standalone/deployments</li></ol></div><p>Which apiman deployments should you delete?  These:</p><pre class="literallayout">standalone/deployments/apiman-ds.xml
+        PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><title xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory">Guide - Deploying for Production</title><link rel="stylesheet" href="css/jbossorg.css" type="text/css"/><meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" name="generator" content="DocBook XSL-NS Stylesheets V1.74.0"/><meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" http-equiv="Content-Type" content="text/html; charset=UTF-8"/></head><body><div class="book" lang="en-US"><div class="titlepage"><div><p xmlns:d="http://docbook.org/ns/docbook" id="title"><a href="http://www.jboss.org" class="site_href"><strong>JBoss.org</strong></a><a href="http://docs.jboss.org/" class="doc_href"><strong>Community Documentation</strong></a></p><div><h1 class="title"><a id="d0e3"/>Guide - Deploying for Production</h1></div><div><h2 class="subtitle">apiman 1.1.9.Final</h2></div></div><hr/></div><div class="toc"><dl><dt><span class="chapter"><a href="#_deployment_tooling_for_apiman">1. Deployment Tooling for apiman</a></span></dt><dt><span class="chapter"><a href="#_architecture_summary">2. Architecture Summary</a></span></dt><dt><span class="chapter"><a href="#_database">3. Database</a></span></dt><dt><span class="chapter"><a href="#_elasticsearch">4. Elasticsearch</a></span></dt><dt><span class="chapter"><a href="#_keycloak">5. Keycloak</a></span></dt><dt><span class="chapter"><a href="#_api_gateway">6. API Gateway</a></span></dt><dd><dl><dt><span class="section"><a href="#_installing_the_api_gateway">6.1. Installing the API Gateway</a></span></dt><dt><span class="section"><a href="#_configuring_the_api_gateway">6.2. Configuring the API Gateway</a></span></dt><dd><dl><dt><span class="section"><a href="#_disabling_the_keycloak_server">6.2.1. Disabling the Keycloak Server</a></span></dt><dt><span class="section"><a href="#_setting_the_api_gateway_public_endpoint">6.2.2. Setting the API Gateway Public Endpoint</a></span></dt><dt><span class="section"><a href="#_configuring_keycloak_authentication_for_the_gateway_api">6.2.3. Configuring Keycloak Authentication for the Gateway API</a></span></dt><dt><span class="section"><a href="#_pointing_the_api_gateway_to_a_remote_elasticsearch">6.2.4. Pointing the API Gateway to a Remote Elasticsearch</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#_api_manager">7. API Manager</a></span></dt><dd><dl><dt><span class="section"><a href="#_installing_the_api_manager">7.1. Installing the API Manager</a></span></dt><dt><span class="section"><a href="#_configuring_the_api_manager">7.2. Configuring the API Manager</a></span></dt><dd><dl><dt><span class="section"><a href="#_disabling_the_keycloak_server_2">7.2.1. Disabling the Keycloak Server</a></span></dt><dt><span class="section"><a href="#_connecting_to_the_database">7.2.2. Connecting to the Database</a></span></dt><dt><span class="section"><a href="#_point_the_api_manager_to_the_api_gateway">7.2.3. Point the API Manager to the API Gateway</a></span></dt><dt><span class="section"><a href="#_configuring_keycloak_authentication_for_the_manager_api_and_ui">7.2.4. Configuring Keycloak Authentication for the Manager API and UI</a></span></dt><dt><span class="section"><a href="#_pointing_the_api_manager_to_a_remote_elasticsearch">7.2.5. Pointing the API Manager to a Remote Elasticsearch</a></span></dt></dl></dd></dl></dd></dl></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_deployment_tooling_for_apiman"/>Chapter 1. Deployment Tooling for apiman</h2></div></div></div><p>This guide should serve as a guide to manually deploy apiman into production.  However, we also offer a
+    simple shell script that can do much of the work for you.  It will likely always be a work in progress,
+    so many production deployers may not feel comfortable using it.  However, it can currently install the
+    following components:</p><div class="itemizedlist"><ul><li>Elasticsearch</li><li>Keycloak</li><li>API Manager</li><li>API Gateway</li></ul></div><p>You can find the apiman production deployer here:</p><p><a class="ulink" href="https://github.com/apiman/apiman-deployer/tree/apiman-1.1.9.Final">https://github.com/apiman/apiman-deployer/tree/apiman-1.1.9.Final</a></p><p>Simply download that script and run it on each of the machines you wish to install the various apiman
+    components!</p></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_architecture_summary"/>Chapter 2. Architecture Summary</h2></div></div></div><p>Before we get started, it may be useful to know the overall architecture of apiman.  Let’s start with a
+    picture!</p><h5 xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="formalpara">Architecture of apiman</h5><p class="formalpara"><span class="inlinemediaobject"><img src="images/images/apiman-architecture.png" alt="Architecture of apiman"/></span></p><p>The apiman solution is made up of a number of pieces, including:</p><div class="itemizedlist"><ul><li>Keycloak Authentication Server</li><li>Relational Database</li><li>Elasticsearch Datastore</li><li>apiman API Gateway</li><li>apiman API Manager</li></ul></div><p>The image above should give you an idea of how they all fit together.</p></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_database"/>Chapter 3. Database</h2></div></div></div><p>You have a number of persistence options in both Keycloak and apiman, but this guide will focus on using an
+    RDBMS instead of other options (e.g. Elasticsearch for apiman or mongodb for KC).</p><p>On a separate server, install a production ready database such as mysql, mariadb, or postresql.  You will
+    want to create two schemas/databases:</p><div class="itemizedlist"><ul><li>keycloak</li><li>apiman</li></ul></div><p>Make sure your DB is accessible remotely and enable whatever security options you need (SSL, users/passwords).
+    We recommend using two different users and permissioning them appropriately (e.g. create a "sa_apiman" account
+    and a "sa_keycloak" account).</p><p>After creating the ‘apiman' database, you can initialize it using the appropriate DDL for the database you
+    selected.  We currently support mysql5/mariadb and postgresql.  The DDLs for these databases can be found in
+    the quickstart/overlay ZIP file, or you can grab them directly from github.  For example:</p><p><a class="ulink" href="https://github.com/apiman/apiman/tree/master/distro/wildfly8/src/main/resources/overlay/apiman/ddls">https://github.com/apiman/apiman/tree/master/distro/wildfly8/src/main/resources/overlay/apiman/ddls</a></p><p>Make sure you grab the right one for whichever version of apiman you are going to be installing (<span class="strong"><strong>hint</strong></span>: use
+    the appropriate github tag).</p></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_elasticsearch"/>Chapter 4. Elasticsearch</h2></div></div></div><p>If you wish to enable metrics in apiman (who doesn’t?) you’ll need to install Elasticsearch.  This is
+    because the API Gateway stores all metrics information in Elasticsearch (by default), and the API Manager
+    queries that data to present analytics information in the UI.</p><p>Please see the Elasticsearch documentation for how to install and configure it in production.  Ultimately you
+    will need Elasticsearch running in a well known and accessible location.  We also recommend you enable
+    authentication (e.g. via Shield) and SSL.</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>The data in Elasticsearch is not backed up or stored in some other location - Elasticsearch is being
+    used as the primary/canonical data store for the metrics information.  You may wish to configure backup
+    procedures</p></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_keycloak"/>Chapter 5. Keycloak</h2></div></div></div><p>In production, it is typically useful to deploy Keycloak server as a standalone solution.  For more
+    specific information about how to configure a standalone Keycloak server, see the Keycloak documentation:</p><p><a class="ulink" href="http://keycloak.github.io/docs/userguide/html/server-installation.html">http://keycloak.github.io/docs/userguide/html/server-installation.html</a></p><p>Once Keycloak is installed as a standalone server, you must configure the ‘apiman' realm.  This realm will
+    be used for authentication into each of the apiman components (API Manager REST services, API Manager UI,
+    API Gateway REST services, etc).</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>You can configure additional Keycloak Realms for use when using the apiman "Keycloak OAuth2 Policy".</p></div><p>Fortunately, apiman comes with a realm file you can import.  Simply log into your keycloak server and then
+    create the apiman realm using this file:</p><p><a class="ulink" href="https://github.com/apiman/apiman/blob/master/distro/data/src/main/resources/data/apiman-realm.json">https://github.com/apiman/apiman/blob/master/distro/data/src/main/resources/data/apiman-realm.json</a></p><p>Once you have created the apiman realm, you must use the keycloak UI to add your API Manager UI as a valid
+    redirect URL for the ‘apimanui' client.  To do this, log into the keycloak admin console and choose the
+    <span class="strong"><strong>apiman</strong></span> realm.  Next click "clients" in the left navigation, and choose <span class="strong"><strong>apimanui</strong></span> in the resulting list.
+    From there you can add public URL if your API Manager UI to the list of "<span class="strong"><strong><span class="emphasis"><em>Valid Redirect URIs</em></span></strong></span>".  It might
+    be something like:</p><pre class="literallayout">https://apimanager.mycompany.org:8443/apimanui/*</pre><p>That will allow users of the API Manager UI to actually log in and be properly redirected back to the
+    application!</p></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_api_gateway"/>Chapter 6. API Gateway</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#_installing_the_api_gateway">6.1. Installing the API Gateway</a></span></dt><dt><span class="section"><a href="#_configuring_the_api_gateway">6.2. Configuring the API Gateway</a></span></dt><dd><dl><dt><span class="section"><a href="#_disabling_the_keycloak_server">6.2.1. Disabling the Keycloak Server</a></span></dt><dt><span class="section"><a href="#_setting_the_api_gateway_public_endpoint">6.2.2. Setting the API Gateway Public Endpoint</a></span></dt><dt><span class="section"><a href="#_configuring_keycloak_authentication_for_the_gateway_api">6.2.3. Configuring Keycloak Authentication for the Gateway API</a></span></dt><dt><span class="section"><a href="#_pointing_the_api_gateway_to_a_remote_elasticsearch">6.2.4. Pointing the API Gateway to a Remote Elasticsearch</a></span></dt></dl></dd></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_installing_the_api_gateway"/>6.1. Installing the API Gateway</h2></div></div></div><p>The easiest way to install just the API Gateway is to download and install the apiman quickstart overlay
+    and then remove the extraneous components.  Follow that up with some modification of the apiman.properties
+    configuration file and you’ll be Gatewaying in no time!</p><p>Here are the steps you should take to install a standalone API Gateway:</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="orderedlist"><ol><li>Download and unpack WildFly</li><li>Download apiman</li><li>Unpack apiman into WildFly</li><li>Remove unused apiman deployments from standalone/deployments</li></ol></div><p>Which apiman deployments should you delete?  These:</p><pre class="literallayout">standalone/deployments/apiman-ds.xml
 standalone/deployments/apiman-es.war
 standalone/deployments/apiman.war
-standalone/deployments/apimanui.war</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_configuring_the_api_gateway"/>6.2. Configuring the API Gateway</h2></div></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_disabling_the_keycloak_server"/>6.2.1. Disabling the Keycloak Server</h3></div></div></div><p>Because you will be using an external/standalone Keycloak server, it is useful to disable the Keycloak
-components that are bundled with the apiman quickstart.  To do that, make the following modification to
-the <span class="strong"><strong>standalone-apiman.xml</strong></span> file:</p><pre xmlns="" xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="XML"><!-- XML : generated by JHighlight v1.0 (http://jhighlight.dev.java.net) -->
+standalone/deployments/apimanui.war</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_configuring_the_api_gateway"/>6.2. Configuring the API Gateway</h2></div></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_disabling_the_keycloak_server"/>6.2.1. Disabling the Keycloak Server</h3></div></div></div><p>Because you will be using an external/standalone Keycloak server, it is useful to disable the Keycloak
+    components that are bundled with the apiman quickstart.  To do that, make the following modification to
+    the <span class="strong"><strong>standalone-apiman.xml</strong></span> file:</p><pre xmlns="" xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="XML"><!-- XML : generated by JHighlight v1.0 (http://jhighlight.dev.java.net) -->
 <span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">subsystem</span><span class="xml_plain">&nbsp;</span><span class="xml_attribute_name">xmlns</span><span class="xml_tag_symbols">=</span><span class="xml_attribute_value">&quot;urn:jboss:domain:keycloak:1.0&quot;</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_plain">&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">auth-server</span><span class="xml_plain">&nbsp;</span><span class="xml_attribute_name">name</span><span class="xml_tag_symbols">=</span><span class="xml_attribute_value">&quot;main-auth-server&quot;</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_plain">&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">enabled</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain">false</span><span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">enabled</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_plain">&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">web-context</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain">auth</span><span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">web-context</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_plain">&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">auth-server</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">subsystem</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
-</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_setting_the_api_gateway_public_endpoint"/>6.2.2. Setting the API Gateway Public Endpoint</h3></div></div></div><p>An important step is to let the API Gateway know what its public endpoint is.  This is important because
-the API Manager will sometimes ask the Gateway to report on the Managed Endpoint for a published API.</p><p>To set the public URL/endpoint of the API Gateway, add the following to apiman.properties:</p><pre class="literallayout">apiman-gateway.public-endpoint=https://api-gateway-host.org:8443/apiman-gateway/</pre><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="warning"><h2>Warning</h2><p>Please make sure to use your appropriate values for the host and port.</p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_configuring_keycloak_authentication_for_the_gateway_api"/>6.2.3. Configuring Keycloak Authentication for the Gateway API</h3></div></div></div><p>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 apiman quickstart assumes that the keycloak
-server is local, so you’ll need to modify the <span class="strong"><strong>standalone-apiman.xml</strong></span> file to point to the remote Keycloak
-instance.</p><p>Here is the relevant portion of the <span class="strong"><strong>standalone-apiman.xml</strong></span> file that you must change:</p><pre xmlns="" xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="XML"><!-- XML : generated by JHighlight v1.0 (http://jhighlight.dev.java.net) -->
+</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_setting_the_api_gateway_public_endpoint"/>6.2.2. Setting the API Gateway Public Endpoint</h3></div></div></div><p>An important step is to let the API Gateway know what its public endpoint is.  This is important because
+    the API Manager will sometimes ask the Gateway to report on the Managed Endpoint for a published service.</p><p>To set the public URL/endpoint of the API Gateway, add the following to apiman.properties:</p><pre class="literallayout">apiman-gateway.public-endpoint=https://api-gateway-host.org:8443/apiman-gateway/</pre><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="warning"><h2>Warning</h2><p>Please make sure to use your appropriate values for the host and port.</p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_configuring_keycloak_authentication_for_the_gateway_api"/>6.2.3. Configuring Keycloak Authentication for the Gateway API</h3></div></div></div><p>The API Gateway has a REST based configuration API which the API Manager uses when publishing services to
+    it.  This API is protected by Keycloak authentication.  The apiman quickstart assumes that the keycloak
+    server is local, so you’ll need to modify the <span class="strong"><strong>standalone-apiman.xml</strong></span> file to point to the remote Keycloak
+    instance.</p><p>Here is the relevant portion of the <span class="strong"><strong>standalone-apiman.xml</strong></span> file that you must change:</p><pre xmlns="" xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="XML"><!-- XML : generated by JHighlight v1.0 (http://jhighlight.dev.java.net) -->
 <span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">kc:realm</span><span class="xml_plain">&nbsp;</span><span class="xml_attribute_name">xmlns:kc</span><span class="xml_tag_symbols">=</span><span class="xml_attribute_value">&quot;urn:jboss:domain:keycloak:1.0&quot;</span><span class="xml_plain">&nbsp;</span><span class="xml_attribute_name">name</span><span class="xml_tag_symbols">=</span><span class="xml_attribute_value">&quot;apiman&quot;</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_plain">&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">kc:realm-public-key</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain">MIGf..snip..QAB</span><span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">kc:realm-public-key</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_plain">&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">kc:auth-server-url</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain">https://keycloak-host.org:8443/auth</span><span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">kc:auth-server-url</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
@@ -54,43 +54,43 @@
 <span class="xml_plain">&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">kc:enable-cors</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain">false</span><span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">kc:enable-cors</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_plain">&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">kc:principal-attribute</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain">preferred_username</span><span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">kc:principal-attribute</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">kc:realm</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
-</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_pointing_the_api_gateway_to_a_remote_elasticsearch"/>6.2.4. Pointing the API Gateway to a Remote Elasticsearch</h3></div></div></div><p>The API Gateway uses Elasticsearch in a number of ways, including:</p><div class="itemizedlist"><ul><li>Storing configuration information</li><li>Managing shared state across a cluster</li><li>Storing metrics to share with the API Manager  (analytics)</li></ul></div><p>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 <span class="strong"><strong>apiman.properties</strong></span> file:</p><pre class="literallayout">apiman.es.protocol=http
+</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_pointing_the_api_gateway_to_a_remote_elasticsearch"/>6.2.4. Pointing the API Gateway to a Remote Elasticsearch</h3></div></div></div><p>The API Gateway uses Elasticsearch in a number of ways, including:</p><div class="itemizedlist"><ul><li>Storing configuration information</li><li>Managing shared state across a cluster</li><li>Storing metrics to share with the API Manager  (analytics)</li></ul></div><p>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 <span class="strong"><strong>apiman.properties</strong></span> file:</p><pre class="literallayout">apiman.es.protocol=http
 apiman.es.host=es.myorg.com
 apiman.es.port=9200
 apiman.es.username=es_admin
 apiman.es.password=es_admin_password</pre><p>Obviously you will need to replace the values in the properties above with those appropriate for your
-installation of elasticsearch.</p></div></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_api_manager"/>Chapter 7. API Manager</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#_installing_the_api_manager">7.1. Installing the API Manager</a></span></dt><dt><span class="section"><a href="#_configuring_the_api_manager">7.2. Configuring the API Manager</a></span></dt><dd><dl><dt><span class="section"><a href="#_disabling_the_keycloak_server_2">7.2.1. Disabling the Keycloak Server</a></span></dt><dt><span class="section"><a href="#_connecting_to_the_database">7.2.2. Connecting to the Database</a></span></dt><dt><span class="section"><a href="#_point_the_api_manager_to_the_api_gateway">7.2.3. Point the API Manager to the API Gateway</a></span></dt><dt><span class="section"><a href="#_configuring_keycloak_authentication_for_the_manager_api_and_ui">7.2.4. Configuring Keycloak Authentication for the Manager API and UI</a></span></dt><dt><span class="section"><a href="#_pointing_the_api_manager_to_a_remote_elasticsearch">7.2.5. Pointing the API Manager to a Remote Elasticsearch</a></span></dt></dl></dd></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_installing_the_api_manager"/>7.1. Installing the API Manager</h2></div></div></div><p>The easiest way to install just the API Manager is to download and install the apiman quickstart overlay
-and then remove the extraneous components.  Follow that up with a few configuration modifications, and
-you should have the Manager running in no time!</p><p>Here are the steps you should take to install a standalone API Manager:</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="orderedlist"><ol><li>Download and unpack WildFly</li><li>Download apiman</li><li>Unpack apiman into WildFly</li><li>Remove unused apiman deployments from standalone/deployments</li></ol></div><p>Which apiman deployments should you delete?  These:</p><pre class="literallayout">standalone/deployments/apiman-es.war
+    installation of elasticsearch.</p></div></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_api_manager"/>Chapter 7. API Manager</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#_installing_the_api_manager">7.1. Installing the API Manager</a></span></dt><dt><span class="section"><a href="#_configuring_the_api_manager">7.2. Configuring the API Manager</a></span></dt><dd><dl><dt><span class="section"><a href="#_disabling_the_keycloak_server_2">7.2.1. Disabling the Keycloak Server</a></span></dt><dt><span class="section"><a href="#_connecting_to_the_database">7.2.2. Connecting to the Database</a></span></dt><dt><span class="section"><a href="#_point_the_api_manager_to_the_api_gateway">7.2.3. Point the API Manager to the API Gateway</a></span></dt><dt><span class="section"><a href="#_configuring_keycloak_authentication_for_the_manager_api_and_ui">7.2.4. Configuring Keycloak Authentication for the Manager API and UI</a></span></dt><dt><span class="section"><a href="#_pointing_the_api_manager_to_a_remote_elasticsearch">7.2.5. Pointing the API Manager to a Remote Elasticsearch</a></span></dt></dl></dd></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_installing_the_api_manager"/>7.1. Installing the API Manager</h2></div></div></div><p>The easiest way to install just the API Manager is to download and install the apiman quickstart overlay
+    and then remove the extraneous components.  Follow that up with a few configuration modifications, and
+    you should have the Manager running in no time!</p><p>Here are the steps you should take to install a standalone API Manager:</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="orderedlist"><ol><li>Download and unpack WildFly</li><li>Download apiman</li><li>Unpack apiman into WildFly</li><li>Remove unused apiman deployments from standalone/deployments</li></ol></div><p>Which apiman deployments should you delete?  These:</p><pre class="literallayout">standalone/deployments/apiman-es.war
 standalone/deployments/apiman-gateway-api.war
-standalone/deployments/apiman-gateway.war</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_configuring_the_api_manager"/>7.2. Configuring the API Manager</h2></div></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_disabling_the_keycloak_server_2"/>7.2.1. Disabling the Keycloak Server</h3></div></div></div><p>Because you will be using an external/standalone Keycloak server, it is useful to disable the Keycloak
-components that are bundled with the apiman quickstart.  To do that, make the following modification to
-the <span class="strong"><strong>standalone-apiman.xml</strong></span> file:</p><pre xmlns="" xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="XML"><!-- XML : generated by JHighlight v1.0 (http://jhighlight.dev.java.net) -->
+standalone/deployments/apiman-gateway.war</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_configuring_the_api_manager"/>7.2. Configuring the API Manager</h2></div></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_disabling_the_keycloak_server_2"/>7.2.1. Disabling the Keycloak Server</h3></div></div></div><p>Because you will be using an external/standalone Keycloak server, it is useful to disable the Keycloak
+    components that are bundled with the apiman quickstart.  To do that, make the following modification to
+    the <span class="strong"><strong>standalone-apiman.xml</strong></span> file:</p><pre xmlns="" xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="XML"><!-- XML : generated by JHighlight v1.0 (http://jhighlight.dev.java.net) -->
 <span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">subsystem</span><span class="xml_plain">&nbsp;</span><span class="xml_attribute_name">xmlns</span><span class="xml_tag_symbols">=</span><span class="xml_attribute_value">&quot;urn:jboss:domain:keycloak:1.0&quot;</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_plain">&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">auth-server</span><span class="xml_plain">&nbsp;</span><span class="xml_attribute_name">name</span><span class="xml_tag_symbols">=</span><span class="xml_attribute_value">&quot;main-auth-server&quot;</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_plain">&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">enabled</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain">false</span><span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">enabled</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_plain">&nbsp;&nbsp;&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">web-context</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain">auth</span><span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">web-context</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_plain">&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">auth-server</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">subsystem</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
-</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_connecting_to_the_database"/>7.2.2. Connecting to the Database</h3></div></div></div><p>This guide assumes you are using a production ready RDBMS as the storage layer for the API Manager.  Note
-that other options exist, but configuring them is out of scope for this guide.</p><p>Hopefully you’ve already created and initialized the database in the earlier section labeled "<span class="emphasis"><em>Installing a
-Database</em></span>".  So at this point you really only need to connect the API Manager up to the already existing
-database.  The following must be done in order to connect to your database:</p><div class="itemizedlist"><ul><li>Deploy a JDBC driver compatible with your database</li><li>Update the <span class="strong"><strong>apiman-ds.xml</strong></span> datasource file (to point it at your database)</li><li>Update the hibernate dialect in <span class="strong"><strong>apiman.properties</strong></span></li></ul></div><p>First, you will need to deploy a JDBC driver that is compatible with whichever database you have chosen.
-Here are two popular drivers:</p><p><span class="emphasis"><em>*MySQL 5*</em></span></p><p><a class="ulink" href="https://repo1.maven.org/maven2/mysql/mysql-connector-java/5.1.33/mysql-connector-java-5.1.33.jar">https://repo1.maven.org/maven2/mysql/mysql-connector-java/5.1.33/mysql-connector-java-5.1.33.jar</a></p><p><span class="emphasis"><em>*Postgresql 9*</em></span></p><p><a class="ulink" href="https://repo1.maven.org/maven2/org/postgresql/postgresql/9.3-1102-jdbc41/postgresql-9.3-1102-jdbc41.jar">https://repo1.maven.org/maven2/org/postgresql/postgresql/9.3-1102-jdbc41/postgresql-9.3-1102-jdbc41.jar</a></p><p>The easiest way to deploy the driver is to simply download it and copy it into the
-<span class="strong"><strong>wildfly/standalone/deployments</strong></span> directory.</p><p>Next, you must update or replace the <span class="strong"><strong>apiman-ds.xml</strong></span> file to something that is configured for your
- particular database.  Examples of appropriate datasource files for mysql and postgresql can be found here:</p><p><a class="ulink" href="https://github.com/apiman/apiman/tree/master/distro/data/src/main/resources/sample-configs">https://github.com/apiman/apiman/tree/master/distro/data/src/main/resources/sample-configs</a></p><p>These examples are also included in the apiman quickstart/overlay ZIP download.</p><p>Finally you must update the <span class="strong"><strong>apiman.properties</strong></span> file to configure the hibernate dialect for your database.
-Popular dialects for mysql and postgresql are:</p><div class="itemizedlist"><ul><li><span class="emphasis"><em>*MySQL 5*</em></span>: org.hibernate.dialect.MySQL5Dialect</li><li><span class="emphasis"><em>*Postgresql 9*</em></span>: org.hibernate.dialect.PostgreSQLDialect</li></ul></div><p>Here is the line you should change in the <span class="strong"><strong>apiman.properties</strong></span> file:</p><pre class="literallayout">apiman.hibernate.dialect=io.apiman.manager.api.jpa.ApimanH2Dialect</pre><p>Change the value of that property to the appropriate dialect for your database.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_point_the_api_manager_to_the_api_gateway"/>7.2.3. Point the API Manager to the API Gateway</h3></div></div></div><p>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:</p><p><a class="ulink" href="https://api-manager-host.org:8443/apimanui/api-manager/admin/gateways">https://api-manager-host.org:8443/apimanui/api-manager/admin/gateways</a></p><p>From there you will be able to click on the gateway and modify its settings.  Make sure to use the <span class="strong"><strong>Test</strong></span>
-button on the Edit Gateway UI page to make sure you got the settings right!  Don’t worry, the <span class="strong"><strong>Test</strong></span> button
-will simply try to make a connection to the API Gateway’s configuration URL, asking it for the current
-Gateway status.  If the Gateway responds as expected, then you can be confident that your settings are
-correct.</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>You will need to log into the UI.  The default credentials are:  admin/admin123!</p></div><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>You may have changed the default user credentials when you installed and configured keycloak.  If
-so, make sure you use those credentials.</p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_configuring_keycloak_authentication_for_the_manager_api_and_ui"/>7.2.4. Configuring Keycloak Authentication for the Manager API and UI</h3></div></div></div><p>The API Manager has a REST based API which the User Interface uses for all actions taken.  It can also be
-used directly for automation and/or integration purposes.  This API is protected by Keycloak authentication.
-The apiman quickstart assumes that the keycloak server is local, so you’ll need to modify the
-<span class="strong"><strong>standalone-apiman.xml</strong></span> file to point to the remote Keycloak instance.</p><p>Here is the relevant portion of the <span class="strong"><strong>standalone-apiman.xml</strong></span> file that you must change:</p><pre xmlns="" xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="XML"><!-- XML : generated by JHighlight v1.0 (http://jhighlight.dev.java.net) -->
+</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_connecting_to_the_database"/>7.2.2. Connecting to the Database</h3></div></div></div><p>This guide assumes you are using a production ready RDBMS as the storage layer for the API Manager.  Note
+    that other options exist, but configuring them is out of scope for this guide.</p><p>Hopefully you’ve already created and initialized the database in the earlier section labeled "<span class="emphasis"><em>Installing a
+    Database</em></span>".  So at this point you really only need to connect the API Manager up to the already existing
+    database.  The following must be done in order to connect to your database:</p><div class="itemizedlist"><ul><li>Deploy a JDBC driver compatible with your database</li><li>Update the <span class="strong"><strong>apiman-ds.xml</strong></span> datasource file (to point it at your database)</li><li>Update the hibernate dialect in <span class="strong"><strong>apiman.properties</strong></span></li></ul></div><p>First, you will need to deploy a JDBC driver that is compatible with whichever database you have chosen.
+    Here are two popular drivers:</p><p><span class="emphasis"><em>*MySQL 5*</em></span></p><p><a class="ulink" href="https://repo1.maven.org/maven2/mysql/mysql-connector-java/5.1.33/mysql-connector-java-5.1.33.jar">https://repo1.maven.org/maven2/mysql/mysql-connector-java/5.1.33/mysql-connector-java-5.1.33.jar</a></p><p><span class="emphasis"><em>*Postgresql 9*</em></span></p><p><a class="ulink" href="https://repo1.maven.org/maven2/org/postgresql/postgresql/9.3-1102-jdbc41/postgresql-9.3-1102-jdbc41.jar">https://repo1.maven.org/maven2/org/postgresql/postgresql/9.3-1102-jdbc41/postgresql-9.3-1102-jdbc41.jar</a></p><p>The easiest way to deploy the driver is to simply download it and copy it into the
+    <span class="strong"><strong>wildfly/standalone/deployments</strong></span> directory.</p><p>Next, you must update or replace the <span class="strong"><strong>apiman-ds.xml</strong></span> file to something that is configured for your
+    particular database.  Examples of appropriate datasource files for mysql and postgresql can be found here:</p><p><a class="ulink" href="https://github.com/apiman/apiman/tree/master/distro/wildfly8/src/main/resources/overlay/apiman/sample-configs">https://github.com/apiman/apiman/tree/master/distro/wildfly8/src/main/resources/overlay/apiman/sample-configs</a></p><p>These examples are also included in the apiman quickstart/overlay ZIP download.</p><p>Finally you must update the <span class="strong"><strong>apiman.properties</strong></span> file to configure the hibernate dialect for your database.
+    Popular dialects for mysql and postgresql are:</p><div class="itemizedlist"><ul><li><span class="emphasis"><em>*MySQL 5*</em></span>: org.hibernate.dialect.MySQL5Dialect</li><li><span class="emphasis"><em>*Postgresql 9*</em></span>: org.hibernate.dialect.PostgreSQLDialect</li></ul></div><p>Here is the line you should change in the <span class="strong"><strong>apiman.properties</strong></span> file:</p><pre class="literallayout">apiman.hibernate.dialect=io.apiman.manager.api.jpa.ApimanH2Dialect</pre><p>Change the value of that property to the appropriate dialect for your database.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_point_the_api_manager_to_the_api_gateway"/>7.2.3. Point the API Manager to the API Gateway</h3></div></div></div><p>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:</p><p><a class="ulink" href="https://api-manager-host.org:8443/apimanui/api-manager/admin/gateways">https://api-manager-host.org:8443/apimanui/api-manager/admin/gateways</a></p><p>From there you will be able to click on the gateway and modify its settings.  Make sure to use the <span class="strong"><strong>Test</strong></span>
+    button on the Edit Gateway UI page to make sure you got the settings right!  Don’t worry, the <span class="strong"><strong>Test</strong></span> button
+    will simply try to make a connection to the API Gateway’s configuration URL, asking it for the current
+    Gateway status.  If the Gateway responds as expected, then you can be confident that your settings are
+    correct.</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>You will need to log into the UI.  The default credentials are:  admin/admin123!</p></div><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>You may have changed the default user credentials when you installed and configured keycloak.  If
+    so, make sure you use those credentials.</p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_configuring_keycloak_authentication_for_the_manager_api_and_ui"/>7.2.4. Configuring Keycloak Authentication for the Manager API and UI</h3></div></div></div><p>The API Manager has a REST based API which the User Interface uses for all actions taken.  It can also be
+    used directly for automation and/or integration purposes.  This API is protected by Keycloak authentication.
+    The apiman quickstart assumes that the keycloak server is local, so you’ll need to modify the
+    <span class="strong"><strong>standalone-apiman.xml</strong></span> file to point to the remote Keycloak instance.</p><p>Here is the relevant portion of the <span class="strong"><strong>standalone-apiman.xml</strong></span> file that you must change:</p><pre xmlns="" xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="XML"><!-- XML : generated by JHighlight v1.0 (http://jhighlight.dev.java.net) -->
 <span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">kc:realm</span><span class="xml_plain">&nbsp;</span><span class="xml_attribute_name">xmlns:kc</span><span class="xml_tag_symbols">=</span><span class="xml_attribute_value">&quot;urn:jboss:domain:keycloak:1.0&quot;</span><span class="xml_plain">&nbsp;</span><span class="xml_attribute_name">name</span><span class="xml_tag_symbols">=</span><span class="xml_attribute_value">&quot;apiman&quot;</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_plain">&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">kc:realm-public-key</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain">MIGf..snip..QAB</span><span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">kc:realm-public-key</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_plain">&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">kc:auth-server-url</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain">https://keycloak-host.org:8443/auth</span><span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">kc:auth-server-url</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
@@ -98,11 +98,11 @@
 <span class="xml_plain">&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">kc:enable-cors</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain">false</span><span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">kc:enable-cors</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_plain">&nbsp;&nbsp;</span><span class="xml_tag_symbols">&lt;</span><span class="xml_tag_name">kc:principal-attribute</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain">preferred_username</span><span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">kc:principal-attribute</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
 <span class="xml_tag_symbols">&lt;/</span><span class="xml_tag_name">kc:realm</span><span class="xml_tag_symbols">&gt;</span><span class="xml_plain"></span><br />
-</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_pointing_the_api_manager_to_a_remote_elasticsearch"/>7.2.5. Pointing the API Manager to a Remote Elasticsearch</h3></div></div></div><p>The API Manager uses Elasticsearch for analysis of metrics.  This metrics data is stored in Elasticsearch
-by the API Gateway whenever API requests are handled.  Therefore, the API Manager and API Gateway must
-talk to the same Elasticsearch instance/cluster.</p><p>To configure Elasticsearch for the API Manager, modify these properties in the <span class="strong"><strong>apiman.properties</strong></span> file:</p><pre class="literallayout">apiman.es.protocol=http
+</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_pointing_the_api_manager_to_a_remote_elasticsearch"/>7.2.5. Pointing the API Manager to a Remote Elasticsearch</h3></div></div></div><p>The API Manager uses Elasticsearch for analysis of metrics.  This metrics data is stored in Elasticsearch
+    by the API Gateway whenever API requests are handled.  Therefore, the API Manager and API Gateway must
+    talk to the same Elasticsearch instance/cluster.</p><p>To configure Elasticsearch for the API Manager, modify these properties in the <span class="strong"><strong>apiman.properties</strong></span> file:</p><pre class="literallayout">apiman.es.protocol=http
 apiman.es.host=es.myorg.com
 apiman.es.port=9200
 apiman.es.username=es_admin
 apiman.es.password=es_admin_password</pre><p>Obviously you will need to replace the values in the properties above with those appropriate for your
-installation of elasticsearch.</p></div></div></div></div></body></html>
\ No newline at end of file
+    installation of elasticsearch.</p></div></div></div></div></body></html>
\ No newline at end of file
diff --git a/latest/roadmap.html b/latest/roadmap.html
index 84c92431d..de31f5054 100644
--- a/latest/roadmap.html
+++ b/latest/roadmap.html
@@ -5,7 +5,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge">
     <meta name="viewport" content="width=device-width, initial-scale=1">
     <link rel="shortcut icon" href="resources/images/favicon.ico">
-    <title>apiman :: roadmap</title>
+    <title>Roadmap | apiman API Management</title>
 
     <link href="resources/bootstrap-3.3.0/css/bootstrap.min.css" rel="stylesheet">
     <link href="resources/patternfly-1.0.5/css/patternfly.min.css" rel="stylesheet">
@@ -35,8 +35,8 @@
   </head>
   <body class="roadmap">
     <div id="rhbar">
-      <a class="jbdevlogo" href="http://www.jboss.org/projects/about"></a>
-      <a class="rhlogo" href="http://www.redhat.com/"></a>
+      <a class="jbdevlogo" href="http://www.jboss.org/projects/about" rel="nofollow" target="_blank"></a>
+      <a class="rhlogo" href="http://www.redhat.com/" rel="nofollow" target="_blank"></a>
     </div>
     <nav id="top-nav" class="navbar navbar-inverse" role="navigation">
       <div class="container">
@@ -56,19 +56,19 @@
             <li class="top-menu-item menu-item active"><a href="roadmap.html">Roadmap</a></li>
             <li class="top-menu-item menu-item"><a href="/blog">Blog</a></li>
             <li class="top-menu-item menu-item dropdown">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Get Involved<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Get Involved<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
-                        <a href="https://issues.jboss.org/browse/APIMAN">Report a Bug</a>
+                        <a href="https://issues.jboss.org/browse/APIMAN" rel="nofollow" target="_blank">Report a Bug</a>
                     </li>
                     <li class="menu-item">
                         <a href="chat.html">Chat on IRC</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://twitter.com/apiman_io">Twitter Feed</a>
+                        <a href="https://twitter.com/apiman_io" rel="nofollow" target="_blank">Twitter Feed</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user">Mailing List</a>
+                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="nofollow" target="_blank">Mailing List</a>
                     </li>
                     <li class="divider"></li>
                     <li class="menu-item">
@@ -77,7 +77,7 @@
                 </ul>
             </li>
             <li class="top-menu-item menu-item dropdown">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Learn More<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Learn More<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
                         <a href="tutorials.html">Tutorials &amp; Walkthroughs</a>
@@ -125,7 +125,7 @@ <h1 class="section-header">Roadmap</h1>
                   Here you will find a very high level roadmap for the apiman project.  The details are
                   subject to change, but this page can provide a basic sense of the project's priorities
                   and version numbers.  Additional information can typically be found in
-                  <a href="https://issues.jboss.org/browse/APIMAN">JIRA</a>.
+                  <a href="https://issues.jboss.org/browse/APIMAN" rel="nofollow" target="_blank">JIRA</a>.
                 </p>
                 <p>
                   Typically there will be multiple iterative released within a major+minor version, with
@@ -188,18 +188,18 @@ <h2><a class="" data-toggle="collapse" href="#features1_0" aria-expanded="false"
                       <li><span class="completed">Clone a version (App, Service, Plan)</span> <span class="in-version">1.0.1.Final</span></li>
                       <li><span class="completed">Support "public" services (can be invoked without a Contract)</span> <span class="in-version">1.0.1.Final</span></li>
                       <li><span class="completed">Plugin framework - contribute policies</span> <span class="in-version">1.0.3.Final</span></li>
-                      <li><span class="completed">Plugin framework - contribute policy configuration forms based on <a href="http://json-schema.org/">JSON Schema</a></span> <span class="in-version">1.0.3.Final</span></li>
+                      <li><span class="completed">Plugin framework - contribute policy configuration forms based on <a href="http://json-schema.org/" rel="nofollow" target="_blank">JSON Schema</a></span> <span class="in-version">1.0.3.Final</span></li>
                     </ul>
                   </div>
                   <div class="col-lg-3 relnotes">
                     <!-- Version 1.0 -->
                     <h2>1.0 Release Notes</h2>
                     <div class="release-notes">
-                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12325096">1.0.0.Beta1</a> <span class="label-small">(2014 Nov 21)</span></div>
-                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12326282">1.0.0.Final</a> <span class="label-small">(2014 Dec 18)</span></div>
-                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12326467">1.0.1.Final</a> <span class="label-small">(2015 Jan 06)</span></div>
-                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12326491">1.0.2.Final</a> <span class="label-small">(2015 Jan 29)</span></div>
-                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12326633">1.0.3.Final</a> <span class="label-small">(2015 Feb 17)</span></div>
+                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12325096" rel="nofollow" target="_blank">1.0.0.Beta1</a> <span class="label-small">(2014 Nov 21)</span></div>
+                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12326282" rel="nofollow" target="_blank">1.0.0.Final</a> <span class="label-small">(2014 Dec 18)</span></div>
+                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12326467" rel="nofollow" target="_blank">1.0.1.Final</a> <span class="label-small">(2015 Jan 06)</span></div>
+                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12326491" rel="nofollow" target="_blank">1.0.2.Final</a> <span class="label-small">(2015 Jan 29)</span></div>
+                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12326633" rel="nofollow" target="_blank">1.0.3.Final</a> <span class="label-small">(2015 Feb 17)</span></div>
                     </div>
                   </div>
                 </div>
@@ -268,16 +268,16 @@ <h2 class=""><a class="" data-toggle="collapse" href="#features1_1" aria-expande
                   <div class="col-lg-3 relnotes">
                     <h2>1.1 Release Notes</h2>
                     <div class="release-notes">
-                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12326497">1.1.0.Final</a> <span class="label-small">(2015 April 11)</span></div>
-                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12326950">1.1.1.Final</a> <span class="label-small">(2015 April 22)</span></div>
-                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12327059">1.1.2.Final</a> <span class="label-small">(2015 May 7)</span></div>
-                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12327298">1.1.3.Final</a> <span class="label-small">(2015 June 2)</span></div>
-                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12327477">1.1.4.Final</a> <span class="label-small">(2015 July 6)</span></div>
-                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12327612">1.1.5.Final</a> <span class="label-small">(2015 July 22)</span></div>
-                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12327699">1.1.6.Final</a> <span class="label-small">(2015 Aug 14)</span></div>
-                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12327805">1.1.7.Final</a> <span class="label-small">(2015 Aug 21)</span></div>
-                      <div><a href="http://red.ht/1igFSrj">1.1.8.Final</a> <span class="label-small">(2015 Sep 10)</span></div>
-                      <div><a href="http://red.ht/1MJbBsx">1.1.9.Final</a> <span class="label-small">(2015 Oct 23)</span></div>
+                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12326497" rel="nofollow" target="_blank">1.1.0.Final</a> <span class="label-small">(2015 April 11)</span></div>
+                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12326950" rel="nofollow" target="_blank">1.1.1.Final</a> <span class="label-small">(2015 April 22)</span></div>
+                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12327059" rel="nofollow" target="_blank">1.1.2.Final</a> <span class="label-small">(2015 May 7)</span></div>
+                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12327298" rel="nofollow" target="_blank">1.1.3.Final</a> <span class="label-small">(2015 June 2)</span></div>
+                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12327477" rel="nofollow" target="_blank">1.1.4.Final</a> <span class="label-small">(2015 July 6)</span></div>
+                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12327612" rel="nofollow" target="_blank">1.1.5.Final</a> <span class="label-small">(2015 July 22)</span></div>
+                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12327699" rel="nofollow" target="_blank">1.1.6.Final</a> <span class="label-small">(2015 Aug 14)</span></div>
+                      <div><a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314121&version=12327805" rel="nofollow" target="_blank">1.1.7.Final</a> <span class="label-small">(2015 Aug 21)</span></div>
+                      <div><a href="http://red.ht/1igFSrj" rel="nofollow" target="_blank">1.1.8.Final</a> <span class="label-small">(2015 Sep 10)</span></div>
+                      <div><a href="http://red.ht/1MJbBsx" rel="nofollow" target="_blank">1.1.9.Final</a> <span class="label-small">(2015 Oct 23)</span></div>
                     </div>
                   </div>
                 </div>
@@ -413,14 +413,14 @@ <h2 class=""><a class="" data-toggle="collapse" href="#features1_3" aria-expande
                         <div class="textwidget">
                             <p>
                                 Copyright © 2015 Red Hat, Inc. All rights reserved.<br>
-                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License, v2.0</a>.<br>
+                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="nofollow" target="_blank">Apache License, v2.0</a>.<br>
                                 <a href="disclosure.html">Open Source Disclosure</a>
                             </p>
                         </div>
                     </div>
                     <div class="widget col-sm-6 col-md-6 widget_text" style="text-align: right">
 
-                        <a href="http://www.redhat.com"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png"></a>
+                        <a href="http://www.redhat.com" rel="nofollow" target="_blank"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png" alt="Red Hat"></a>
                     </div>
                 </div>
                 <nav class="clearfix"></nav>
diff --git a/latest/tutorials.html b/latest/tutorials.html
index c7b3bd564..27d628532 100644
--- a/latest/tutorials.html
+++ b/latest/tutorials.html
@@ -5,7 +5,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge">
     <meta name="viewport" content="width=device-width, initial-scale=1">
     <link rel="shortcut icon" href="resources/images/favicon.ico">
-    <title>apiman :: tutorials &amp; walkthroughs</title>
+    <title>Tutorials &amp; Walkthroughs | apiman Open Source API Management</title>
 
     <link href="resources/bootstrap-3.3.0/css/bootstrap.min.css" rel="stylesheet">
     <link href="resources/patternfly-1.0.5/css/patternfly.min.css" rel="stylesheet">
@@ -35,8 +35,8 @@
   </head>
   <body class="tutorials">
     <div id="rhbar">
-      <a class="jbdevlogo" href="http://www.jboss.org/projects/about"></a>
-      <a class="rhlogo" href="http://www.redhat.com/"></a>
+      <a class="jbdevlogo" href="http://www.jboss.org/projects/about" rel="nofollow" target="_blank"></a>
+      <a class="rhlogo" href="http://www.redhat.com/" rel="nofollow" target="_blank"></a>
     </div>
     <nav id="top-nav" class="navbar navbar-inverse" role="navigation">
       <div class="container">
@@ -56,19 +56,19 @@
             <li class="top-menu-item menu-item"><a href="roadmap.html">Roadmap</a></li>
             <li class="top-menu-item menu-item"><a href="/blog">Blog</a></li>
             <li class="top-menu-item menu-item dropdown">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Get Involved<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Get Involved<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
-                        <a href="https://issues.jboss.org/browse/APIMAN">Report a Bug</a>
+                        <a href="https://issues.jboss.org/browse/APIMAN" rel="nofollow" target="_blank">Report a Bug</a>
                     </li>
                     <li class="menu-item">
                         <a href="chat.html">Chat on IRC</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://twitter.com/apiman_io">Twitter Feed</a>
+                        <a href="https://twitter.com/apiman_io" rel="nofollow" target="_blank">Twitter Feed</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user">Mailing List</a>
+                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="nofollow" target="_blank">Mailing List</a>
                     </li>
                     <li class="divider"></li>
                     <li class="menu-item">
@@ -77,7 +77,7 @@
                 </ul>
             </li>
             <li class="top-menu-item menu-item dropdown active">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Learn More<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Learn More<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
                         <a href="tutorials.html">Tutorials &amp; Walkthroughs</a>
@@ -128,7 +128,7 @@ <h1 class="section-header">Tutorials &amp; Walkthroughs</h1>
                 </p>
                 <div class="alert alert-info">
                   <span class="pficon pficon-info"></span>
-                  <strong>Note:</strong> we are in the process of updating the tutorial videos to bring them up to date with the latest changes to apiman.  Please stay tuned!  If you are interested in watching the older videos, you can <a href="https://vimeo.com/user34396826/videos">find them on vimeo</a>.
+                  <strong>Note:</strong> we are in the process of updating the tutorial videos to bring them up to date with the latest changes to apiman.  Please stay tuned!  If you are interested in watching the older videos, you can <a href="https://vimeo.com/user34396826/videos" rel="nofollow" target="_blank">find them on vimeo</a>.
                 </div>
             </div>
 <!--             <div class="col-md-4 video"> -->
@@ -171,14 +171,14 @@ <h1 class="section-header">Tutorials &amp; Walkthroughs</h1>
                         <div class="textwidget">
                             <p>
                                 Copyright © 2015 Red Hat, Inc. All rights reserved.<br>
-                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License, v2.0</a>.<br> 
+                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="nofollow" target="_blank">Apache License, v2.0</a>.<br>
                                 <a href="disclosure.html">Open Source Disclosure</a> 
                             </p>
                         </div>
                     </div>
                     <div class="widget col-sm-6 col-md-6 widget_text" style="text-align: right">
                         
-                        <a href="http://www.redhat.com"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png"></a>
+                        <a href="http://www.redhat.com" rel="nofollow" target="_blank"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png" alt="Red Hat"></a>
                     </div>
                 </div>
                 <nav class="clearfix"></nav>
diff --git a/latest/user-guide.html b/latest/user-guide.html
index c8771bf0b..c3245cd06 100644
--- a/latest/user-guide.html
+++ b/latest/user-guide.html
@@ -5,7 +5,7 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge">
     <meta name="viewport" content="width=device-width, initial-scale=1">
     <link rel="shortcut icon" href="resources/images/favicon.ico">
-    <title>apiman :: user guide</title>
+    <title>User Guide | apiman Open Source API Management</title>
 
     <link href="resources/bootstrap-3.3.0/css/bootstrap.min.css" rel="stylesheet">
     <link href="resources/patternfly-1.0.5/css/patternfly.min.css" rel="stylesheet">
@@ -50,8 +50,8 @@
   </head>
   <body class="user-guide guide">
     <div id="rhbar">
-      <a class="jbdevlogo" href="http://www.jboss.org/projects/about"></a>
-      <a class="rhlogo" href="http://www.redhat.com/"></a>
+      <a class="jbdevlogo" href="http://www.jboss.org/projects/about" rel="nofollow" target="_blank"></a>
+      <a class="rhlogo" href="http://www.redhat.com/" rel="nofollow" target="_blank"></a>
     </div>
     <nav id="top-nav" class="navbar navbar-inverse" role="navigation">
       <div class="container">
@@ -71,19 +71,19 @@
             <li class="top-menu-item menu-item"><a href="roadmap.html">Roadmap</a></li>
             <li class="top-menu-item menu-item"><a href="/blog">Blog</a></li>
             <li class="top-menu-item menu-item dropdown">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Get Involved<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Get Involved<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
-                        <a href="https://issues.jboss.org/browse/APIMAN">Report a Bug</a>
+                        <a href="https://issues.jboss.org/browse/APIMAN" rel="nofollow" target="_blank">Report a Bug</a>
                     </li>
                     <li class="menu-item">
                         <a href="chat.html">Chat on IRC</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://twitter.com/apiman_io">Twitter Feed</a>
+                        <a href="https://twitter.com/apiman_io" rel="nofollow" target="_blank">Twitter Feed</a>
                     </li>
                     <li class="menu-item">
-                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user">Mailing List</a>
+                        <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="nofollow" target="_blank">Mailing List</a>
                     </li>
                     <li class="divider"></li>
                     <li class="menu-item">
@@ -92,7 +92,7 @@
                 </ul>
             </li>
             <li class="top-menu-item menu-item dropdown active">
-                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown">Learn More<b class="caret"></b></a>
+                <a href="https://www.patternfly.org/visual-styles/" class="dropdown-toggle" data-toggle="dropdown" rel="nofollow" target="_blank">Learn More<b class="caret"></b></a>
                 <ul class="dropdown-menu">
                     <li class="menu-item">
                         <a href="tutorials.html">Tutorials &amp; Walkthroughs</a>
@@ -147,14 +147,14 @@
                         <div class="textwidget">
                             <p>
                                 Copyright © 2015 Red Hat, Inc. All rights reserved.<br>
-                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License, v2.0</a>.<br> 
+                                apiman code is open source and released under <a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="nofollow" target="_blank">Apache License, v2.0</a>.<br>
                                 <a href="disclosure.html">Open Source Disclosure</a>
                             </p>
                         </div>
                     </div>
                     <div class="widget col-sm-6 col-md-6 widget_text" style="text-align: right">
                         
-                        <a href="http://www.redhat.com"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png"></a>
+                        <a href="http://www.redhat.com" rel="nofollow" target="_blank"><img src="http://static.jboss.org/theme/images/common/redhat_logo.png" alt="Red Hat"></a>
                     </div>
                 </div>
                 <nav class="clearfix"></nav>
diff --git a/latest/user-guide/index.html b/latest/user-guide/index.html
index ccb8af2de..83bb69db4 100644
--- a/latest/user-guide/index.html
+++ b/latest/user-guide/index.html
@@ -1,360 +1,1409 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><title xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory">apiman - User Guide</title><link rel="stylesheet" href="css/jbossorg.css" type="text/css"/><meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" name="generator" content="DocBook XSL-NS Stylesheets V1.74.0"/><meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" http-equiv="Content-Type" content="text/html; charset=UTF-8"/></head><body><div class="book" lang="en-US"><div class="titlepage"><div><p xmlns:d="http://docbook.org/ns/docbook" id="title"><a href="http://www.jboss.org" class="site_href"><strong>JBoss.org</strong></a><a href="http://docs.jboss.org/" class="doc_href"><strong>Community Documentation</strong></a></p><div><h1 class="title"><a id="d0e3"/>apiman - User Guide</h1></div></div><hr/></div><div class="toc"><dl><dt><span class="chapter"><a href="#_introduction">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="#_what_is_api_management">1.1. What is API Management?</a></span></dt><dt><span class="section"><a href="#_project_goals">1.2. Project Goals</a></span></dt><dt><span class="section"><a href="#_typical_use_cases">1.3. Typical Use Cases</a></span></dt><dd><dl><dt><span class="section"><a href="#_security">1.3.1. Security</a></span></dt><dt><span class="section"><a href="#_throttling_rate_limiting">1.3.2. Throttling/Rate Limiting</a></span></dt><dt><span class="section"><a href="#_metering_billing">1.3.3. Metering/Billing</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#_crash_course">2. Crash Course</a></span></dt><dd><dl><dt><span class="section"><a href="#_organizations">2.1. Organizations</a></span></dt><dt><span class="section"><a href="#_providing_public_apis">2.2. Providing Public APIs</a></span></dt><dd><dl><dt><span class="section"><a href="#_public_api">2.2.1. Public API</a></span></dt><dt><span class="section"><a href="#_sending_requests_to_your_public_api">2.2.2. Sending Requests to your Public API</a></span></dt></dl></dd><dt><span class="section"><a href="#_providing_apis">2.3. Providing APIs`</a></span></dt><dd><dl><dt><span class="section"><a href="#_plans">2.3.1. Plans</a></span></dt><dt><span class="section"><a href="#_apis">2.3.2. APIs</a></span></dt></dl></dd><dt><span class="section"><a href="#_consuming_apis">2.4. Consuming APIs</a></span></dt><dd><dl><dt><span class="section"><a href="#_client_apps">2.4.1. Client Apps</a></span></dt><dt><span class="section"><a href="#_sending_requests">2.4.2. Sending Requests</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#_api_manager">3. API Manager</a></span></dt><dd><dl><dt><span class="section"><a href="#_data_model">3.1. Data Model</a></span></dt><dd><dl><dt><span class="section"><a href="#_organizations_2">3.1.1. Organizations</a></span></dt><dt><span class="section"><a href="#_policies">3.1.2. Policies</a></span></dt><dt><span class="section"><a href="#_plans_2">3.1.3. Plans</a></span></dt><dt><span class="section"><a href="#_apis_2">3.1.4. APIs</a></span></dt><dt><span class="section"><a href="#_client_apps_2">3.1.5. Client Apps</a></span></dt><dt><span class="section"><a href="#_api_contracts">3.1.6. API Contracts</a></span></dt><dt><span class="section"><a href="#_policy_chain">3.1.7. Policy Chain</a></span></dt></dl></dd><dt><span class="section"><a href="#_user_management">3.2. User Management</a></span></dt><dd><dl><dt><span class="section"><a href="#_new_users">3.2.1. New Users</a></span></dt><dt><span class="section"><a href="#_membership">3.2.2. Membership</a></span></dt><dt><span class="section"><a href="#_roles">3.2.3. Roles</a></span></dt></dl></dd><dt><span class="section"><a href="#_managing_organizations">3.3. Managing Organizations</a></span></dt><dt><span class="section"><a href="#_managing_plans">3.4. Managing Plans</a></span></dt><dd><dl><dt><span class="section"><a href="#_creating_a_plan">3.4.1. Creating a Plan</a></span></dt><dt><span class="section"><a href="#_plan_policies">3.4.2. Plan Policies</a></span></dt><dt><span class="section"><a href="#_locking_the_plan">3.4.3. Locking the Plan</a></span></dt></dl></dd><dt><span class="section"><a href="#_providing_apis_2">3.5. Providing APIs</a></span></dt><dd><dl><dt><span class="section"><a href="#_creating_an_api">3.5.1. Creating an API</a></span></dt><dt><span class="section"><a href="#_api_implementation">3.5.2. API Implementation</a></span></dt><dt><span class="section"><a href="#_api_definition">3.5.3. API Definition</a></span></dt><dt><span class="section"><a href="#_available_plans">3.5.4. Available Plans</a></span></dt><dt><span class="section"><a href="#_managing_policies">3.5.5. Managing Policies</a></span></dt><dt><span class="section"><a href="#_publishing_in_the_gateway">3.5.6. Publishing in the Gateway</a></span></dt><dt><span class="section"><a href="#_api_metrics">3.5.7. API Metrics</a></span></dt><dt><span class="section"><a href="#_importing_api_s">3.5.8. Importing API(s)</a></span></dt></dl></dd><dt><span class="section"><a href="#_consuming_apis_2">3.6. Consuming APIs</a></span></dt><dd><dl><dt><span class="section"><a href="#_consuming_public_apis">3.6.1. Consuming Public APIs</a></span></dt><dt><span class="section"><a href="#_creating_a_client_app">3.6.2. Creating a Client App</a></span></dt><dt><span class="section"><a href="#_creating_api_contracts">3.6.3. Creating API Contracts</a></span></dt><dt><span class="section"><a href="#_api_definition_information">3.6.4. API Definition Information</a></span></dt><dt><span class="section"><a href="#_managing_policies_2">3.6.5. Managing Policies</a></span></dt><dt><span class="section"><a href="#_registering_in_the_gateway">3.6.6. Registering in the Gateway</a></span></dt><dt><span class="section"><a href="#_live_api_endpoints">3.6.7. Live API Endpoints</a></span></dt></dl></dd><dt><span class="section"><a href="#_versioning">3.7. Versioning</a></span></dt><dt><span class="section"><a href="#_system_administration">3.8. System Administration</a></span></dt><dd><dl><dt><span class="section"><a href="#_roles_2">3.8.1. Roles</a></span></dt><dt><span class="section"><a href="#_policy_definitions">3.8.2. Policy Definitions</a></span></dt><dt><span class="section"><a href="#_gateways">3.8.3. Gateways</a></span></dt><dt><span class="section"><a href="#_plugins">3.8.4. Plugins</a></span></dt><dt><span class="section"><a href="#_export_import_data">3.8.5. Export/Import Data</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#_api_gateway">4. API Gateway</a></span></dt><dd><dl><dt><span class="section"><a href="#_configuration">4.1. Configuration</a></span></dt><dt><span class="section"><a href="#_invoking_managed_apis">4.2. Invoking Managed APIs</a></span></dt><dt><span class="section"><a href="#_recording_metrics">4.3. Recording Metrics</a></span></dt></dl></dd></dl></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_introduction"/>Chapter 1. Introduction</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#_what_is_api_management">1.1. What is API Management?</a></span></dt><dt><span class="section"><a href="#_project_goals">1.2. Project Goals</a></span></dt><dt><span class="section"><a href="#_typical_use_cases">1.3. Typical Use Cases</a></span></dt><dd><dl><dt><span class="section"><a href="#_security">1.3.1. Security</a></span></dt><dt><span class="section"><a href="#_throttling_rate_limiting">1.3.2. Throttling/Rate Limiting</a></span></dt><dt><span class="section"><a href="#_metering_billing">1.3.3. Metering/Billing</a></span></dt></dl></dd></dl></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_what_is_api_management"/>1.1. What is API Management?</h2></div></div></div><p>A popular trend in enterprise software development these days is to design client apps to be very decoupled
-and use APIs to connect them.  This approach provides an excellent way to reuse functionality across various
-applications and business units. Another great benefit of API usage in enterprises is the ability to create
-those APIs using a variety of disparate technologies.</p><p>However, this approach also introduces its own pitfalls and disadvantages. Some of those disadvantages
-include things like:</p><div class="itemizedlist"><ul><li>Difficulty discovering or sharing existing APIs</li><li>Difficulty sharing common functionality across API implementations</li><li>Tracking of API usage/consumption</li></ul></div><p>API Management is a technology that addresses these and other issues by providing an API Manager to track
-APIs and configure governance policies, as well as an API Gateway that sits between the API and the client.
-This API Gateway is responsible for applying the policies configured during management.</p><p>Therefore an API management system tends to provide the following features:</p><div class="itemizedlist"><ul><li>Centralized governance policy configuration</li><li>Tracking of APIs and consumers of those APIs</li><li>Easy sharing and discovery of APIs</li><li>Leveraging common policy configuration across different APIs</li></ul></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_project_goals"/>1.2. Project Goals</h2></div></div></div><p>The goals of the JBoss API management project are to provide an easy to use and powerful API
-Manager as well as a small, fast, low-overhead API Gateway to implement standard API management functionality.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_typical_use_cases"/>1.3. Typical Use Cases</h2></div></div></div><p>Some common API management use cases include:</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_security"/>1.3.1. Security</h3></div></div></div><p>APIs will very often have a security requirement such that clients connecting to the API must authenticate in
-some fashion. Authentication can vary greatly both in the protocols used to authenticate and the identity
-source used for validation.</p><p>It can often be convenient to provide authentication at the API management layer to free up the back end API
-from having to do this work. This approach also has the side benefit of centralizing configuration of
-authentication for a wide array of disparate APIs.</p><p>Therefore the API management layer must provide authentication capabilities using a wide range of protocols
-including BASIC, digest, OAuth, etc.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_throttling_rate_limiting"/>1.3.2. Throttling/Rate Limiting</h3></div></div></div><p>The API management layer is a convenient place to ensure throttling (also known as rate limiting) to your
-APIs.  Throttling is a way to prevent individual clients from issuing too many requests to an API. Because
-all requests to an API go through the API Gateway it is an excellent place to do this throttling work.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_metering_billing"/>1.3.3. Metering/Billing</h3></div></div></div><p>There are a number of reasons why an API provider would be interested in the number of requests made to her
-API. The most common reason for public facing APIs is to implement billing based on usage per consumer.
-Metering is the feature that provides this API management capability.</p></div></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_crash_course"/>Chapter 2. Crash Course</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#_organizations">2.1. Organizations</a></span></dt><dt><span class="section"><a href="#_providing_public_apis">2.2. Providing Public APIs</a></span></dt><dd><dl><dt><span class="section"><a href="#_public_api">2.2.1. Public API</a></span></dt><dt><span class="section"><a href="#_sending_requests_to_your_public_api">2.2.2. Sending Requests to your Public API</a></span></dt></dl></dd><dt><span class="section"><a href="#_providing_apis">2.3. Providing APIs`</a></span></dt><dd><dl><dt><span class="section"><a href="#_plans">2.3.1. Plans</a></span></dt><dt><span class="section"><a href="#_apis">2.3.2. APIs</a></span></dt></dl></dd><dt><span class="section"><a href="#_consuming_apis">2.4. Consuming APIs</a></span></dt><dd><dl><dt><span class="section"><a href="#_client_apps">2.4.1. Client Apps</a></span></dt><dt><span class="section"><a href="#_sending_requests">2.4.2. Sending Requests</a></span></dt></dl></dd></dl></div><p>This is the "tl;dr" section of the apiman User Guide.  Read this section to get a decent high level
-overview of the concepts you need to know to get going quickly.</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_organizations"/>2.1. Organizations</h2></div></div></div><p>Everything in apiman starts with the Organization.  First you should create one of these.  The
-Organization is where everything else will be managed.  It also allows you to grant specific
-roles to other users you wish to collaborate with.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_providing_public_apis"/>2.2. Providing Public APIs</h2></div></div></div><p>The simplest way to get started with apiman is to create a "Public" API.  This is simply an API
-that can be invoked by any client by sending HTTP requests to the appropriate Gateway endpoint.
-No contracts are required.</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_public_api"/>2.2.1. Public API</h3></div></div></div><p>First, you must have an Organization created.  In apiman an API is a representation of your
-back-end API, but managed with policies and accessible via the API Gateway instead of
-directly to the URL of the back-end API.</p><p>To create an API, simply navigate to the "APIs" tab for one of your Organizations and click
-the "New API" button.  You will need to provide a Name and Initial Version for your new
-API and then click "Create API" at the bottom of the form.</p><p>Once you have created an API, you will need to provide some basic configuration, including:</p><div class="itemizedlist"><ul><li><span class="strong"><strong>API Endpoint</strong></span> - the URL to your back-end API</li><li><span class="strong"><strong>API Type</strong></span> - whether your API is rest or soap</li><li><span class="strong"><strong>API Content-Type</strong></span> - whether your API speaks JSON or XML</li></ul></div><p>Finally, on the "Plans" tab you need to check the "Make this API public" checkbox.</p><p>Once you have configured all these aspects of the API, you need to <span class="strong"><strong>Publish</strong></span> the API
-to the API Gateway.  This can be done by clicking the "Publish" button at the top of
-the page.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_sending_requests_to_your_public_api"/>2.2.2. Sending Requests to your Public API</h3></div></div></div><p>Once the API is published, you can get its URL by navigating to the "Endpoint" tab.
-From there you can copy the URL for this managed API.  Simply send HTTP requests
-to this URL as you would your back-end API!</p><p>The actual managed endpoint may vary depending on the Gateway, but typically the endpoint is
-something like this:</p><div class="itemizedlist"><ul><li><a class="ulink" href="http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/">http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/</a></li></ul></div></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_providing_apis"/>2.3. Providing APIs`</h2></div></div></div><p>If you want to know how to provide managed APIs via apiman, this is a fast and dirty quickstart.</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_plans"/>2.3.1. Plans</h3></div></div></div><p>You should already have created an Organization.  Navigate to your Organization and switch to the
-Plans tab.  From there you can create new Plans.  A Plan is basically a collection of policies
-that will be applied to requests made to APIs being access through it.  Plans will be assigned
-to APIs during API configuration.  Plans give you the opportunity to offer access to the
-same API with different SLAs (e.g. different quotas).</p><p>Use the Policies tab to add zero or more Policies to the Plan.  Each Policy has its own unique
-configuration.</p><p>Once you have created all appropriate Policies, you need to <span class="strong"><strong>Lock</strong></span> the Plan so that it can be
-used by your APIs.  This can be done by clicking the <span class="emphasis"><em>Lock</em></span> button at the top of the page.  Note
-that a Policy must be locked for use so that API consumers can have confidence that the details
-of the Plan will not change after they have agreed to them.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_apis"/>2.3.2. APIs</h3></div></div></div><p>After you have created at least one Plan, you can go back to the Organization page and switch to
-the APIs tab.  From there you can create a new API.  In apiman an API is a representation of your
-back-end API, but managed with policies and discoverable within the apiman system.</p><p>Once you have created an API, you will need to provide some basic configuration, including:</p><div class="itemizedlist"><ul><li><span class="strong"><strong>API Endpoint</strong></span> - the URL to your back-end API</li><li><span class="strong"><strong>API Type</strong></span> - whether your API is rest or soap</li><li><span class="strong"><strong>API Content-Type</strong></span> - whether your API speaks JSON or XML</li><li><span class="strong"><strong>Plans</strong></span> - One or more Plans</li></ul></div><p>The Plans are chosen from those available within the Organization.  An API can be made
-available through any or all of the Organization’s plans.  When a client app consumes the
-API it will do so through one of the available plans.  See the "Consuming APIs" section
-for details.</p><p>Once you have configured all necessary aspects of the API, you need to <span class="strong"><strong>Publish</strong></span> the API
-to the API Gateway.  This can be done by clicking the <span class="emphasis"><em>Publish</em></span> button at the top of the page.</p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_consuming_apis"/>2.4. Consuming APIs</h2></div></div></div><p>If you’re interested in consuming APIs that someone else is providing via apiman, this section
-should give you a good start.</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_client_apps"/>2.4.1. Client Apps</h3></div></div></div><p>In order to consume an API, you will first need to create a Client App in your Organization.
-The Client App <span class="strong"><strong>can</strong></span> (but often does not) exist in the same Organization as the APIs it
-consumes.  To create a Client App, navigate to the Client Apps tab for your Organization.</p><p>Once you have create a Client App, you can search for APIs to consume.  There are a number
-of ways to search for APIs.  Once you have located an API, you must create a Contract
-between your Client App and the API.  A Contract is always created through one of the Plans
-provided by the API.</p><p>After you have created all appropriate API Contracts, you must register the Client App with
-the API Gateway.  This can be done by clicking the <span class="emphasis"><em>Register</em></span> button at the top of the page.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_sending_requests"/>2.4.2. Sending Requests</h3></div></div></div><p>After the Client App is Registered, navigate to the APIs tab to see a list of all the API
-Contracts and to get details (by clicking the Expand Details arrow on the left) about each one.
-This tab is important because it allows you to find out the API Key assigned to each API
-Contract.  The API Key is necessary when making managing calls to the API Gateway for a particular
-API.  Additionally, this tab shows the actual API Gateway endpoint that your client must
-invoke in order to call the managed API.</p><p>The actual managed endpoint may vary depending on the Gateway, but typically the endpoint is
-something like this:</p><div class="itemizedlist"><ul><li><a class="ulink" href="http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/">http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/</a></li></ul></div><p>Requests to managed endpoints must include the API Key so that the Gateway knows which Contract
-is being used to invoke the API.  The API Key can be sent in one of the following ways:</p><div class="itemizedlist"><ul><li>As an HTTP Header named <span class="strong"><strong>X-API-Key</strong></span></li><li>As a URL query parameter named <span class="strong"><strong>apikey</strong></span></li></ul></div></div></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_api_manager"/>Chapter 3. API Manager</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#_data_model">3.1. Data Model</a></span></dt><dd><dl><dt><span class="section"><a href="#_organizations_2">3.1.1. Organizations</a></span></dt><dt><span class="section"><a href="#_policies">3.1.2. Policies</a></span></dt><dt><span class="section"><a href="#_plans_2">3.1.3. Plans</a></span></dt><dt><span class="section"><a href="#_apis_2">3.1.4. APIs</a></span></dt><dt><span class="section"><a href="#_client_apps_2">3.1.5. Client Apps</a></span></dt><dt><span class="section"><a href="#_api_contracts">3.1.6. API Contracts</a></span></dt><dt><span class="section"><a href="#_policy_chain">3.1.7. Policy Chain</a></span></dt></dl></dd><dt><span class="section"><a href="#_user_management">3.2. User Management</a></span></dt><dd><dl><dt><span class="section"><a href="#_new_users">3.2.1. New Users</a></span></dt><dt><span class="section"><a href="#_membership">3.2.2. Membership</a></span></dt><dt><span class="section"><a href="#_roles">3.2.3. Roles</a></span></dt></dl></dd><dt><span class="section"><a href="#_managing_organizations">3.3. Managing Organizations</a></span></dt><dt><span class="section"><a href="#_managing_plans">3.4. Managing Plans</a></span></dt><dd><dl><dt><span class="section"><a href="#_creating_a_plan">3.4.1. Creating a Plan</a></span></dt><dt><span class="section"><a href="#_plan_policies">3.4.2. Plan Policies</a></span></dt><dt><span class="section"><a href="#_locking_the_plan">3.4.3. Locking the Plan</a></span></dt></dl></dd><dt><span class="section"><a href="#_providing_apis_2">3.5. Providing APIs</a></span></dt><dd><dl><dt><span class="section"><a href="#_creating_an_api">3.5.1. Creating an API</a></span></dt><dt><span class="section"><a href="#_api_implementation">3.5.2. API Implementation</a></span></dt><dt><span class="section"><a href="#_api_definition">3.5.3. API Definition</a></span></dt><dt><span class="section"><a href="#_available_plans">3.5.4. Available Plans</a></span></dt><dt><span class="section"><a href="#_managing_policies">3.5.5. Managing Policies</a></span></dt><dt><span class="section"><a href="#_publishing_in_the_gateway">3.5.6. Publishing in the Gateway</a></span></dt><dt><span class="section"><a href="#_api_metrics">3.5.7. API Metrics</a></span></dt><dt><span class="section"><a href="#_importing_api_s">3.5.8. Importing API(s)</a></span></dt></dl></dd><dt><span class="section"><a href="#_consuming_apis_2">3.6. Consuming APIs</a></span></dt><dd><dl><dt><span class="section"><a href="#_consuming_public_apis">3.6.1. Consuming Public APIs</a></span></dt><dt><span class="section"><a href="#_creating_a_client_app">3.6.2. Creating a Client App</a></span></dt><dt><span class="section"><a href="#_creating_api_contracts">3.6.3. Creating API Contracts</a></span></dt><dt><span class="section"><a href="#_api_definition_information">3.6.4. API Definition Information</a></span></dt><dt><span class="section"><a href="#_managing_policies_2">3.6.5. Managing Policies</a></span></dt><dt><span class="section"><a href="#_registering_in_the_gateway">3.6.6. Registering in the Gateway</a></span></dt><dt><span class="section"><a href="#_live_api_endpoints">3.6.7. Live API Endpoints</a></span></dt></dl></dd><dt><span class="section"><a href="#_versioning">3.7. Versioning</a></span></dt><dt><span class="section"><a href="#_system_administration">3.8. System Administration</a></span></dt><dd><dl><dt><span class="section"><a href="#_roles_2">3.8.1. Roles</a></span></dt><dt><span class="section"><a href="#_policy_definitions">3.8.2. Policy Definitions</a></span></dt><dt><span class="section"><a href="#_gateways">3.8.3. Gateways</a></span></dt><dt><span class="section"><a href="#_plugins">3.8.4. Plugins</a></span></dt><dt><span class="section"><a href="#_export_import_data">3.8.5. Export/Import Data</a></span></dt></dl></dd></dl></div><p>There are two layers to the API management project. There is an API Manager which allows end users to
-centrally manage their APIs. Additionally there is an API Gateway which is responsible for applying those
-policies to API requests.</p><p>The API Manager allows end-users to track, configure, and share APIs with other users. All of this is
-accomplished by the end user by logging into the API Manager user interface (or using the API Manager
-REST API).</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_data_model"/>3.1. Data Model</h2></div></div></div><p>It is perhaps most important to understand the various entities used by the API Manager, as well as
-their relationships with each other.</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_organizations_2"/>3.1.1. Organizations</h3></div></div></div><p>The top level container concept within the API management project its called the organization. All other
-entities are managed within the scope of an organization.</p><p>When users log into the API management system they must be affiliated with one or more organization. Users
-can have different roles within that organization allowing them to perform different actions and manage
-different entities. Please see the <span class="emphasis"><em>User Management</em></span> section below for more details on this topic.</p><p>What an organization actually represents will depend upon who is using API management. When installed within
-a large enterprise, an organization may represent an internal group within IT (for example the HR group).  If
-installed in the cloud, an organization might represent an external company or organization.</p><p>In any case, an organization is required before the end user can create or consume APIs.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_policies"/>3.1.2. Policies</h3></div></div></div><p>The most important concept in API management is the policy. The policy is the unit of work executed at
-runtime in order to implement API governance. All other entities within the API Manager exist in support
-of configuring policies and sensibly applying them at runtime.</p><p>When a request for an API is made at runtime, a policy chain is created and applied to the inbound request,
-prior to proxying that request to the back-end API implementation.  This policy chain consists of policies
-configured in the API Manager.</p><p>An individual policy consists of a type (e.g. authentication or rate limiting) as well as configuration
-details specific to the type and instance of that policy.  Multiple policies can be configured per API
-resulting in a policy chain that is applied at runtime.</p><p>It is very important to understand that policies can be configured at three different levels within API
-management.  Policies can be configured on an API, on a plan, or on a client app. For more details
-please see the sections below.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_plans_2"/>3.1.3. Plans</h3></div></div></div><p>A plan is a set of policies that define a level of service for an API. When an API is consumed it may be
-consumed through a plan. Please see the section on <span class="emphasis"><em>API Contracts</em></span> for more information.</p><p>An organization can have multiple plans associated with it. Typically each plan within an organization
-consists of the same set of policies but with different configuration details. For example, an organization
-might have a Gold plan with a rate limiting policy that restricts consumers to 1000 requests per day. The
-same organization may then have a Silver plan which is also configured with a rate limiting policy, but which
-restricts consumers to 500 requests per day.</p><p>Once a plan has been fully configured (all desired policies added and configured) it must be locked so that
-it can be used by APIs.  This is done so that API providers can’t change the details of the plan
-out from underneath the client app developers who are using it.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_apis_2"/>3.1.4. APIs</h3></div></div></div><p>An API represents an external API that is being governed by the API management system.  An API consists
-of a set of metadata including name and description as well as an external endpoint defining the API
-implementation. The external API implementation endpoint includes:</p><div class="itemizedlist"><ul><li>The type/protocol of the endpoint (e.g. REST or SOAP)</li><li>The endpoint content type (e.g. XML or JSON)</li><li>The endpoint location (URL) so that the API can be properly proxied to at runtime.</li></ul></div><p>In addition, policies can be configured on an API. Typically, the policies applied to APIs are things
-like authentication, or caching.  Any policies configured on API will be applied at runtime regardless of the
-client app and API contract.  This is why authentication is a common policy to configure at the API
-level.</p><p>APIs may be offered through one or more plans configured in the same organization. When plans are used,
-API consumers (client apps) must consume the API through one of those plans. Please see the section on
-<span class="emphasis"><em>API Contracts</em></span> for more information.  Alternatively, an API can simply be marked as "Public", in which
-case any client may access the API’s managed endpoint without providing an API Key.</p><p>Only once an API is fully configured, including its policies, implementation, and plans can it be
-published to the Gateway for consumption by client apps.  Once an API has been published, it can only
-be changed if it is a "Public" API.  APIs that are offered via Plans are immutable - to change them
-you must create a new version.  The reason for this is that API consumers may have created Contracts
-with your API, through your Plan.  When they do this, they must agree to some terms and conditions.
-It is therefore understood that the terms to which they are agreeing will not change.  However, for
-Public APIs, there is no such agreement.  For this reason, you can make changes to Public APIs and
-re-publish them at any time.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_client_apps_2"/>3.1.5. Client Apps</h3></div></div></div><p>A client app represents a consumer of an API. Typical API consumers are things like mobile applications and
-B2B applications. Regardless of the actual implementation, a client app must be added to the
-API management system so that Contracts can be created between it and the APIs it wishes to consume.</p><p>A client app consists of basic metadata such as name and description.  Policies can also be configured on
-a client app, but are optional.</p><p>Finally, API Contracts can be created between a client app and the API(s) it wishes to consume.
-Once the API Contracts are created, the client app can be registered with the runtime gateway.  Policies
-and Contracts can be added/removed at any time.  However, after any changes are made, you must
-re-register the client app.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_api_contracts"/>3.1.6. API Contracts</h3></div></div></div><p>An API contract is simply a link between a Client App and an API through a plan offered by that
-API. This is the only way that a client app can consume an API. If there are no client apps that
-have created API contracts with an API, that API cannot be accessed through the API management
-runtime gateway (unless of course the API is "Public").</p><p>When an API Contract is created, the system generates a unique API key specific to that contract. All
-requests made to the API by a Client App through the API Gateway must include this API key. The API
-key is used to create the runtime policy chain from the policies configured on the API, plan, and
-client app.</p><p>API Contracts can only be created between Client Apps and published APIs which are offered through
-at least one Plan.  An API Contract cannot be created between a Client App and a Public API.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_policy_chain"/>3.1.7. Policy Chain</h3></div></div></div><p>A policy chain is an ordered sequence of policies that are applied when a request is made for an API
-through the API Gateway. The order that policies are applied is important and is as follows:</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="orderedlist"><ol><li>Client App</li><li>Plan</li><li>API</li></ol></div><p>Within these individual sections, the end user can specify the order of the policies.</p><p>When a request for an API is received by the API Gateway the policy chain is applied to the request in
-the order listed above. If none of the policies fail, the API Gateway will proxy the request to the backend
-API implementation.  Once a response is received from the back end API implementation, the policy chain is
-then applied in reverse order to that response. This allows each policy to be applied twice, once to the
-inbound request and then again to the outbound response.</p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_user_management"/>3.2. User Management</h2></div></div></div><p>The API Manager offers user role capabilities at the organization level. Users can be members of
-organizations and have specific roles within those organizations. The roles themselves are configurable by
-an administrator, and each role provides the user with a set of permissions that determine what actions the
-user can take within an organization.</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_new_users"/>3.2.1. New Users</h3></div></div></div><p>Users must self register with the management UI in order to be given access to an organization or to
-create their own organization. In some configurations it is possible that user self registration is
-unavailable and instead user information is provided by a standard source of identity such as LDAP.  In
-either case, the actions a user can take are determined by that user’s role memberships within the context
-of an organization.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_membership"/>3.2.2. Membership</h3></div></div></div><p>Users can be members of organizations. All memberships in an organization include the specific roles the
-user is granted. It is typically up to the owner of an organization to grant role memberships to the members
-of that organization.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_roles"/>3.2.3. Roles</h3></div></div></div><p>Roles determine the capabilities granted a user within the context of the organization. The roles themselves
-and the capabilities that those roles grant are configured by system administrators. For example,
-administrators would typically configure the following roles:</p><div class="itemizedlist"><ul><li>Organization Owner</li><li>API Developer</li><li>Client App Developer</li></ul></div><p>Each of these roles is configured by an administrator to provide a specific set of permissions allowing the
-user to perform relevant actions appropriate to that role. For example the Client App Developer role would
-grant an end user the ability to manage client apps and API contracts for those client apps. However
-that user would not be able to create or manage the organization’s APIs or plans.</p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_managing_organizations"/>3.3. Managing Organizations</h2></div></div></div><p>Before any other actions can be taken an organization must exist. All other operations take place within the
-context of an organization.</p><p>In order to create an organization click the <span class="emphasis"><em>Create a New Organization</em></span> link found on the dashboard page
-that appears when you first login. Simply provide an organization name and description and then click the
-<span class="emphasis"><em>Create Organization</em></span> button.  If successful you will be taken to the organization details page.</p><p>If you create multiple organizations, you can see the list of those organizations on your home page. For
-example, you may click the <span class="emphasis"><em>Go to My Organizations</em></span> link from the dashboard page.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_managing_plans"/>3.4. Managing Plans</h2></div></div></div><p>Plans must be managed within the scope of an organization.  Once created, plans can be used for any API
-defined within that same organization.  To see a list of existing plans for an organization, navigate to the
-<span class="emphasis"><em>Plans</em></span> tab for that organization on its details page.</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_creating_a_plan"/>3.4.1. Creating a Plan</h3></div></div></div><p>Plans can be created easily from the <span class="emphasis"><em>Plans</em></span> tab of the organization details page. Simply click the <span class="emphasis"><em>New Plan</em></span>
-button and then provide a plan name, version, and description. Once that information is provided, click the
-<span class="emphasis"><em>Create Plan</em></span> button. If successfully created, you’ll be taken to the plan details page.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_plan_policies"/>3.4.2. Plan Policies</h3></div></div></div><p>If you switch to the <span class="emphasis"><em>Policies</em></span> tab on the plan details page you can configure the list of policies for the
-plan. Please note that the order of the policies can be changed and is important. The order that the policies
-appear in the user interface determines the order they will be applied at runtime. You can drag a policy up
-and down the list to change the order.</p><p>To add a policy to the plan click the <span class="emphasis"><em>Add Policy</em></span> button. On the resulting page choose the type of policy
-you wish to create and then configure the details for that policy. Once you have configured the details click
-the <span class="emphasis"><em>Add Policy</em></span> button to add the policy to the plan.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_locking_the_plan"/>3.4.3. Locking the Plan</h3></div></div></div><p>Once all your plan policies are added and configured the way you want them, you will need to Lock the
-plan.  This can be done from any tab of the Plan UI page.  Locking the plan will prevent all future policy
-changes, and make the plan available for use by APIs.</p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_providing_apis_2"/>3.5. Providing APIs</h2></div></div></div><p>A core capability of API management is for end users to create, manage, and configure APIs they wish to
-provide. This section explains the steps necessary for users to provide those APIs.</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_creating_an_api"/>3.5.1. Creating an API</h3></div></div></div><p>First the user must create an API within an organization. If an organization does not yet exist one can
-easily be created.  See the <span class="emphasis"><em>Managing Organizations</em></span> section for details.</p><p>From the organization details page, navigate to the <span class="emphasis"><em>APIs</em></span> tab and click on the <span class="emphasis"><em>New API</em></span> button. You
-will be asked to provide an API name, version number, and description.</p><p>If successfully created, you will be taken to the API details page. From here you can configure the
-details of the API.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_api_implementation"/>3.5.2. API Implementation</h3></div></div></div><p>Every API must be configured with an API implementation. The implementation indicates the external
-API that the API Gateway will proxy to if all the policies are successfully applied. Click the
-<span class="emphasis"><em>Implementation</em></span> tab to configure the API endpoint and API type details on your API.</p><p>The <span class="emphasis"><em>Implementation</em></span> tab is primarily used to configure the details of the back-end API that
-apiman will proxy to at runtime.  You must configure the following:</p><div class="itemizedlist"><ul><li><span class="strong"><strong>Endpoint URL</strong></span> - The URL that apiman will use to proxy a request made for this API.</li><li><span class="strong"><strong>Endpoint Type</strong></span> - Currently either REST or SOAP (not presently used, future information)</li><li><span class="strong"><strong>Endpoint Content Type</strong></span> - Choose between JSON and XML, information primarily used to respond with a policy failure or error in the appropriate format.</li></ul></div><p>Additionally, the <span class="emphasis"><em>Implementation</em></span> tab allows you to configure any security options that might
-be required when proxying requests to the back-end API.  For example, if you are using two-way
-SSL to ensure full security between the API Gateway and your back-end API, you may configure
-that here.  We also support simple BASIC authentication between the gateway and your back end
-API.  Please note that BASIC authentication is not ideal, and especially insecure if not
-using SSL/HTTPS to connect to the back end API.</p><p>If the apiman administrator has configured multiple Gateways (see the "System Administration / Gateways"
-section below), then the <span class="emphasis"><em>Implementation</em></span> tab will also include an option that will let
-you choose which Gateway(s) to use when publishing.  You may select one or more Gateway
-in this case.  If you choose multiple Gateways, then when you click the <span class="emphasis"><em>Publish</em></span> button,
-apiman will publish the API to <span class="strong"><strong>all</strong></span> of the selected Gateways.</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>If a single Gateway has been configured, then you don’t have a choice, and so the UI
-will hide the Gateway selector entirely and simply pick the default Gateway for you.</p></div><p>Do not forget to click the Save button when you are done making changes.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_api_definition"/>3.5.3. API Definition</h3></div></div></div><p>As a provider of an API, it is best to include as much information about the API as possible, so
-that consumers can not only create contracts, but also learn how to make calls.  For this purpose, you
-can optionally include an API Definition document by adding it to your API on the Definition tab.
-Currently the only supported type of definition file is Swagger.  Include a swagger spec document here
-so that consumers of your API can browse information about your API directly in the API Manager
-UI.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_available_plans"/>3.5.4. Available Plans</h3></div></div></div><p>Before an API can be consumed by a client app, it must make itself available through at least one of
-the organization’s plans (or it must be marked as "Public"). Marking an API as public or making an API
-available through one or more plan can be done by navigating to the <span class="emphasis"><em>Plans</em></span> tab on the API details page. The
-<span class="emphasis"><em>Plans</em></span> tab will list all of the available plans defined by the organization. Simply choose one or more plan
-from this list.  If no plans are needed, you can instead mark the API as "Public", making it available to
-be consumed anonymously by any client.  Although an API can be <span class="strong"><strong>both</strong></span> Public and available through one or
-more plan, it is unusual to do so.</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>After you have either marked the API as "public" or selected at least one plan, make sure to click the
-Save button.</p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_managing_policies"/>3.5.5. Managing Policies</h3></div></div></div><p>API policies can be added and configured by navigating to the <span class="emphasis"><em>Policies</em></span> tab on the API details
-page. The <span class="emphasis"><em>Policies</em></span> tab presents a list of all the policies configured for this API. To add another
-policy to the API click the <span class="emphasis"><em>Add Policy</em></span> button. On the resulting page choose the type of policy you
-wish to create and then configure the details for that policy. Once you have configured the details click
-the <span class="emphasis"><em>Add Policy</em></span> button to add the policy to the API.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_publishing_in_the_gateway"/>3.5.6. Publishing in the Gateway</h3></div></div></div><p>After all of the configuration is complete for an API, it is time to publish the API to the runtime
-gateway. This can be done from any tab on the API details page by clicking  the <span class="emphasis"><em>Publish</em></span> button in
-the top section of the UI.  If successful, the status of the API will change to "Published" and the
-<span class="emphasis"><em>Publish</em></span> button will disappear.</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>If the API cannot yet be published (the <span class="emphasis"><em>Publish</em></span> button is disabled) then a notification will
-appear near the button and will read "Why Can’t I publish?"  Clicking this notification will provide
-details about what information is still required before the API can be published to the Gateway.</p></div><p>Once the API has been published, it may or may not be editable depending on whether it is a "Public"
-API or not.  For "Public" APIs, you will be able to continue making changes.  After at least one
-change is made, you will have the option to "Re-Publish" the API to the Gateway.  Doing so will
-update all information about the API in the Gateway.  However, if the API is <span class="strong"><strong>not</strong></span> Public, then
-the API will be immutable - therefore in order to make any changes you will need to create a new
-version of the API.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_api_metrics"/>3.5.7. API Metrics</h3></div></div></div><p>Once an API is published and is being consumed at runtime, metrics information about that usage is
-recorded in a metrics storage system.  See the Metrics section of the API Gateway documentation for
-more about how and when metrics data is recorded.</p><p>If an API has been used by at least once, then it will have metrics information available.
-This information can be viewed in the <span class="emphasis"><em>Metrics</em></span> tab on the API’s details page.  On this page
-you can choose the type of metric you wish to see (e.g. Usage metrics and Response Type
-metrics) as well as a pre-defined time range (e.g. Last 30 Days, Last Week, etc…).</p><p>The API Metrics page is a great way to figure out how often your API is used, and in what
-ways.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_importing_api_s"/>3.5.8. Importing API(s)</h3></div></div></div><p>As an alternative to manually creating and configuring an API, apiman also supports importing
-an API from a globally configured API Catalog.</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>The API Catalog is configured by the apiman system administrator/installer.  See the
-installation guide for more information about how to configure a custom API Catalog.</p></div><p>An API can be imported into apiman in one of two ways.  First, from the Organization’s "APIs"
-tab you can click the down-arrow next to the "New API" button and choose the "Import API(s)"
-option.  This results in a wizard that will guide you through importing one or more API
-from the catalog into the Organization.  This wizard will allow you to search for, find, and
-select multiple APIs.  It will then walk you through choosing your Plans or making the
-APIs "Public". Once all the wizard pages are completed, you can then import the API(s).</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>The Import API(s) wizard above is the only way to import multiple APIs at the same time.</p></div><p>Another option for importing an API from the catalog is to use the API Catalog Browser UI,
-which can be found by clicking the "Browse available/importable APIs" link on the API Manager
-Dashboard.  This link will open the catalog browser, allowing you to search for APIs to
-import.  The catalog browser is a friendlier interface, but only allows you to import a
-single API at a time.</p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_consuming_apis_2"/>3.6. Consuming APIs</h2></div></div></div><p>After the API providers have added a number of APIs to the API management system, those APIs
-can be consumed by Client Apps. This section explains how to consume APIs.</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_consuming_public_apis"/>3.6.1. Consuming Public APIs</h3></div></div></div><p>If you have marked an API as "Public", then consuming it is a simple matter of sending a request to the
-appropriate API Gateway endpoint.  The managed API endpoint may vary depending on the Gateway being
-used, but it typically of the following form:</p><div class="itemizedlist"><ul><li><a class="ulink" href="http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/">http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/</a></li></ul></div><p>Simply send requests to the managed API endpoint, and do not include an API Key.</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>The managed endpoint URL can be easily determined in the UI by navigating to the
-"Endpoint" tab on the API details UI page.</p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_creating_a_client_app"/>3.6.2. Creating a Client App</h3></div></div></div><p>In order to consume an API that is not "Public" you must first create a client app. Client Apps must
-exist within the context of an organization. If an organization does not yet exist for this purpose,
-simply create a new organization. See the section above on <span class="emphasis"><em>Managing Organizations</em></span> for more information.</p><p>To create a new Client App click the <span class="emphasis"><em>Create a New Client App</em></span> link on the dashboard page. On the resulting
-page provide a client app name, version, and description and then click the <span class="emphasis"><em>Create Client App</em></span> button. If
-the client app is successfully created, you will be taken to the client app details page.</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>You can also create a Client App within an Organization by going to the Organization’s "Client Apps"
-tab and clicking the "New Client App" button.</p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_creating_api_contracts"/>3.6.3. Creating API Contracts</h3></div></div></div><p>The primary action taken when configuring a client app is the creation of Contracts to APIs. This is
-what we mean when we say "consuming an API". There are a number of ways to create API contracts. This
-section will describe the most useful of these options.</p><p>From the Client App details page, you can find an API to consume by clicking on the <span class="emphasis"><em>Search for APIs to consume</em></span>
-link in the top section of the page. You will be taken to a page that will help you search for and find the
-API you wish to consume.</p><p>Use the controls on this page to search for an API. Once you have found the API you are interested in,
-click on its name in the search results area. This will take you to the API details page for API
-consumers. The consumer-oriented API details page presents you with all of the information necessary to
-make a decision about how to consume the API. It includes a list of all the API versions and a list
-of all of the available plans the API can be consumed through.</p><p>Note that you can click on an individual plan to see the details of the policies that will be enforced should
-that plan be chosen. Click on the <span class="emphasis"><em>Create Contract</em></span> button next to the plan you wish to use when consuming
-this API. You will be taken to the new contract page to confirm that you want to create an API
-contract to this API through the selected plan. If you are sure this is the API contract you wish to
-create, click the <span class="emphasis"><em>Create Contract</em></span> button and then agree to the terms and conditions. If successful, you
-will be taken to the <span class="emphasis"><em>Contracts</em></span> tab on the client app details page.</p><p>From the <span class="emphasis"><em>Contracts</em></span> tab on the client app details page you can see the list of API contracts already
-created for this client app. It is also possible to break API contracts from this same list by clicking
-an appropriate <span class="emphasis"><em>Break Contract</em></span> button.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_api_definition_information"/>3.6.4. API Definition Information</h3></div></div></div><p>If An API provider has included An API Definition for the API they are providing, you will be
-presented with an additional link on the consumer-oriented API details page labeled "API Definition".
-This link will take you to a page where you can browse the detailed documentation for the API.  The
-detailed documentation should be very helpful in learning what resources and operations are
-supported by the API, which will aid in figuring out how precisely to consume the API.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_managing_policies_2"/>3.6.5. Managing Policies</h3></div></div></div><p>Just like plans and APIs, client apps can have configured policies. The <span class="emphasis"><em>Policies</em></span> tab will present a
-list of all the policies configured for this client app. To add another policy to the client app click the
-<span class="emphasis"><em>Add Policy</em></span> button. On the resulting page choose the type of policy you wish to create and then configure
-the details for that policy. Once you have configured the details click the <span class="emphasis"><em>Add Policy</em></span> button to add the
-policy to the client app.</p><p>Of course, just like for Plans and APIs, you can manage the Client App policies from the <span class="emphasis"><em>Policies</em></span> tab.
-This allows you to not only add new policies but also edit, remove, and reorder them.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_registering_in_the_gateway"/>3.6.6. Registering in the Gateway</h3></div></div></div><p>After at least one API contract has been created for the client app, it is possible to register the
-client app with the runtime gateway. Until the client app is registered with the runtime gateway, it is
-not possible to make requests to back-end APIs on behalf of that client app.</p><p>To register the client app with the gateway, simply click the "Register" button at the top of the Client
-App details UI page (any tab).  If the status of the client app is "Ready", then the <span class="emphasis"><em>Register</em></span> button
-should be enabled.  If successful, the client app status will change to "Registered", and the <span class="emphasis"><em>Register</em></span>
-button will disappear.</p><p>Once the client app is registered, you can continue to make changes to it (such as modify its policies
-or create/break API Contracts).  If you do make any changes, then the <span class="emphasis"><em>Re-Register</em></span> button will become
-enabled.  Whenever you make changes to your Client App, you <span class="strong"><strong>must</strong></span> Re-Register it before those changes
-will show up in the Gateway.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_live_api_endpoints"/>3.6.7. Live API Endpoints</h3></div></div></div><p>After a client app has been registered with the runtime gateway, it is possible to send requests to the
-back-end APIs on behalf of that client app (through the client app’s API contracts). To do this
-you must know the URL of the managed API.  This URL <span class="emphasis"><em>optionally</em></span> includes the API Key generated for the API
-Contract.</p><p>To view a list of all of these managed endpoints, navigate to the <span class="emphasis"><em>APIs</em></span> tab on the API detail page. Each
-API contract is represented in the list of managed endpoints. You can expand an entry in the managed
-API endpoints table by clicking the <span class="emphasis"><em>&gt;</em></span> icon in the first column.  The resulting details will help you
-figure out the appropriate endpoint to use for a particular managed API.</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>There are two ways to pass the API Key to the Gateway when you make a request for a Managed
-Endpoint.  You can either include the API Key in the URL as a query parameter, or you can pass it
-via the <span class="strong"><strong>X-API-Key</strong></span> HTTP header.</p></div></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_versioning"/>3.7. Versioning</h2></div></div></div><p>Many of the entities in the API Manager support multiple simultaneous versions.  These include the
-following:</p><div class="itemizedlist"><ul><li>Plans</li><li>APIs</li><li>Client Apps</li></ul></div><p>Typically once an entity is frozen (e.g. Locked or Published) it can no longer be
-modified.  But often as things change, modifications to the API Management configuration are necessary.
-For example, as an API implementation evolves, the policies associated with it in the API Manager
-may need to change.  Versioning allows this to happen, by providing a way for a user to create a new
-version of a particular API (or Client App or Plan) and then making changes to it.</p><p>To create a new version of an entity, view the details of the entity and click the "New Version" button
-in the UI.  This will allow you to make a new version of the entity.  You can either make a simple,
-empty new version or you can make a clone of an existing version.  The latter is typically more
-convenient when making incremental changes.</p><div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="tip"><h2>Tip</h2><p>"Public" APIs and Client Apps can be modified and re-published (or re-registered) in the
-Gateway without the need to create a new version.</p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_system_administration"/>3.8. System Administration</h2></div></div></div><p>There are several "global" settings that must be configured/managed by an apiman administrator.  These
-global settings are managed by navigating to the <span class="strong"><strong>System Administration</strong></span> section of the API Manager UI.</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_roles_2"/>3.8.1. Roles</h3></div></div></div><p>Users must become a member of an organization before being allowed to manage any of the plans, APIs,
-or client apps contained within it.  When a user is made a member of an organization, they are granted
-a specific role within that organization.  Typical examples of roles are <span class="strong"><strong>Organization Owner</strong></span>, <span class="strong"><strong>API
-Provider</strong></span>, and <span class="strong"><strong>Client App Developer</strong></span>.  These roles each grant different specific privileges to the
-user.  For example, a user with the <span class="strong"><strong>Client App Developer</strong></span> role will be able to manage the organization’s
-client apps but not its APIs or plans.</p><p>The roles that are available when adding a member to an organization are managed in the <span class="strong"><strong>Roles</strong></span> section
-of the <span class="strong"><strong>System Administration</strong></span> UI.  The apiman admin can create as many roles as she wishes, giving
-each one a name, description, and the set of permissions it grants.  Additionally, certain roles may be
-automatically granted to users who create new organizations.  At least one such role must be present,
-otherwise organizations cannot be created.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_policy_definitions"/>3.8.2. Policy Definitions</h3></div></div></div><p>The policies available when configuring APIs, Plans, and Client Apps are controlled by the <span class="strong"><strong>Policy
-Definitions</strong></span> known to apiman.  These definitions are stored in the API Manager and are added by the
-apiman admin.  Typically these are added once and rarely changed.  But as new versions of apiman are
-released, additional policies will be made available.  For each policy, a policy definition must be
-configured in the <span class="strong"><strong>System Administration</strong></span> UI.</p><p>Additionally, it is possible for a plugin, when installed, to contribute one or more policy
-definitions to the list.  This is a very common way for new policy definitions to be added to
-apiman.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_gateways"/>3.8.3. Gateways</h3></div></div></div><p>Apiman allows multiple logical Gateways to be configured.  The Gateway is the server that actually applies
-the policies configured in the API Manager to live requests to managed APIs.  When using apiman, at
-least one Gateway must be running and configured in the API Manager.  However, there is no limit to the
-total number of Gateways that may be running.  The typical reason to have multiple Gateways is when
-some APIs are very high volume and others are not.  In this case, the high volume APIs could be
-published to a Gateway that can handle such load, while the low volume APIs could be published to
-another (perhaps cheaper) Gateway.</p><p>Another reason you may want multiple Gateways if if you need some of your APIs to be provided in
-a particular physical region and others in a different one.  In this case, you may have a Gateway
-(perhaps clustered) running in a US data center, while another Gateway (different cluster) is
-running separately in a data center in Europe.</p><p>In all cases, the apiman admin must configure these Gateways in the <span class="strong"><strong>System Administration</strong></span> UI.  Each
-Gateway has a name, description, and configuration endpoint.  The configuration endpoint is what the
-API Manager will use when publishing APIs and client apps into the Gateway.</p><p>When configuring an API Gateway you will need to include the authentication credentials required to
-invoke the API Gateway configuration REST API.  Typically this user must have the <span class="emphasis"><em>apipublisher</em></span> role
-in order to successfully talk to the API Gateway.  The Gateway UI includes a <span class="strong"><strong>Test Gateway</strong></span> button
-which will attempt to contact the Gateway API with the credentials included.  If successful, the
-test button will turn green.  If unsuccessful, details about the failure will be displayed and the
-test button will turn red.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_plugins"/>3.8.4. Plugins</h3></div></div></div><p>Apiman supports contributing additional functionality via a powerful plugin mechanism.  Plugins can be
-managed by an administrator within the API Manager UI.  The plugin management administration page allows
-an admin to add and delete plugins.</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h4 class="title"><a id="_adding_plugins"/>3.8.4.1. Adding Plugins</h4></div></div></div><p>The Plugin admin page has two tabs - one shows the list of plugins currently installed, and the
-other shows a list of "Available Plugins".  The list of available plugins comes from a plugin
-registry that is configured when apiman is installed (see the Installation Guide for details
-on how to configure a custom plugin registry).  By default, the "official" apiman plugins will
-show up in the list.</p><p>A custom plugin is typically added by clicking on the <span class="emphasis"><em>Add Custom Plugin</em></span> button found on the
-"Available Plugins" tab.  This allows you to install a plugin that is not found in the configured
-plugin registry.  When installing a custom plugin, you must provide the "coordinates" of the plugin.
-All plugins are actually maven artifacts, and as such their coordinates consist of the following
-maven properties:</p><div class="itemizedlist"><ul><li>Group ID</li><li>Artifact ID</li><li>Version</li><li>Classifier (optional)</li><li>Type (optional, defaults to <span class="emphasis"><em>war</em></span>)</li></ul></div><p>When installing a plugin from the plugin registry, simply locate it in the list shown on the
-"Available Plugins" tab and then click the "Install" action.  This will again take you to the
-Add Plugin page, but with all of the appropriate information already filled in.  At this point
-you should only need to click the "Add Plugin" button.</p><p>Plugins primarily are used to contribute custom policies to apiman.  These policies are automatically
-discovered (if they exist in the plugin) when a plugin is added to the API Manager.  Policies that
-have been contributed via a plugin will appear in the Policy Definitions admin page along with the
-built-in policies.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h4 class="title"><a id="_deleting_plugins"/>3.8.4.2. Deleting Plugins</h4></div></div></div><p>At any time you may choose to delete a plugin.  Note that if the plugin was contributing one
-or more policies to apiman, then the policy will no longer be available for use when configuring
-your Plans, APIs, and Client Apps.  However, if the policy is already in use by one of these
-entities, it will continue to work.  In other words, deleting a plugin only removes the policy
-for use by new entities, it does <span class="strong"><strong>not</strong></span> break existing usages.</p><p>To delete a plugin, simply click the "Delete" action for the appropriate plugin on the "Installed Plugins"
-tab.  After confirming the delete, the plugin should disappear from the list.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h4 class="title"><a id="_upgrading_plugins"/>3.8.4.3. Upgrading Plugins</h4></div></div></div><p>If apiman determines that a plugin can be upgraded, then an "Upgrade Plugin" action button will
-show up for the plugin in the "Installed Plugins" tab.  This action will be represented as an
-up arrow icon button.  When clicked, you will be prompted for the version of the plugin you wish
-to upgrade <span class="strong"><strong>to</strong></span>.  The result will be that a new version of the plugin will be downloaded and
-installed, replacing the older version you had before.  Note that any Plans, APIs, or Client
-Apps that were using the old version of the plugin’s policies will <span class="strong"><strong>continue</strong></span> to use the older
-version.  However, any new policies from the plugin added to entities will use the new version.
-In order to upgrade an existing entity to a newer policy, you will need to remove the old
-policy from that entity and re-add it.  We recommend that you only do this if there is a
-compelling reason (e.g. a bug is fixed or a new feature added).</p></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a id="_export_import_data"/>3.8.5. Export/Import Data</h3></div></div></div><p>Apiman has a feature that allows an admin user to Export and/or Import data.  You can access this
-feature by clicking the "Export/Import Data" link on the API Manager Dashboard page (admin only).
-This feature is useful for the following use-cases:</p><div class="itemizedlist"><ul><li>Backing up data</li><li>Migrating data between environments (e.g. Test→Production)</li><li>Upgrading between apiman versions</li></ul></div><p>From the Export/Import UI page, simply click the "Export All" button if you wish to export all
-of the data in the API Manager.  The result will be a downloaded JSON file containing all of
-your apiman data.  This file can then be optionally post-processed (perhaps you want to migrate only
-a single Organization from your Test environment to your Prod environment).  At some later time,
-you can import this file (typically into a different installation of apiman) by selecting it and
-choosing "Upload File".</p></div></div></div><div class="chapter" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_api_gateway"/>Chapter 4. API Gateway</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#_configuration">4.1. Configuration</a></span></dt><dt><span class="section"><a href="#_invoking_managed_apis">4.2. Invoking Managed APIs</a></span></dt><dt><span class="section"><a href="#_recording_metrics">4.3. Recording Metrics</a></span></dt></dl></div><p>The runtime layer of apiman consists of a small, lightweight and embeddable API Gateway, which is responsible
-for applying the policies configured in the API Manager to all requests to managed APIs.  By default
-apiman comes with a WAR version of the API Gateway.  Additionally, there is an asynchronous version of
-the API Gateway that runs on the vert.x platform.</p><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_configuration"/>4.1. Configuration</h2></div></div></div><p>The API Gateway is a completely separate component from the API Manager, and can therefore be used
-completely standalone if desired.  However, the API Manager provides a great deal of management functionality
-(along with a user interface) that is quite useful.  The API Gateway has a simple REST API that is used
-to configure it.  The API provides the following basic capabilities:</p><div class="itemizedlist"><ul><li>Publish an API</li><li>Register a Client App (with API Contracts)</li><li>Retire an API</li><li>Unregister a Client App</li></ul></div><p>Typically the API Manager is used to manage the configuration of various APIs and client apps
-within the scope of one or more Organizations.  At various times during the management of these
-entities, the user of the API Manager will <span class="emphasis"><em>Publish</em></span> an API or <span class="emphasis"><em>Register</em></span> a Client App.  When this
-action occurs, the API Manager invokes one of the relevant API Gateway configuration endpoints listed
-above.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_invoking_managed_apis"/>4.2. Invoking Managed APIs</h2></div></div></div><p>Once appropriate configuration has been published/registered with the API Gateway (see the Configuration
-section above), the API Gateway can be used to make managed calls to the APIs it knows about.  A
-managed API can be invoked as though the back-end API were being invoked directly, with the
-exception that the endpoint is obviously different.  The specific endpoint to use in order to invoke
-a particular API can be different based on the Gateway implementation.  However, typically the
-endpoint format is:</p><div class="itemizedlist"><ul><li><a class="ulink" href="http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/">http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/</a></li></ul></div><p>Note that all path segments beyond the {version} segment will be proxied on to the back-end
-API endpoint.  Additionally, all HTTP headers and all query parameters (except for the
-API Key) will also be proxied to the back-end API.</p><p>Requests to managed endpoints may include the API Key so that the Gateway knows which Contract
-is being used to invoke the API.  The API Key can be sent in one of the following ways:</p><div class="itemizedlist"><ul><li>As an HTTP Header named <span class="strong"><strong>X-API-Key</strong></span></li><li>As a URL query parameter named <span class="strong"><strong>apikey</strong></span></li></ul></div><p>If the API being invoked is a "Public" API, then no API Key should be sent.  However,
-the request should still be sent to the same endpoint as described above.  The endpoint
-itself contains enough information to let the Gateway know what API is being invoked.</p><p>If an API is not "Public" and you ommit the API Key, then the request will fail.</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title"><a id="_recording_metrics"/>4.3. Recording Metrics</h2></div></div></div><p>The API Gateway is typically configured to record each request made to it into a metrics
-storage system of some kind.  By default apiman will use an included elasticsearch
-instance to store this information.  Various pieces of information about each request
-is included in the record, including but not necessarily limited to the following:</p><div class="itemizedlist"><ul><li>Request start and end times</li><li>API start and end times (i.e. just the part of the request taken up by the back end API)</li><li>Resource path</li><li>Response type (success, failure, error)</li><li>API info (org id, id, version)</li><li>Client App info (org id, id, version)</li></ul></div><p>This information is then available for analysis and reporting.  The data can be accessed
-in a number of ways, including:</p><div class="itemizedlist"><ul><li>Through the API Manager UI</li><li>Through the API Manager REST API</li><li>Directly from the metrics system</li></ul></div></div></div></div></body></html>
\ No newline at end of file
+        PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head><title xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory">User Guide | apiman Open Source API Management</title>
+    <link rel="stylesheet" href="css/jbossorg.css" type="text/css"/>
+    <meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory"
+          name="generator" content="DocBook XSL-NS Stylesheets V1.74.0"/>
+    <meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory"
+          http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+</head>
+<body>
+<div class="book" lang="en-US">
+    <div class="titlepage">
+        <div><p xmlns:d="http://docbook.org/ns/docbook" id="title"><a href="http://www.jboss.org" class="site_href" rel="nofollow" target="_blank"><strong>JBoss.org</strong></a><a href="http://docs.jboss.org/" class="doc_href" rel="nofollow" target="_blank"><strong>Community Documentation</strong></a></p>
+            <div><h1 class="title"><a id="d0e3"/>apiman - User Guide</h1></div>
+        </div>
+        <hr/>
+    </div>
+    <div class="toc">
+        <dl>
+            <dt><span class="chapter"><a href="#_introduction">1. Introduction</a></span></dt>
+            <dd>
+                <dl>
+            <dt><span class="section"><a href="#_what_is_api_management">1.1. What is API Management?</a></span></dt>
+            <dt><span class="section"><a href="#_project_goals">1.2. Project Goals</a></span></dt>
+            <dt><span class="section"><a href="#_typical_use_cases">1.3. Typical Use Cases</a></span></dt>
+            <dd>
+                <dl>
+            <dt><span class="section"><a href="#_security">1.3.1. Security</a></span></dt>
+            <dt><span class="section"><a href="#_throttling_rate_limiting">1.3.2. Throttling/Rate Limiting</a></span>
+            </dt>
+            <dt><span class="section"><a href="#_metering_billing">1.3.3. Metering/Billing</a></span></dt>
+        </dl>
+        </dd></dl></dd>
+        <dt><span class="chapter"><a href="#_crash_course">2. Crash Course</a></span></dt>
+        <dd>
+            <dl>
+        <dt><span class="section"><a href="#_organizations">2.1. Organizations</a></span></dt>
+        <dt><span class="section"><a href="#_providing_public_apis">2.2. Providing Public APIs</a></span></dt>
+        <dd>
+            <dl>
+        <dt><span class="section"><a href="#_public_api">2.2.1. Public API</a></span></dt>
+        <dt><span class="section"><a href="#_sending_requests_to_your_public_api">2.2.2. Sending Requests to your Public
+            API</a></span></dt>
+        </dl></dd>
+        <dt><span class="section"><a href="#_providing_apis">2.3. Providing APIs`</a></span></dt>
+        <dd>
+            <dl>
+        <dt><span class="section"><a href="#_plans">2.3.1. Plans</a></span></dt>
+        <dt><span class="section"><a href="#_apis">2.3.2. APIs</a></span></dt>
+        </dl></dd>
+        <dt><span class="section"><a href="#_consuming_apis">2.4. Consuming APIs</a></span></dt>
+        <dd>
+            <dl>
+        <dt><span class="section"><a href="#_client_apps">2.4.1. Client Apps</a></span></dt>
+        <dt><span class="section"><a href="#_sending_requests">2.4.2. Sending Requests</a></span></dt>
+        </dl></dd></dl></dd>
+        <dt><span class="chapter"><a href="#_api_manager">3. API Manager</a></span></dt>
+        <dd>
+            <dl>
+        <dt><span class="section"><a href="#_data_model">3.1. Data Model</a></span></dt>
+        <dd>
+            <dl>
+        <dt><span class="section"><a href="#_organizations_2">3.1.1. Organizations</a></span></dt>
+        <dt><span class="section"><a href="#_policies">3.1.2. Policies</a></span></dt>
+        <dt><span class="section"><a href="#_plans_2">3.1.3. Plans</a></span></dt>
+        <dt><span class="section"><a href="#_apis_2">3.1.4. APIs</a></span></dt>
+        <dt><span class="section"><a href="#_client_apps_2">3.1.5. Client Apps</a></span></dt>
+        <dt><span class="section"><a href="#_api_contracts">3.1.6. API Contracts</a></span></dt>
+        <dt><span class="section"><a href="#_policy_chain">3.1.7. Policy Chain</a></span></dt>
+        </dl></dd>
+        <dt><span class="section"><a href="#_user_management">3.2. User Management</a></span></dt>
+        <dd>
+            <dl>
+        <dt><span class="section"><a href="#_new_users">3.2.1. New Users</a></span></dt>
+        <dt><span class="section"><a href="#_membership">3.2.2. Membership</a></span></dt>
+        <dt><span class="section"><a href="#_roles">3.2.3. Roles</a></span></dt>
+        </dl></dd>
+        <dt><span class="section"><a href="#_managing_organizations">3.3. Managing Organizations</a></span></dt>
+        <dt><span class="section"><a href="#_managing_plans">3.4. Managing Plans</a></span></dt>
+        <dd>
+            <dl>
+        <dt><span class="section"><a href="#_creating_a_plan">3.4.1. Creating a Plan</a></span></dt>
+        <dt><span class="section"><a href="#_plan_policies">3.4.2. Plan Policies</a></span></dt>
+        <dt><span class="section"><a href="#_locking_the_plan">3.4.3. Locking the Plan</a></span></dt>
+        </dl></dd>
+        <dt><span class="section"><a href="#_providing_apis_2">3.5. Providing APIs</a></span></dt>
+        <dd>
+            <dl>
+        <dt><span class="section"><a href="#_creating_an_api">3.5.1. Creating an API</a></span></dt>
+        <dt><span class="section"><a href="#_api_implementation">3.5.2. API Implementation</a></span></dt>
+        <dt><span class="section"><a href="#_api_definition">3.5.3. API Definition</a></span></dt>
+        <dt><span class="section"><a href="#_available_plans">3.5.4. Available Plans</a></span></dt>
+        <dt><span class="section"><a href="#_managing_policies">3.5.5. Managing Policies</a></span></dt>
+        <dt><span class="section"><a href="#_publishing_in_the_gateway">3.5.6. Publishing in the Gateway</a></span></dt>
+        <dt><span class="section"><a href="#_api_metrics">3.5.7. API Metrics</a></span></dt>
+        <dt><span class="section"><a href="#_importing_api_s">3.5.8. Importing API(s)</a></span></dt>
+        </dl></dd>
+        <dt><span class="section"><a href="#_consuming_apis_2">3.6. Consuming APIs</a></span></dt>
+        <dd>
+            <dl>
+        <dt><span class="section"><a href="#_consuming_public_apis">3.6.1. Consuming Public APIs</a></span></dt>
+        <dt><span class="section"><a href="#_creating_a_client_app">3.6.2. Creating a Client App</a></span></dt>
+        <dt><span class="section"><a href="#_creating_api_contracts">3.6.3. Creating API Contracts</a></span></dt>
+        <dt><span class="section"><a href="#_api_definition_information">3.6.4. API Definition Information</a></span>
+        </dt>
+        <dt><span class="section"><a href="#_managing_policies_2">3.6.5. Managing Policies</a></span></dt>
+        <dt><span class="section"><a href="#_registering_in_the_gateway">3.6.6. Registering in the Gateway</a></span>
+        </dt>
+        <dt><span class="section"><a href="#_live_api_endpoints">3.6.7. Live API Endpoints</a></span></dt>
+        </dl></dd>
+        <dt><span class="section"><a href="#_versioning">3.7. Versioning</a></span></dt>
+        <dt><span class="section"><a href="#_system_administration">3.8. System Administration</a></span></dt>
+        <dd>
+            <dl>
+        <dt><span class="section"><a href="#_roles_2">3.8.1. Roles</a></span></dt>
+        <dt><span class="section"><a href="#_policy_definitions">3.8.2. Policy Definitions</a></span></dt>
+        <dt><span class="section"><a href="#_gateways">3.8.3. Gateways</a></span></dt>
+        <dt><span class="section"><a href="#_plugins">3.8.4. Plugins</a></span></dt>
+        <dt><span class="section"><a href="#_export_import_data">3.8.5. Export/Import Data</a></span></dt>
+        </dl></dd></dl></dd>
+        <dt><span class="chapter"><a href="#_api_gateway">4. API Gateway</a></span></dt>
+        <dd>
+            <dl>
+        <dt><span class="section"><a href="#_configuration">4.1. Configuration</a></span></dt>
+        <dt><span class="section"><a href="#_invoking_managed_apis">4.2. Invoking Managed APIs</a></span></dt>
+        <dt><span class="section"><a href="#_recording_metrics">4.3. Recording Metrics</a></span></dt>
+        </dl></dd></dl></div>
+    <div class="chapter" lang="en-US">
+        <div class="titlepage">
+            <div>
+                <div><h2 class="title"><a id="_introduction"/>Chapter 1. Introduction</h2></div>
+            </div>
+        </div>
+        <div class="toc">
+            <dl>
+                <dt><span class="section"><a href="#_what_is_api_management">1.1. What is API Management?</a></span>
+                </dt>
+                <dt><span class="section"><a href="#_project_goals">1.2. Project Goals</a></span></dt>
+                <dt><span class="section"><a href="#_typical_use_cases">1.3. Typical Use Cases</a></span></dt>
+                <dd>
+                    <dl>
+                <dt><span class="section"><a href="#_security">1.3.1. Security</a></span></dt>
+                <dt><span class="section"><a href="#_throttling_rate_limiting">1.3.2. Throttling/Rate
+                    Limiting</a></span></dt>
+                <dt><span class="section"><a href="#_metering_billing">1.3.3. Metering/Billing</a></span></dt>
+            </dl>
+            </dd></dl></div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_what_is_api_management"/>1.1. What is API Management?</h2></div>
+                </div>
+            </div>
+            <p>A popular trend in enterprise software development these days is to design client apps to be very
+                decoupled and use APIs to connect them. This approach provides an excellent way to reuse functionality
+                across various applications and business units. Another great benefit of API usage in enterprises is the
+                ability to create those APIs using a variety of disparate technologies.</p>
+            <p>However, this approach also introduces its own pitfalls and disadvantages. Some of those disadvantages
+                include things like:</p>
+            <div class="itemizedlist">
+                <ul>
+                    <li>Difficulty discovering or sharing existing APIs</li>
+                    <li>Difficulty sharing common functionality across API implementations</li>
+                    <li>Tracking of API usage/consumption</li>
+                </ul>
+            </div>
+            <p>API Management is a technology that addresses these and other issues by providing an API Manager to track
+                APIs and configure governance policies, as well as an API Gateway that sits between the API and the
+                client. This API Gateway is responsible for applying the policies configured during management.</p>
+            <p>Therefore an API management system tends to provide the following features:</p>
+            <div class="itemizedlist">
+                <ul>
+                    <li>Centralized governance policy configuration</li>
+                    <li>Tracking of APIs and consumers of those APIs</li>
+                    <li>Easy sharing and discovery of APIs</li>
+                    <li>Leveraging common policy configuration across different APIs</li>
+                </ul>
+            </div>
+        </div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_project_goals"/>1.2. Project Goals</h2></div>
+                </div>
+            </div>
+            <p>The goals of the JBoss API management project are to provide an easy to use and powerful API Manager as
+                well as a small, fast, low-overhead API Gateway to implement standard API management functionality.</p>
+        </div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_typical_use_cases"/>1.3. Typical Use Cases</h2></div>
+                </div>
+            </div>
+            <p>Some common API management use cases include:</p>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_security"/>1.3.1. Security</h3></div>
+                    </div>
+                </div>
+                <p>APIs will very often have a security requirement such that clients connecting to the API must
+                    authenticate in some fashion. Authentication can vary greatly both in the protocols used to
+                    authenticate and the identity source used for validation.</p>
+                <p>It can often be convenient to provide authentication at the API management layer to free up the back
+                    end API from having to do this work. This approach also has the side benefit of centralizing
+                    configuration of authentication for a wide array of disparate APIs.</p>
+                <p>Therefore the API management layer must provide authentication capabilities using a wide range of
+                    protocols including BASIC, digest, OAuth, etc.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_throttling_rate_limiting"/>1.3.2. Throttling/Rate Limiting</h3>
+                        </div>
+                    </div>
+                </div>
+                <p>The API management layer is a convenient place to ensure throttling (also known as rate limiting) to
+                    your APIs. Throttling is a way to prevent individual clients from issuing too many requests to an
+                    API. Because all requests to an API go through the API Gateway it is an excellent place to do this
+                    throttling work.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_metering_billing"/>1.3.3. Metering/Billing</h3></div>
+                    </div>
+                </div>
+                <p>There are a number of reasons why an API provider would be interested in the number of requests made
+                    to her API. The most common reason for public facing APIs is to implement billing based on usage per
+                    consumer. Metering is the feature that provides this API management capability.</p></div>
+        </div>
+    </div>
+    <div class="chapter" lang="en-US">
+        <div class="titlepage">
+            <div>
+                <div><h2 class="title"><a id="_crash_course"/>Chapter 2. Crash Course</h2></div>
+            </div>
+        </div>
+        <div class="toc">
+            <dl>
+                <dt><span class="section"><a href="#_organizations">2.1. Organizations</a></span></dt>
+                <dt><span class="section"><a href="#_providing_public_apis">2.2. Providing Public APIs</a></span></dt>
+                <dd>
+                    <dl>
+                <dt><span class="section"><a href="#_public_api">2.2.1. Public API</a></span></dt>
+                <dt><span class="section"><a href="#_sending_requests_to_your_public_api">2.2.2. Sending Requests to
+                    your Public API</a></span></dt>
+            </dl>
+            </dd>
+            <dt><span class="section"><a href="#_providing_apis">2.3. Providing APIs`</a></span></dt>
+            <dd>
+                <dl>
+            <dt><span class="section"><a href="#_plans">2.3.1. Plans</a></span></dt>
+            <dt><span class="section"><a href="#_apis">2.3.2. APIs</a></span></dt>
+            </dl></dd>
+            <dt><span class="section"><a href="#_consuming_apis">2.4. Consuming APIs</a></span></dt>
+            <dd>
+                <dl>
+            <dt><span class="section"><a href="#_client_apps">2.4.1. Client Apps</a></span></dt>
+            <dt><span class="section"><a href="#_sending_requests">2.4.2. Sending Requests</a></span></dt>
+            </dl></dd></dl></div>
+        <p>This is the "tl;dr" section of the apiman User Guide. Read this section to get a decent high level overview
+            of the concepts you need to know to get going quickly.</p>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_organizations"/>2.1. Organizations</h2></div>
+                </div>
+            </div>
+            <p>Everything in apiman starts with the Organization. First you should create one of these. The Organization
+                is where everything else will be managed. It also allows you to grant specific roles to other users you
+                wish to collaborate with.</p></div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_providing_public_apis"/>2.2. Providing Public APIs</h2></div>
+                </div>
+            </div>
+            <p>The simplest way to get started with apiman is to create a "Public" API. This is simply an API that can
+                be invoked by any client by sending HTTP requests to the appropriate Gateway endpoint. No contracts are
+                required.</p>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_public_api"/>2.2.1. Public API</h3></div>
+                    </div>
+                </div>
+                <p>First, you must have an Organization created. In apiman an API is a representation of your back-end
+                    API, but managed with policies and accessible via the API Gateway instead of directly to the URL of
+                    the back-end API.</p>
+                <p>To create an API, simply navigate to the "APIs" tab for one of your Organizations and click the "New
+                    API" button. You will need to provide a Name and Initial Version for your new API and then click
+                    "Create API" at the bottom of the form.</p>
+                <p>Once you have created an API, you will need to provide some basic configuration, including:</p>
+                <div class="itemizedlist">
+                    <ul>
+                        <li><span class="strong"><strong>API Endpoint</strong></span> - the URL to your back-end API
+                        </li>
+                        <li><span class="strong"><strong>API Type</strong></span> - whether your API is rest or soap
+                        </li>
+                        <li><span class="strong"><strong>API Content-Type</strong></span> - whether your API speaks JSON
+                            or XML
+                        </li>
+                    </ul>
+                </div>
+                <p>Finally, on the "Plans" tab you need to check the "Make this API public" checkbox.</p>
+                <p>Once you have configured all these aspects of the API, you need to <span class="strong"><strong>Publish</strong></span>
+                    the API to the API Gateway. This can be done by clicking the "Publish" button at the top of the
+                    page.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_sending_requests_to_your_public_api"/>2.2.2. Sending Requests to
+                            your Public API</h3></div>
+                    </div>
+                </div>
+                <p>Once the API is published, you can get its URL by navigating to the "Endpoint" tab. From there you
+                    can copy the URL for this managed API. Simply send HTTP requests to this URL as you would your
+                    back-end API!</p>
+                <p>The actual managed endpoint may vary depending on the Gateway, but typically the endpoint is
+                    something like this:</p>
+                <div class="itemizedlist">
+                    <ul>
+                        <li><a class="ulink"
+                               href="http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/" rel="nofollow" target="_blank">http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/</a>
+                        </li>
+                    </ul>
+                </div>
+            </div>
+        </div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_providing_apis"/>2.3. Providing APIs`</h2></div>
+                </div>
+            </div>
+            <p>If you want to know how to provide managed APIs via apiman, this is a fast and dirty quickstart.</p>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_plans"/>2.3.1. Plans</h3></div>
+                    </div>
+                </div>
+                <p>You should already have created an Organization. Navigate to your Organization and switch to the
+                    Plans tab. From there you can create new Plans. A Plan is basically a collection of policies that
+                    will be applied to requests made to APIs being access through it. Plans will be assigned to APIs
+                    during API configuration. Plans give you the opportunity to offer access to the same API with
+                    different SLAs (e.g. different quotas).</p>
+                <p>Use the Policies tab to add zero or more Policies to the Plan. Each Policy has its own unique
+                    configuration.</p>
+                <p>Once you have created all appropriate Policies, you need to <span
+                        class="strong"><strong>Lock</strong></span> the Plan so that it can be used by your APIs. This
+                    can be done by clicking the <span class="emphasis"><em>Lock</em></span> button at the top of the
+                    page. Note that a Policy must be locked for use so that API consumers can have confidence that the
+                    details of the Plan will not change after they have agreed to them.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_apis"/>2.3.2. APIs</h3></div>
+                    </div>
+                </div>
+                <p>After you have created at least one Plan, you can go back to the Organization page and switch to the
+                    APIs tab. From there you can create a new API. In apiman an API is a representation of your back-end
+                    API, but managed with policies and discoverable within the apiman system.</p>
+                <p>Once you have created an API, you will need to provide some basic configuration, including:</p>
+                <div class="itemizedlist">
+                    <ul>
+                        <li><span class="strong"><strong>API Endpoint</strong></span> - the URL to your back-end API
+                        </li>
+                        <li><span class="strong"><strong>API Type</strong></span> - whether your API is rest or soap
+                        </li>
+                        <li><span class="strong"><strong>API Content-Type</strong></span> - whether your API speaks JSON
+                            or XML
+                        </li>
+                        <li><span class="strong"><strong>Plans</strong></span> - One or more Plans</li>
+                    </ul>
+                </div>
+                <p>The Plans are chosen from those available within the Organization. An API can be made available
+                    through any or all of the Organization’s plans. When a client app consumes the API it will do so
+                    through one of the available plans. See the "Consuming APIs" section for details.</p>
+                <p>Once you have configured all necessary aspects of the API, you need to <span class="strong"><strong>Publish</strong></span>
+                    the API to the API Gateway. This can be done by clicking the <span class="emphasis"><em>Publish</em></span>
+                    button at the top of the page.</p></div>
+        </div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_consuming_apis"/>2.4. Consuming APIs</h2></div>
+                </div>
+            </div>
+            <p>If you’re interested in consuming APIs that someone else is providing via apiman, this section should
+                give you a good start.</p>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_client_apps"/>2.4.1. Client Apps</h3></div>
+                    </div>
+                </div>
+                <p>In order to consume an API, you will first need to create a Client App in your Organization. The
+                    Client App <span class="strong"><strong>can</strong></span> (but often does not) exist in the same
+                    Organization as the APIs it consumes. To create a Client App, navigate to the Client Apps tab for
+                    your Organization.</p>
+                <p>Once you have create a Client App, you can search for APIs to consume. There are a number of ways to
+                    search for APIs. Once you have located an API, you must create a Contract between your Client App
+                    and the API. A Contract is always created through one of the Plans provided by the API.</p>
+                <p>After you have created all appropriate API Contracts, you must register the Client App with the API
+                    Gateway. This can be done by clicking the <span class="emphasis"><em>Register</em></span> button at
+                    the top of the page.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_sending_requests"/>2.4.2. Sending Requests</h3></div>
+                    </div>
+                </div>
+                <p>After the Client App is Registered, navigate to the APIs tab to see a list of all the API Contracts
+                    and to get details (by clicking the Expand Details arrow on the left) about each one. This tab is
+                    important because it allows you to find out the API Key assigned to each API Contract. The API Key
+                    is necessary when making managing calls to the API Gateway for a particular API. Additionally, this
+                    tab shows the actual API Gateway endpoint that your client must invoke in order to call the managed
+                    API.</p>
+                <p>The actual managed endpoint may vary depending on the Gateway, but typically the endpoint is
+                    something like this:</p>
+                <div class="itemizedlist">
+                    <ul>
+                        <li><a class="ulink"
+                               href="http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/" rel="nofollow" target="_blank">http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/</a>
+                        </li>
+                    </ul>
+                </div>
+                <p>Requests to managed endpoints must include the API Key so that the Gateway knows which Contract is
+                    being used to invoke the API. The API Key can be sent in one of the following ways:</p>
+                <div class="itemizedlist">
+                    <ul>
+                        <li>As an HTTP Header named <span class="strong"><strong>X-API-Key</strong></span></li>
+                        <li>As a URL query parameter named <span class="strong"><strong>apikey</strong></span></li>
+                    </ul>
+                </div>
+            </div>
+        </div>
+    </div>
+    <div class="chapter" lang="en-US">
+        <div class="titlepage">
+            <div>
+                <div><h2 class="title"><a id="_api_manager"/>Chapter 3. API Manager</h2></div>
+            </div>
+        </div>
+        <div class="toc">
+            <dl>
+                <dt><span class="section"><a href="#_data_model">3.1. Data Model</a></span></dt>
+                <dd>
+                    <dl>
+                <dt><span class="section"><a href="#_organizations_2">3.1.1. Organizations</a></span></dt>
+                <dt><span class="section"><a href="#_policies">3.1.2. Policies</a></span></dt>
+                <dt><span class="section"><a href="#_plans_2">3.1.3. Plans</a></span></dt>
+                <dt><span class="section"><a href="#_apis_2">3.1.4. APIs</a></span></dt>
+                <dt><span class="section"><a href="#_client_apps_2">3.1.5. Client Apps</a></span></dt>
+                <dt><span class="section"><a href="#_api_contracts">3.1.6. API Contracts</a></span></dt>
+                <dt><span class="section"><a href="#_policy_chain">3.1.7. Policy Chain</a></span></dt>
+            </dl>
+            </dd>
+            <dt><span class="section"><a href="#_user_management">3.2. User Management</a></span></dt>
+            <dd>
+                <dl>
+            <dt><span class="section"><a href="#_new_users">3.2.1. New Users</a></span></dt>
+            <dt><span class="section"><a href="#_membership">3.2.2. Membership</a></span></dt>
+            <dt><span class="section"><a href="#_roles">3.2.3. Roles</a></span></dt>
+            </dl></dd>
+            <dt><span class="section"><a href="#_managing_organizations">3.3. Managing Organizations</a></span></dt>
+            <dt><span class="section"><a href="#_managing_plans">3.4. Managing Plans</a></span></dt>
+            <dd>
+                <dl>
+            <dt><span class="section"><a href="#_creating_a_plan">3.4.1. Creating a Plan</a></span></dt>
+            <dt><span class="section"><a href="#_plan_policies">3.4.2. Plan Policies</a></span></dt>
+            <dt><span class="section"><a href="#_locking_the_plan">3.4.3. Locking the Plan</a></span></dt>
+            </dl></dd>
+            <dt><span class="section"><a href="#_providing_apis_2">3.5. Providing APIs</a></span></dt>
+            <dd>
+                <dl>
+            <dt><span class="section"><a href="#_creating_an_api">3.5.1. Creating an API</a></span></dt>
+            <dt><span class="section"><a href="#_api_implementation">3.5.2. API Implementation</a></span></dt>
+            <dt><span class="section"><a href="#_api_definition">3.5.3. API Definition</a></span></dt>
+            <dt><span class="section"><a href="#_available_plans">3.5.4. Available Plans</a></span></dt>
+            <dt><span class="section"><a href="#_managing_policies">3.5.5. Managing Policies</a></span></dt>
+            <dt><span class="section"><a href="#_publishing_in_the_gateway">3.5.6. Publishing in the Gateway</a></span>
+            </dt>
+            <dt><span class="section"><a href="#_api_metrics">3.5.7. API Metrics</a></span></dt>
+            <dt><span class="section"><a href="#_importing_api_s">3.5.8. Importing API(s)</a></span></dt>
+            </dl></dd>
+            <dt><span class="section"><a href="#_consuming_apis_2">3.6. Consuming APIs</a></span></dt>
+            <dd>
+                <dl>
+            <dt><span class="section"><a href="#_consuming_public_apis">3.6.1. Consuming Public APIs</a></span></dt>
+            <dt><span class="section"><a href="#_creating_a_client_app">3.6.2. Creating a Client App</a></span></dt>
+            <dt><span class="section"><a href="#_creating_api_contracts">3.6.3. Creating API Contracts</a></span></dt>
+            <dt><span class="section"><a href="#_api_definition_information">3.6.4. API Definition
+                Information</a></span></dt>
+            <dt><span class="section"><a href="#_managing_policies_2">3.6.5. Managing Policies</a></span></dt>
+            <dt><span class="section"><a href="#_registering_in_the_gateway">3.6.6. Registering in the
+                Gateway</a></span></dt>
+            <dt><span class="section"><a href="#_live_api_endpoints">3.6.7. Live API Endpoints</a></span></dt>
+            </dl></dd>
+            <dt><span class="section"><a href="#_versioning">3.7. Versioning</a></span></dt>
+            <dt><span class="section"><a href="#_system_administration">3.8. System Administration</a></span></dt>
+            <dd>
+                <dl>
+            <dt><span class="section"><a href="#_roles_2">3.8.1. Roles</a></span></dt>
+            <dt><span class="section"><a href="#_policy_definitions">3.8.2. Policy Definitions</a></span></dt>
+            <dt><span class="section"><a href="#_gateways">3.8.3. Gateways</a></span></dt>
+            <dt><span class="section"><a href="#_plugins">3.8.4. Plugins</a></span></dt>
+            <dt><span class="section"><a href="#_export_import_data">3.8.5. Export/Import Data</a></span></dt>
+            </dl></dd></dl></div>
+        <p>There are two layers to the API management project. There is an API Manager which allows end users to
+            centrally manage their APIs. Additionally there is an API Gateway which is responsible for applying those
+            policies to API requests.</p>
+        <p>The API Manager allows end-users to track, configure, and share APIs with other users. All of this is
+            accomplished by the end user by logging into the API Manager user interface (or using the API Manager REST
+            API).</p>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_data_model"/>3.1. Data Model</h2></div>
+                </div>
+            </div>
+            <p>It is perhaps most important to understand the various entities used by the API Manager, as well as their
+                relationships with each other.</p>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_organizations_2"/>3.1.1. Organizations</h3></div>
+                    </div>
+                </div>
+                <p>The top level container concept within the API management project its called the organization. All
+                    other entities are managed within the scope of an organization.</p>
+                <p>When users log into the API management system they must be affiliated with one or more organization.
+                    Users can have different roles within that organization allowing them to perform different actions
+                    and manage different entities. Please see the <span class="emphasis"><em>User Management</em></span>
+                    section below for more details on this topic.</p>
+                <p>What an organization actually represents will depend upon who is using API management. When installed
+                    within a large enterprise, an organization may represent an internal group within IT (for example
+                    the HR group). If installed in the cloud, an organization might represent an external company or
+                    organization.</p>
+                <p>In any case, an organization is required before the end user can create or consume APIs.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_policies"/>3.1.2. Policies</h3></div>
+                    </div>
+                </div>
+                <p>The most important concept in API management is the policy. The policy is the unit of work executed
+                    at runtime in order to implement API governance. All other entities within the API Manager exist in
+                    support of configuring policies and sensibly applying them at runtime.</p>
+                <p>When a request for an API is made at runtime, a policy chain is created and applied to the inbound
+                    request, prior to proxying that request to the back-end API implementation. This policy chain
+                    consists of policies configured in the API Manager.</p>
+                <p>An individual policy consists of a type (e.g. authentication or rate limiting) as well as
+                    configuration details specific to the type and instance of that policy. Multiple policies can be
+                    configured per API resulting in a policy chain that is applied at runtime.</p>
+                <p>It is very important to understand that policies can be configured at three different levels within
+                    API management. Policies can be configured on an API, on a plan, or on a client app. For more
+                    details please see the sections below.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_plans_2"/>3.1.3. Plans</h3></div>
+                    </div>
+                </div>
+                <p>A plan is a set of policies that define a level of service for an API. When an API is consumed it may
+                    be consumed through a plan. Please see the section on <span class="emphasis"><em>API Contracts</em></span>
+                    for more information.</p>
+                <p>An organization can have multiple plans associated with it. Typically each plan within an
+                    organization consists of the same set of policies but with different configuration details. For
+                    example, an organization might have a Gold plan with a rate limiting policy that restricts consumers
+                    to 1000 requests per day. The same organization may then have a Silver plan which is also configured
+                    with a rate limiting policy, but which restricts consumers to 500 requests per day.</p>
+                <p>Once a plan has been fully configured (all desired policies added and configured) it must be locked
+                    so that it can be used by APIs. This is done so that API providers can’t change the details of the
+                    plan out from underneath the client app developers who are using it.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_apis_2"/>3.1.4. APIs</h3></div>
+                    </div>
+                </div>
+                <p>An API represents an external API that is being governed by the API management system. An API
+                    consists of a set of metadata including name and description as well as an external endpoint
+                    defining the API implementation. The external API implementation endpoint includes:</p>
+                <div class="itemizedlist">
+                    <ul>
+                        <li>The type/protocol of the endpoint (e.g. REST or SOAP)</li>
+                        <li>The endpoint content type (e.g. XML or JSON)</li>
+                        <li>The endpoint location (URL) so that the API can be properly proxied to at runtime.</li>
+                    </ul>
+                </div>
+                <p>In addition, policies can be configured on an API. Typically, the policies applied to APIs are things
+                    like authentication, or caching. Any policies configured on API will be applied at runtime
+                    regardless of the client app and API contract. This is why authentication is a common policy to
+                    configure at the API level.</p>
+                <p>APIs may be offered through one or more plans configured in the same organization. When plans are
+                    used, API consumers (client apps) must consume the API through one of those plans. Please see the
+                    section on <span class="emphasis"><em>API Contracts</em></span> for more information. Alternatively,
+                    an API can simply be marked as "Public", in which case any client may access the API’s managed
+                    endpoint without providing an API Key.</p>
+                <p>Only once an API is fully configured, including its policies, implementation, and plans can it be
+                    published to the Gateway for consumption by client apps. Once an API has been published, it can only
+                    be changed if it is a "Public" API. APIs that are offered via Plans are immutable - to change them
+                    you must create a new version. The reason for this is that API consumers may have created Contracts
+                    with your API, through your Plan. When they do this, they must agree to some terms and conditions.
+                    It is therefore understood that the terms to which they are agreeing will not change. However, for
+                    Public APIs, there is no such agreement. For this reason, you can make changes to Public APIs and
+                    re-publish them at any time.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_client_apps_2"/>3.1.5. Client Apps</h3></div>
+                    </div>
+                </div>
+                <p>A client app represents a consumer of an API. Typical API consumers are things like mobile
+                    applications and B2B applications. Regardless of the actual implementation, a client app must be
+                    added to the API management system so that Contracts can be created between it and the APIs it
+                    wishes to consume.</p>
+                <p>A client app consists of basic metadata such as name and description. Policies can also be configured
+                    on a client app, but are optional.</p>
+                <p>Finally, API Contracts can be created between a client app and the API(s) it wishes to consume. Once
+                    the API Contracts are created, the client app can be registered with the runtime gateway. Policies
+                    and Contracts can be added/removed at any time. However, after any changes are made, you must
+                    re-register the client app.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_api_contracts"/>3.1.6. API Contracts</h3></div>
+                    </div>
+                </div>
+                <p>An API contract is simply a link between a Client App and an API through a plan offered by that API.
+                    This is the only way that a client app can consume an API. If there are no client apps that have
+                    created API contracts with an API, that API cannot be accessed through the API management runtime
+                    gateway (unless of course the API is "Public").</p>
+                <p>When an API Contract is created, the system generates a unique API key specific to that contract. All
+                    requests made to the API by a Client App through the API Gateway must include this API key. The API
+                    key is used to create the runtime policy chain from the policies configured on the API, plan, and
+                    client app.</p>
+                <p>API Contracts can only be created between Client Apps and published APIs which are offered through at
+                    least one Plan. An API Contract cannot be created between a Client App and a Public API.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_policy_chain"/>3.1.7. Policy Chain</h3></div>
+                    </div>
+                </div>
+                <p>A policy chain is an ordered sequence of policies that are applied when a request is made for an API
+                    through the API Gateway. The order that policies are applied is important and is as follows:</p>
+                <div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory"
+                     class="orderedlist">
+                    <ol>
+                        <li>Client App</li>
+                        <li>Plan</li>
+                        <li>API</li>
+                    </ol>
+                </div>
+                <p>Within these individual sections, the end user can specify the order of the policies.</p>
+                <p>When a request for an API is received by the API Gateway the policy chain is applied to the request
+                    in the order listed above. If none of the policies fail, the API Gateway will proxy the request to
+                    the backend API implementation. Once a response is received from the back end API implementation,
+                    the policy chain is then applied in reverse order to that response. This allows each policy to be
+                    applied twice, once to the inbound request and then again to the outbound response.</p></div>
+        </div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_user_management"/>3.2. User Management</h2></div>
+                </div>
+            </div>
+            <p>The API Manager offers user role capabilities at the organization level. Users can be members of
+                organizations and have specific roles within those organizations. The roles themselves are configurable
+                by an administrator, and each role provides the user with a set of permissions that determine what
+                actions the user can take within an organization.</p>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_new_users"/>3.2.1. New Users</h3></div>
+                    </div>
+                </div>
+                <p>Users must self register with the management UI in order to be given access to an organization or to
+                    create their own organization. In some configurations it is possible that user self registration is
+                    unavailable and instead user information is provided by a standard source of identity such as LDAP.
+                    In either case, the actions a user can take are determined by that user’s role memberships within
+                    the context of an organization.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_membership"/>3.2.2. Membership</h3></div>
+                    </div>
+                </div>
+                <p>Users can be members of organizations. All memberships in an organization include the specific roles
+                    the user is granted. It is typically up to the owner of an organization to grant role memberships to
+                    the members of that organization.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_roles"/>3.2.3. Roles</h3></div>
+                    </div>
+                </div>
+                <p>Roles determine the capabilities granted a user within the context of the organization. The roles
+                    themselves and the capabilities that those roles grant are configured by system administrators. For
+                    example, administrators would typically configure the following roles:</p>
+                <div class="itemizedlist">
+                    <ul>
+                        <li>Organization Owner</li>
+                        <li>API Developer</li>
+                        <li>Client App Developer</li>
+                    </ul>
+                </div>
+                <p>Each of these roles is configured by an administrator to provide a specific set of permissions
+                    allowing the user to perform relevant actions appropriate to that role. For example the Client App
+                    Developer role would grant an end user the ability to manage client apps and API contracts for those
+                    client apps. However that user would not be able to create or manage the organization’s APIs or
+                    plans.</p></div>
+        </div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_managing_organizations"/>3.3. Managing Organizations</h2></div>
+                </div>
+            </div>
+            <p>Before any other actions can be taken an organization must exist. All other operations take place within
+                the context of an organization.</p>
+            <p>In order to create an organization click the <span class="emphasis"><em>Create a New
+                Organization</em></span> link found on the dashboard page that appears when you first login. Simply
+                provide an organization name and description and then click the <span class="emphasis"><em>Create
+                    Organization</em></span> button. If successful you will be taken to the organization details page.
+            </p>
+            <p>If you create multiple organizations, you can see the list of those organizations on your home page. For
+                example, you may click the <span class="emphasis"><em>Go to My Organizations</em></span> link from the
+                dashboard page.</p></div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_managing_plans"/>3.4. Managing Plans</h2></div>
+                </div>
+            </div>
+            <p>Plans must be managed within the scope of an organization. Once created, plans can be used for any API
+                defined within that same organization. To see a list of existing plans for an organization, navigate to
+                the <span class="emphasis"><em>Plans</em></span> tab for that organization on its details page.</p>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_creating_a_plan"/>3.4.1. Creating a Plan</h3></div>
+                    </div>
+                </div>
+                <p>Plans can be created easily from the <span class="emphasis"><em>Plans</em></span> tab of the
+                    organization details page. Simply click the <span class="emphasis"><em>New Plan</em></span> button
+                    and then provide a plan name, version, and description. Once that information is provided, click the
+                    <span class="emphasis"><em>Create Plan</em></span> button. If successfully created, you’ll be taken
+                    to the plan details page.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_plan_policies"/>3.4.2. Plan Policies</h3></div>
+                    </div>
+                </div>
+                <p>If you switch to the <span class="emphasis"><em>Policies</em></span> tab on the plan details page you
+                    can configure the list of policies for the plan. Please note that the order of the policies can be
+                    changed and is important. The order that the policies appear in the user interface determines the
+                    order they will be applied at runtime. You can drag a policy up and down the list to change the
+                    order.</p>
+                <p>To add a policy to the plan click the <span class="emphasis"><em>Add Policy</em></span> button. On
+                    the resulting page choose the type of policy you wish to create and then configure the details for
+                    that policy. Once you have configured the details click the <span class="emphasis"><em>Add
+                        Policy</em></span> button to add the policy to the plan.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_locking_the_plan"/>3.4.3. Locking the Plan</h3></div>
+                    </div>
+                </div>
+                <p>Once all your plan policies are added and configured the way you want them, you will need to Lock the
+                    plan. This can be done from any tab of the Plan UI page. Locking the plan will prevent all future
+                    policy changes, and make the plan available for use by APIs.</p></div>
+        </div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_providing_apis_2"/>3.5. Providing APIs</h2></div>
+                </div>
+            </div>
+            <p>A core capability of API management is for end users to create, manage, and configure APIs they wish to
+                provide. This section explains the steps necessary for users to provide those APIs.</p>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_creating_an_api"/>3.5.1. Creating an API</h3></div>
+                    </div>
+                </div>
+                <p>First the user must create an API within an organization. If an organization does not yet exist one
+                    can easily be created. See the <span class="emphasis"><em>Managing Organizations</em></span> section
+                    for details.</p>
+                <p>From the organization details page, navigate to the <span class="emphasis"><em>APIs</em></span> tab
+                    and click on the <span class="emphasis"><em>New API</em></span> button. You will be asked to provide
+                    an API name, version number, and description.</p>
+                <p>If successfully created, you will be taken to the API details page. From here you can configure the
+                    details of the API.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_api_implementation"/>3.5.2. API Implementation</h3></div>
+                    </div>
+                </div>
+                <p>Every API must be configured with an API implementation. The implementation indicates the external
+                    API that the API Gateway will proxy to if all the policies are successfully applied. Click the <span
+                            class="emphasis"><em>Implementation</em></span> tab to configure the API endpoint and API
+                    type details on your API.</p>
+                <p>The <span class="emphasis"><em>Implementation</em></span> tab is primarily used to configure the
+                    details of the back-end API that apiman will proxy to at runtime. You must configure the following:
+                </p>
+                <div class="itemizedlist">
+                    <ul>
+                        <li><span class="strong"><strong>Endpoint URL</strong></span> - The URL that apiman will use to
+                            proxy a request made for this API.
+                        </li>
+                        <li><span class="strong"><strong>Endpoint Type</strong></span> - Currently either REST or SOAP
+                            (not presently used, future information)
+                        </li>
+                        <li><span class="strong"><strong>Endpoint Content Type</strong></span> - Choose between JSON and
+                            XML, information primarily used to respond with a policy failure or error in the appropriate
+                            format.
+                        </li>
+                    </ul>
+                </div>
+                <p>Additionally, the <span class="emphasis"><em>Implementation</em></span> tab allows you to configure
+                    any security options that might be required when proxying requests to the back-end API. For example,
+                    if you are using two-way SSL to ensure full security between the API Gateway and your back-end API,
+                    you may configure that here. We also support simple BASIC authentication between the gateway and
+                    your back end API. Please note that BASIC authentication is not ideal, and especially insecure if
+                    not using SSL/HTTPS to connect to the back end API.</p>
+                <p>If the apiman administrator has configured multiple Gateways (see the "System Administration /
+                    Gateways" section below), then the <span class="emphasis"><em>Implementation</em></span> tab will
+                    also include an option that will let you choose which Gateway(s) to use when publishing. You may
+                    select one or more Gateway in this case. If you choose multiple Gateways, then when you click the
+                    <span class="emphasis"><em>Publish</em></span> button, apiman will publish the API to <span
+                            class="strong"><strong>all</strong></span> of the selected Gateways.</p>
+                <div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory"
+                     class="tip"><h2>Tip</h2>
+                    <p>If a single Gateway has been configured, then you don’t have a choice, and so the UI will hide
+                        the Gateway selector entirely and simply pick the default Gateway for you.</p></div>
+                <p>Do not forget to click the Save button when you are done making changes.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_api_definition"/>3.5.3. API Definition</h3></div>
+                    </div>
+                </div>
+                <p>As a provider of an API, it is best to include as much information about the API as possible, so that
+                    consumers can not only create contracts, but also learn how to make calls. For this purpose, you can
+                    optionally include an API Definition document by adding it to your API on the Definition tab.
+                    Currently the only supported type of definition file is Swagger. Include a swagger spec document
+                    here so that consumers of your API can browse information about your API directly in the API Manager
+                    UI.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_available_plans"/>3.5.4. Available Plans</h3></div>
+                    </div>
+                </div>
+                <p>Before an API can be consumed by a client app, it must make itself available through at least one of
+                    the organization’s plans (or it must be marked as "Public"). Marking an API as public or making an
+                    API available through one or more plan can be done by navigating to the <span class="emphasis"><em>Plans</em></span>
+                    tab on the API details page. The <span class="emphasis"><em>Plans</em></span> tab will list all of
+                    the available plans defined by the organization. Simply choose one or more plan from this list. If
+                    no plans are needed, you can instead mark the API as "Public", making it available to be consumed
+                    anonymously by any client. Although an API can be <span class="strong"><strong>both</strong></span>
+                    Public and available through one or more plan, it is unusual to do so.</p>
+                <div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory"
+                     class="tip"><h2>Tip</h2>
+                    <p>After you have either marked the API as "public" or selected at least one plan, make sure to
+                        click the Save button.</p></div>
+            </div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_managing_policies"/>3.5.5. Managing Policies</h3></div>
+                    </div>
+                </div>
+                <p>API policies can be added and configured by navigating to the <span
+                        class="emphasis"><em>Policies</em></span> tab on the API details page. The <span
+                        class="emphasis"><em>Policies</em></span> tab presents a list of all the policies configured for
+                    this API. To add another policy to the API click the <span class="emphasis"><em>Add
+                        Policy</em></span> button. On the resulting page choose the type of policy you wish to create
+                    and then configure the details for that policy. Once you have configured the details click the <span
+                            class="emphasis"><em>Add Policy</em></span> button to add the policy to the API.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_publishing_in_the_gateway"/>3.5.6. Publishing in the Gateway</h3>
+                        </div>
+                    </div>
+                </div>
+                <p>After all of the configuration is complete for an API, it is time to publish the API to the runtime
+                    gateway. This can be done from any tab on the API details page by clicking the <span
+                            class="emphasis"><em>Publish</em></span> button in the top section of the UI. If successful,
+                    the status of the API will change to "Published" and the <span
+                            class="emphasis"><em>Publish</em></span> button will disappear.</p>
+                <div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory"
+                     class="tip"><h2>Tip</h2>
+                    <p>If the API cannot yet be published (the <span class="emphasis"><em>Publish</em></span> button is
+                        disabled) then a notification will appear near the button and will read "Why Can’t I publish?"
+                        Clicking this notification will provide details about what information is still required before
+                        the API can be published to the Gateway.</p></div>
+                <p>Once the API has been published, it may or may not be editable depending on whether it is a "Public"
+                    API or not. For "Public" APIs, you will be able to continue making changes. After at least one
+                    change is made, you will have the option to "Re-Publish" the API to the Gateway. Doing so will
+                    update all information about the API in the Gateway. However, if the API is <span
+                            class="strong"><strong>not</strong></span> Public, then the API will be immutable -
+                    therefore in order to make any changes you will need to create a new version of the API.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_api_metrics"/>3.5.7. API Metrics</h3></div>
+                    </div>
+                </div>
+                <p>Once an API is published and is being consumed at runtime, metrics information about that usage is
+                    recorded in a metrics storage system. See the Metrics section of the API Gateway documentation for
+                    more about how and when metrics data is recorded.</p>
+                <p>If an API has been used by at least once, then it will have metrics information available. This
+                    information can be viewed in the <span class="emphasis"><em>Metrics</em></span> tab on the API’s
+                    details page. On this page you can choose the type of metric you wish to see (e.g. Usage metrics and
+                    Response Type metrics) as well as a pre-defined time range (e.g. Last 30 Days, Last Week, etc…).</p>
+                <p>The API Metrics page is a great way to figure out how often your API is used, and in what ways.</p>
+            </div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_importing_api_s"/>3.5.8. Importing API(s)</h3></div>
+                    </div>
+                </div>
+                <p>As an alternative to manually creating and configuring an API, apiman also supports importing an API
+                    from a globally configured API Catalog.</p>
+                <div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory"
+                     class="tip"><h2>Tip</h2>
+                    <p>The API Catalog is configured by the apiman system administrator/installer. See the installation
+                        guide for more information about how to configure a custom API Catalog.</p></div>
+                <p>An API can be imported into apiman in one of two ways. First, from the Organization’s "APIs" tab you
+                    can click the down-arrow next to the "New API" button and choose the "Import API(s)" option. This
+                    results in a wizard that will guide you through importing one or more API from the catalog into the
+                    Organization. This wizard will allow you to search for, find, and select multiple APIs. It will then
+                    walk you through choosing your Plans or making the APIs "Public". Once all the wizard pages are
+                    completed, you can then import the API(s).</p>
+                <div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory"
+                     class="tip"><h2>Tip</h2>
+                    <p>The Import API(s) wizard above is the only way to import multiple APIs at the same time.</p>
+                </div>
+                <p>Another option for importing an API from the catalog is to use the API Catalog Browser UI, which can
+                    be found by clicking the "Browse available/importable APIs" link on the API Manager Dashboard. This
+                    link will open the catalog browser, allowing you to search for APIs to import. The catalog browser
+                    is a friendlier interface, but only allows you to import a single API at a time.</p></div>
+        </div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_consuming_apis_2"/>3.6. Consuming APIs</h2></div>
+                </div>
+            </div>
+            <p>After the API providers have added a number of APIs to the API management system, those APIs can be
+                consumed by Client Apps. This section explains how to consume APIs.</p>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_consuming_public_apis"/>3.6.1. Consuming Public APIs</h3></div>
+                    </div>
+                </div>
+                <p>If you have marked an API as "Public", then consuming it is a simple matter of sending a request to
+                    the appropriate API Gateway endpoint. The managed API endpoint may vary depending on the Gateway
+                    being used, but it typically of the following form:</p>
+                <div class="itemizedlist">
+                    <ul>
+                        <li><a class="ulink"
+                               href="http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/" rel="nofollow" target="_blank">http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/</a>
+                        </li>
+                    </ul>
+                </div>
+                <p>Simply send requests to the managed API endpoint, and do not include an API Key.</p>
+                <div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory"
+                     class="tip"><h2>Tip</h2>
+                    <p>The managed endpoint URL can be easily determined in the UI by navigating to the "Endpoint" tab
+                        on the API details UI page.</p></div>
+            </div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_creating_a_client_app"/>3.6.2. Creating a Client App</h3></div>
+                    </div>
+                </div>
+                <p>In order to consume an API that is not "Public" you must first create a client app. Client Apps must
+                    exist within the context of an organization. If an organization does not yet exist for this purpose,
+                    simply create a new organization. See the section above on <span class="emphasis"><em>Managing
+                        Organizations</em></span> for more information.</p>
+                <p>To create a new Client App click the <span class="emphasis"><em>Create a New Client App</em></span>
+                    link on the dashboard page. On the resulting page provide a client app name, version, and
+                    description and then click the <span class="emphasis"><em>Create Client App</em></span> button. If
+                    the client app is successfully created, you will be taken to the client app details page.</p>
+                <div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory"
+                     class="tip"><h2>Tip</h2>
+                    <p>You can also create a Client App within an Organization by going to the Organization’s "Client
+                        Apps" tab and clicking the "New Client App" button.</p></div>
+            </div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_creating_api_contracts"/>3.6.3. Creating API Contracts</h3></div>
+                    </div>
+                </div>
+                <p>The primary action taken when configuring a client app is the creation of Contracts to APIs. This is
+                    what we mean when we say "consuming an API". There are a number of ways to create API contracts.
+                    This section will describe the most useful of these options.</p>
+                <p>From the Client App details page, you can find an API to consume by clicking on the <span
+                        class="emphasis"><em>Search for APIs to consume</em></span> link in the top section of the page.
+                    You will be taken to a page that will help you search for and find the API you wish to consume.</p>
+                <p>Use the controls on this page to search for an API. Once you have found the API you are interested
+                    in, click on its name in the search results area. This will take you to the API details page for API
+                    consumers. The consumer-oriented API details page presents you with all of the information necessary
+                    to make a decision about how to consume the API. It includes a list of all the API versions and a
+                    list of all of the available plans the API can be consumed through.</p>
+                <p>Note that you can click on an individual plan to see the details of the policies that will be
+                    enforced should that plan be chosen. Click on the <span class="emphasis"><em>Create
+                        Contract</em></span> button next to the plan you wish to use when consuming this API. You will
+                    be taken to the new contract page to confirm that you want to create an API contract to this API
+                    through the selected plan. If you are sure this is the API contract you wish to create, click the
+                    <span class="emphasis"><em>Create Contract</em></span> button and then agree to the terms and
+                    conditions. If successful, you will be taken to the <span class="emphasis"><em>Contracts</em></span>
+                    tab on the client app details page.</p>
+                <p>From the <span class="emphasis"><em>Contracts</em></span> tab on the client app details page you can
+                    see the list of API contracts already created for this client app. It is also possible to break API
+                    contracts from this same list by clicking an appropriate <span class="emphasis"><em>Break
+                        Contract</em></span> button.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_api_definition_information"/>3.6.4. API Definition Information
+                        </h3></div>
+                    </div>
+                </div>
+                <p>If An API provider has included An API Definition for the API they are providing, you will be
+                    presented with an additional link on the consumer-oriented API details page labeled "API
+                    Definition". This link will take you to a page where you can browse the detailed documentation for
+                    the API. The detailed documentation should be very helpful in learning what resources and operations
+                    are supported by the API, which will aid in figuring out how precisely to consume the API.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_managing_policies_2"/>3.6.5. Managing Policies</h3></div>
+                    </div>
+                </div>
+                <p>Just like plans and APIs, client apps can have configured policies. The <span class="emphasis"><em>Policies</em></span>
+                    tab will present a list of all the policies configured for this client app. To add another policy to
+                    the client app click the <span class="emphasis"><em>Add Policy</em></span> button. On the resulting
+                    page choose the type of policy you wish to create and then configure the details for that policy.
+                    Once you have configured the details click the <span class="emphasis"><em>Add Policy</em></span>
+                    button to add the policy to the client app.</p>
+                <p>Of course, just like for Plans and APIs, you can manage the Client App policies from the <span
+                        class="emphasis"><em>Policies</em></span> tab. This allows you to not only add new policies but
+                    also edit, remove, and reorder them.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_registering_in_the_gateway"/>3.6.6. Registering in the Gateway
+                        </h3></div>
+                    </div>
+                </div>
+                <p>After at least one API contract has been created for the client app, it is possible to register the
+                    client app with the runtime gateway. Until the client app is registered with the runtime gateway, it
+                    is not possible to make requests to back-end APIs on behalf of that client app.</p>
+                <p>To register the client app with the gateway, simply click the "Register" button at the top of the
+                    Client App details UI page (any tab). If the status of the client app is "Ready", then the <span
+                            class="emphasis"><em>Register</em></span> button should be enabled. If successful, the
+                    client app status will change to "Registered", and the <span
+                            class="emphasis"><em>Register</em></span> button will disappear.</p>
+                <p>Once the client app is registered, you can continue to make changes to it (such as modify its
+                    policies or create/break API Contracts). If you do make any changes, then the <span
+                            class="emphasis"><em>Re-Register</em></span> button will become enabled. Whenever you make
+                    changes to your Client App, you <span class="strong"><strong>must</strong></span> Re-Register it
+                    before those changes will show up in the Gateway.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_live_api_endpoints"/>3.6.7. Live API Endpoints</h3></div>
+                    </div>
+                </div>
+                <p>After a client app has been registered with the runtime gateway, it is possible to send requests to
+                    the back-end APIs on behalf of that client app (through the client app’s API contracts). To do this
+                    you must know the URL of the managed API. This URL <span class="emphasis"><em>optionally</em></span>
+                    includes the API Key generated for the API Contract.</p>
+                <p>To view a list of all of these managed endpoints, navigate to the <span
+                        class="emphasis"><em>APIs</em></span> tab on the API detail page. Each API contract is
+                    represented in the list of managed endpoints. You can expand an entry in the managed API endpoints
+                    table by clicking the <span class="emphasis"><em>&gt;</em></span> icon in the first column. The
+                    resulting details will help you figure out the appropriate endpoint to use for a particular managed
+                    API.</p>
+                <div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory"
+                     class="tip"><h2>Tip</h2>
+                    <p>There are two ways to pass the API Key to the Gateway when you make a request for a Managed
+                        Endpoint. You can either include the API Key in the URL as a query parameter, or you can pass it
+                        via the <span class="strong"><strong>X-API-Key</strong></span> HTTP header.</p></div>
+            </div>
+        </div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_versioning"/>3.7. Versioning</h2></div>
+                </div>
+            </div>
+            <p>Many of the entities in the API Manager support multiple simultaneous versions. These include the
+                following:</p>
+            <div class="itemizedlist">
+                <ul>
+                    <li>Plans</li>
+                    <li>APIs</li>
+                    <li>Client Apps</li>
+                </ul>
+            </div>
+            <p>Typically once an entity is frozen (e.g. Locked or Published) it can no longer be modified. But often as
+                things change, modifications to the API Management configuration are necessary. For example, as an API
+                implementation evolves, the policies associated with it in the API Manager may need to change.
+                Versioning allows this to happen, by providing a way for a user to create a new version of a particular
+                API (or Client App or Plan) and then making changes to it.</p>
+            <p>To create a new version of an entity, view the details of the entity and click the "New Version" button
+                in the UI. This will allow you to make a new version of the entity. You can either make a simple, empty
+                new version or you can make a clone of an existing version. The latter is typically more convenient when
+                making incremental changes.</p>
+            <div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory"
+                 class="tip"><h2>Tip</h2>
+                <p>"Public" APIs and Client Apps can be modified and re-published (or re-registered) in the Gateway
+                    without the need to create a new version.</p></div>
+        </div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_system_administration"/>3.8. System Administration</h2></div>
+                </div>
+            </div>
+            <p>There are several "global" settings that must be configured/managed by an apiman administrator. These
+                global settings are managed by navigating to the <span class="strong"><strong>System
+                    Administration</strong></span> section of the API Manager UI.</p>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_roles_2"/>3.8.1. Roles</h3></div>
+                    </div>
+                </div>
+                <p>Users must become a member of an organization before being allowed to manage any of the plans, APIs,
+                    or client apps contained within it. When a user is made a member of an organization, they are
+                    granted a specific role within that organization. Typical examples of roles are <span
+                            class="strong"><strong>Organization Owner</strong></span>, <span class="strong"><strong>API
+                        Provider</strong></span>, and <span class="strong"><strong>Client App Developer</strong></span>.
+                    These roles each grant different specific privileges to the user. For example, a user with the <span
+                            class="strong"><strong>Client App Developer</strong></span> role will be able to manage the
+                    organization’s client apps but not its APIs or plans.</p>
+                <p>The roles that are available when adding a member to an organization are managed in the <span
+                        class="strong"><strong>Roles</strong></span> section of the <span class="strong"><strong>System
+                    Administration</strong></span> UI. The apiman admin can create as many roles as she wishes, giving
+                    each one a name, description, and the set of permissions it grants. Additionally, certain roles may
+                    be automatically granted to users who create new organizations. At least one such role must be
+                    present, otherwise organizations cannot be created.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_policy_definitions"/>3.8.2. Policy Definitions</h3></div>
+                    </div>
+                </div>
+                <p>The policies available when configuring APIs, Plans, and Client Apps are controlled by the <span
+                        class="strong"><strong>Policy Definitions</strong></span> known to apiman. These definitions are
+                    stored in the API Manager and are added by the apiman admin. Typically these are added once and
+                    rarely changed. But as new versions of apiman are released, additional policies will be made
+                    available. For each policy, a policy definition must be configured in the <span
+                            class="strong"><strong>System Administration</strong></span> UI.</p>
+                <p>Additionally, it is possible for a plugin, when installed, to contribute one or more policy
+                    definitions to the list. This is a very common way for new policy definitions to be added to
+                    apiman.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_gateways"/>3.8.3. Gateways</h3></div>
+                    </div>
+                </div>
+                <p>Apiman allows multiple logical Gateways to be configured. The Gateway is the server that actually
+                    applies the policies configured in the API Manager to live requests to managed APIs. When using
+                    apiman, at least one Gateway must be running and configured in the API Manager. However, there is no
+                    limit to the total number of Gateways that may be running. The typical reason to have multiple
+                    Gateways is when some APIs are very high volume and others are not. In this case, the high volume
+                    APIs could be published to a Gateway that can handle such load, while the low volume APIs could be
+                    published to another (perhaps cheaper) Gateway.</p>
+                <p>Another reason you may want multiple Gateways if if you need some of your APIs to be provided in a
+                    particular physical region and others in a different one. In this case, you may have a Gateway
+                    (perhaps clustered) running in a US data center, while another Gateway (different cluster) is
+                    running separately in a data center in Europe.</p>
+                <p>In all cases, the apiman admin must configure these Gateways in the <span class="strong"><strong>System
+                    Administration</strong></span> UI. Each Gateway has a name, description, and configuration endpoint.
+                    The configuration endpoint is what the API Manager will use when publishing APIs and client apps
+                    into the Gateway.</p>
+                <p>When configuring an API Gateway you will need to include the authentication credentials required to
+                    invoke the API Gateway configuration REST API. Typically this user must have the <span
+                            class="emphasis"><em>apipublisher</em></span> role in order to successfully talk to the API
+                    Gateway. The Gateway UI includes a <span class="strong"><strong>Test Gateway</strong></span> button
+                    which will attempt to contact the Gateway API with the credentials included. If successful, the test
+                    button will turn green. If unsuccessful, details about the failure will be displayed and the test
+                    button will turn red.</p></div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_plugins"/>3.8.4. Plugins</h3></div>
+                    </div>
+                </div>
+                <p>Apiman supports contributing additional functionality via a powerful plugin mechanism. Plugins can be
+                    managed by an administrator within the API Manager UI. The plugin management administration page
+                    allows an admin to add and delete plugins.</p>
+                <div class="section" lang="en-US">
+                    <div class="titlepage">
+                        <div>
+                            <div><h4 class="title"><a id="_adding_plugins"/>3.8.4.1. Adding Plugins</h4></div>
+                        </div>
+                    </div>
+                    <p>The Plugin admin page has two tabs - one shows the list of plugins currently installed, and the
+                        other shows a list of "Available Plugins". The list of available plugins comes from a plugin
+                        registry that is configured when apiman is installed (see the Installation Guide for details on
+                        how to configure a custom plugin registry). By default, the "official" apiman plugins will show
+                        up in the list.</p>
+                    <p>A custom plugin is typically added by clicking on the <span class="emphasis"><em>Add Custom
+                        Plugin</em></span> button found on the "Available Plugins" tab. This allows you to install a
+                        plugin that is not found in the configured plugin registry. When installing a custom plugin, you
+                        must provide the "coordinates" of the plugin. All plugins are actually maven artifacts, and as
+                        such their coordinates consist of the following maven properties:</p>
+                    <div class="itemizedlist">
+                        <ul>
+                            <li>Group ID</li>
+                            <li>Artifact ID</li>
+                            <li>Version</li>
+                            <li>Classifier (optional)</li>
+                            <li>Type (optional, defaults to <span class="emphasis"><em>war</em></span>)</li>
+                        </ul>
+                    </div>
+                    <p>When installing a plugin from the plugin registry, simply locate it in the list shown on the
+                        "Available Plugins" tab and then click the "Install" action. This will again take you to the Add
+                        Plugin page, but with all of the appropriate information already filled in. At this point you
+                        should only need to click the "Add Plugin" button.</p>
+                    <p>Plugins primarily are used to contribute custom policies to apiman. These policies are
+                        automatically discovered (if they exist in the plugin) when a plugin is added to the API
+                        Manager. Policies that have been contributed via a plugin will appear in the Policy Definitions
+                        admin page along with the built-in policies.</p></div>
+                <div class="section" lang="en-US">
+                    <div class="titlepage">
+                        <div>
+                            <div><h4 class="title"><a id="_deleting_plugins"/>3.8.4.2. Deleting Plugins</h4></div>
+                        </div>
+                    </div>
+                    <p>At any time you may choose to delete a plugin. Note that if the plugin was contributing one or
+                        more policies to apiman, then the policy will no longer be available for use when configuring
+                        your Plans, APIs, and Client Apps. However, if the policy is already in use by one of these
+                        entities, it will continue to work. In other words, deleting a plugin only removes the policy
+                        for use by new entities, it does <span class="strong"><strong>not</strong></span> break existing
+                        usages.</p>
+                    <p>To delete a plugin, simply click the "Delete" action for the appropriate plugin on the "Installed
+                        Plugins" tab. After confirming the delete, the plugin should disappear from the list.</p></div>
+                <div class="section" lang="en-US">
+                    <div class="titlepage">
+                        <div>
+                            <div><h4 class="title"><a id="_upgrading_plugins"/>3.8.4.3. Upgrading Plugins</h4></div>
+                        </div>
+                    </div>
+                    <p>If apiman determines that a plugin can be upgraded, then an "Upgrade Plugin" action button will
+                        show up for the plugin in the "Installed Plugins" tab. This action will be represented as an up
+                        arrow icon button. When clicked, you will be prompted for the version of the plugin you wish to
+                        upgrade <span class="strong"><strong>to</strong></span>. The result will be that a new version
+                        of the plugin will be downloaded and installed, replacing the older version you had before. Note
+                        that any Plans, APIs, or Client Apps that were using the old version of the plugin’s policies
+                        will <span class="strong"><strong>continue</strong></span> to use the older version. However,
+                        any new policies from the plugin added to entities will use the new version. In order to upgrade
+                        an existing entity to a newer policy, you will need to remove the old policy from that entity
+                        and re-add it. We recommend that you only do this if there is a compelling reason (e.g. a bug is
+                        fixed or a new feature added).</p></div>
+            </div>
+            <div class="section" lang="en-US">
+                <div class="titlepage">
+                    <div>
+                        <div><h3 class="title"><a id="_export_import_data"/>3.8.5. Export/Import Data</h3></div>
+                    </div>
+                </div>
+                <p>Apiman has a feature that allows an admin user to Export and/or Import data. You can access this
+                    feature by clicking the "Export/Import Data" link on the API Manager Dashboard page (admin only).
+                    This feature is useful for the following use-cases:</p>
+                <div class="itemizedlist">
+                    <ul>
+                        <li>Backing up data</li>
+                        <li>Migrating data between environments (e.g. Test→Production)</li>
+                        <li>Upgrading between apiman versions</li>
+                    </ul>
+                </div>
+                <p>From the Export/Import UI page, simply click the "Export All" button if you wish to export all of the
+                    data in the API Manager. The result will be a downloaded JSON file containing all of your apiman
+                    data. This file can then be optionally post-processed (perhaps you want to migrate only a single
+                    Organization from your Test environment to your Prod environment). At some later time, you can
+                    import this file (typically into a different installation of apiman) by selecting it and choosing
+                    "Upload File".</p></div>
+        </div>
+    </div>
+    <div class="chapter" lang="en-US">
+        <div class="titlepage">
+            <div>
+                <div><h2 class="title"><a id="_api_gateway"/>Chapter 4. API Gateway</h2></div>
+            </div>
+        </div>
+        <div class="toc">
+            <dl>
+                <dt><span class="section"><a href="#_configuration">4.1. Configuration</a></span></dt>
+                <dt><span class="section"><a href="#_invoking_managed_apis">4.2. Invoking Managed APIs</a></span></dt>
+                <dt><span class="section"><a href="#_recording_metrics">4.3. Recording Metrics</a></span></dt>
+            </dl>
+        </div>
+        <p>The runtime layer of apiman consists of a small, lightweight and embeddable API Gateway, which is responsible
+            for applying the policies configured in the API Manager to all requests to managed APIs. By default apiman
+            comes with a WAR version of the API Gateway. Additionally, there is an asynchronous version of the API
+            Gateway that runs on the vert.x platform.</p>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_configuration"/>4.1. Configuration</h2></div>
+                </div>
+            </div>
+            <p>The API Gateway is a completely separate component from the API Manager, and can therefore be used
+                completely standalone if desired. However, the API Manager provides a great deal of management
+                functionality (along with a user interface) that is quite useful. The API Gateway has a simple REST API
+                that is used to configure it. The API provides the following basic capabilities:</p>
+            <div class="itemizedlist">
+                <ul>
+                    <li>Publish an API</li>
+                    <li>Register a Client App (with API Contracts)</li>
+                    <li>Retire an API</li>
+                    <li>Unregister a Client App</li>
+                </ul>
+            </div>
+            <p>Typically the API Manager is used to manage the configuration of various APIs and client apps within the
+                scope of one or more Organizations. At various times during the management of these entities, the user
+                of the API Manager will <span class="emphasis"><em>Publish</em></span> an API or <span class="emphasis"><em>Register</em></span>
+                a Client App. When this action occurs, the API Manager invokes one of the relevant API Gateway
+                configuration endpoints listed above.</p></div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_invoking_managed_apis"/>4.2. Invoking Managed APIs</h2></div>
+                </div>
+            </div>
+            <p>Once appropriate configuration has been published/registered with the API Gateway (see the Configuration
+                section above), the API Gateway can be used to make managed calls to the APIs it knows about. A managed
+                API can be invoked as though the back-end API were being invoked directly, with the exception that the
+                endpoint is obviously different. The specific endpoint to use in order to invoke a particular API can be
+                different based on the Gateway implementation. However, typically the endpoint format is:</p>
+            <div class="itemizedlist">
+                <ul>
+                    <li><a class="ulink"
+                           href="http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/" rel="nofollow" target="_blank">http://gatewayhost:port/apiman-gateway/{organizationid}/{apiid}/{version}/</a>
+                    </li>
+                </ul>
+            </div>
+            <p>Note that all path segments beyond the {version} segment will be proxied on to the back-end API endpoint.
+                Additionally, all HTTP headers and all query parameters (except for the API Key) will also be proxied to
+                the back-end API.</p>
+            <p>Requests to managed endpoints may include the API Key so that the Gateway knows which Contract is being
+                used to invoke the API. The API Key can be sent in one of the following ways:</p>
+            <div class="itemizedlist">
+                <ul>
+                    <li>As an HTTP Header named <span class="strong"><strong>X-API-Key</strong></span></li>
+                    <li>As a URL query parameter named <span class="strong"><strong>apikey</strong></span></li>
+                </ul>
+            </div>
+            <p>If the API being invoked is a "Public" API, then no API Key should be sent. However, the request should
+                still be sent to the same endpoint as described above. The endpoint itself contains enough information
+                to let the Gateway know what API is being invoked.</p>
+            <p>If an API is not "Public" and you ommit the API Key, then the request will fail.</p></div>
+        <div class="section" lang="en-US">
+            <div class="titlepage">
+                <div>
+                    <div><h2 class="title"><a id="_recording_metrics"/>4.3. Recording Metrics</h2></div>
+                </div>
+            </div>
+            <p>The API Gateway is typically configured to record each request made to it into a metrics storage system
+                of some kind. By default apiman will use an included elasticsearch instance to store this information.
+                Various pieces of information about each request is included in the record, including but not
+                necessarily limited to the following:</p>
+            <div class="itemizedlist">
+                <ul>
+                    <li>Request start and end times</li>
+                    <li>API start and end times (i.e. just the part of the request taken up by the back end API)</li>
+                    <li>Resource path</li>
+                    <li>Response type (success, failure, error)</li>
+                    <li>API info (org id, id, version)</li>
+                    <li>Client App info (org id, id, version)</li>
+                </ul>
+            </div>
+            <p>This information is then available for analysis and reporting. The data can be accessed in a number of
+                ways, including:</p>
+            <div class="itemizedlist">
+                <ul>
+                    <li>Through the API Manager UI</li>
+                    <li>Through the API Manager REST API</li>
+                    <li>Directly from the metrics system</li>
+                </ul>
+            </div>
+        </div>
+    </div>
+</div>
+</body>
+</html>