anchor.diff:  		<properties>
   			<property name="hibernate.ogm.datastore.provider"
   				value="infinispan_remote" />
  +
   			<property name="hibernate.ogm.infinispan_remote.configuration_resource_name"
   				value="hotrodclient.properties" />
  +
   			<property name="hibernate.ogm.datastore.create_database"
   				value="true" /> # <1>
  +
   			<property name="hibernate.ogm.infinispan_remote.cache_configuration"
  -				value="default" /> # <2>
  +				value="sheep" /> # <2>
  +
   		</properties>
   	</persistence-unit>
   </persistence>
   ----
  -<1> Property ``hibernate.ogm.datastore.create_database`` enables cache creation
  -<2> Property ``hibernate.ogm.infinispan_remote.cache_configuration`` defines a configuration,
  -named __default__, to apply to all created caches
  -====
  -
  -Assuming that:
  -
  -* Caches __default__ and __transactional__ are **present** on Infinispan server configuration.
  -* Caches __NoAnnotationEntity__ and __CacheConfigurationEntity__ are instead **NOT present** on Infinispan server configuration.
  -
  -Then:
  -
  -* Cache __NoAnnotationEntity__ will be created by the dialect using __default__ as a cache configuration.
  -* Cache __CacheConfigurationEntity__ will be created by the dialect using __transactional__ as a cache configuration.
  +<1> Enable cache creation
  +<2> Select __sheep__ as default cache configuration
  +====
  +
  +In this scenario, Hibernate OGM will create the  __Sheep__ cache using the configuration
  +__sheep__ and the __BlackSheep__  cache using the __black_sheep__ cache configuration.
   
   [IMPORTANT]
   ====
  -__OGM default configuration__ is transactional.
  -
  -We always recommend using transactional caches, at least unless you are confident that data consistency is not important for your use case.
  -====
  -
  -==== Remote Query Capability
  -
  -Hibernate OGM backend is able to run the queries it needs to materialize relations.
  -Since version __5.4.0.Alpha2__, the dialect is capable to translate JPQL to the **corresponding** Infinispan remote queries
  -or to execute native queries.
  -But there are still some limitations:
  -
  -* We don't support queries on polymorphic entities using TABLE_PER_CLASS inheritance strategy
  -* Selecting from associations is not yet implemented (example: select h.author.name from Hypothesis h where author is a one-to-one association)
  -* Query on Byte filed is currently unsupported
  +__Hibernate OGM default configuration__ is transactional.
  +
  +We generally recommend using transactional caches unless you are confident that data consistency
  +is not important for your use case.
  +====
  +
  +==== Remote Query Capabilities
  +
  +Hibernate OGM backend can translate JPQL queries to the **corresponding** Infinispan remote
  +native queries, or it can execute native queries directly.
  +There are some limitations, though:
  +
  +* queries on polymorphic entities using TABLE_PER_CLASS inheritance strategy are not supported
  +* projection from associations is not yet implemented (example: select h.author.name from Hypothesis h where author is a one-to-one association)
   
   [[infinispan-remote-transaction]]
   
  
positive.code: To run a __remote script__, the script entry must first be in the Infinispan remote cache.
  The name of the procedure is the key of the corresponding entry script.
  The parameter names are instead defined in the first line of the script itself.
  For more information see http://infinispan.org/docs/dev/user_guide/user_guide.html#scripting[Infinispan Guide -Remote Script]
  
  Whereas to run a __server task__ you need first to deploy the java task as jar on Infinispan server.
  In this case the name of the procedure is defined by `getName` method of the task service class.
  
negative.code: `hibernate.ogm.datastore.provider` property to `infinispan_remote`.
  
  The next step is to configure the Hot Rod client.
  You have two alternatives:
  
  * provide a resource file containing all Hot Rod client configuration properties
  * include all the Hot Rod client configuration properties with a custom prefix, as explained below.
  
  To use an external configuration resource, set the `hibernate.ogm.infinispan_remote.configuration_resource_name`
  configuration property to the resource name.
  