anchor.diff:  .Using an alternative configuration file
   If you want to configure the OGM using a _different_ properties file, you must either set a System property or Environment variable called 'ogm.properties' pointing to the alternative configuration file you want to use.
   
  -=== Java Configuration
  +==== Java Configuration
   
   In some cases you won't want to, or will not be able to provide configuration information via a properties file. In this case you can configure the OGM programmatically instead.
   
  
positive.code:              .setURI("bolt://user:password@localhost");
  ----
  
  _Note: Please see the Credentials section below describing the different ways you can pass credentials to the Bolt Driver_
  
  
  ==== Configuring the Cypher compiler
  
  You can _optionally_ specify which cypher compiler the OGM should use when generating cypher queries.
  If you don't specify a compiler option, the OGM will *always* use an appropriate one. So unless you have a specific reason for using a different Cypher compiler, you don't need to configure this yourself.
  
  _Note: As of OGM 2.0 only one official compiler implementation is available, so you can't do much with this setting anyway. But future releases are expected to provide different compilers explicitly tuned for the version of Neo4j you are using_
  
  .Properties file
  ```
  compiler=org.neo4j.ogm.compiler.MultiStatementCypherCompiler
  ```
  
  .Java Configuration
  [source,java]
  ----
  Components.configuration()
               .getCompilerConfiguration()
               .setCompilerClassName("org.neo4j.ogm.compiler.MultiStatementCypherCompiler");
  ----
  
  ==== Credentials
  If you are using the Bolt or Http Driver you have a number of different ways to supply credentials to the Driver Configuration.
  
  .Properties file options:
  
negative.code: 
  _Note: Please see the section below describing the different ways you can pass credentials to the Http Driver_
  
  ==== Configuring the Embedded Driver
  
  The Embedded Driver connects directly to the Neo4j database engine. There is no server involved, therefore no network overhead between your application code and the database.
  You should use the Embedded driver if you don't want to use a client-server model, or if your application is running as a Neo4j Unmanaged Extension.
  You can specify a permanent data store location to provide durability of your data after your application shuts down, or you can use an impermanent data store, which will only exist while your application is running.
  
  