anchor.diff:  3. Configure the API Gateway metrics provider to be JDBC
   4. Configure the API Manager metrics accessor to be JDBC
   
  -===== Deploy an appropriate JDBC datasource
  +==== Deploy an appropriate JDBC datasource
   The first thing to do is deploy a datasource into WildFly that will be used
   by the JDBC metrics implementations.  There are a number of ways to do this, and
   documenting how to create a datasource in WildFly is outside the scope of this
  
positive.code: 
  TIP: Don't forget to also deploy the appropriate JDBC driver JAR for your database.
  
  ===== Enable the API Gateway JDBC initializer
  Of course, there is a database schema that must be installed in your database, 
  which creates the tables and indexes needed.  This schema can be automatically 
  created by apiman the first time it is used.  To enable this feature, you must
  
negative.code: * mssql11
  * oracle12
  
  ==== Configure the API Gateway metrics provider to be JDBC
  Next, you just need to tell apiman that you want to use JDBC instead of Elasticsearch
  for the storage of metrics data.  This can be done again by setting a specific
  property in *apiman.properties*:
  