Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The "Clustering" page has been changed by ThomasMueller.
http://wiki.apache.org/jackrabbit/Clustering?action=diff&rev1=28&rev2=29

--------------------------------------------------

  
  The cluster nodes store information identifying items they modified in a journal. This journal must again be globally available to all nodes in the cluster. This can be either a folder in the file system or a database running standalone.
  
- ==== File Journal ====
+ === File Journal ===
  
  The file journal is configured through the following properties:
  
   * '''revision''': location of the cluster node's revision file
   * '''directory''': location of the journal folder
  
- ==== Database Journal ====
+ === Database Journal ===
  
  There are three Journal classes:
  
@@ -93, +93 @@

   * '''user''': user name
   * '''password''': password
  
- == Sample Cluster Configuration ==
+ == Sample Cluster Configurations ==
  
- This section contains some sample cluster configurations. First, using a file based journal implementation, where the journal files are created in a share exported by NFS:
+ === Database (Complete Example) ===
+ 
+ A sample repository.xml file that is using a clustered H2 database for all data (file system, data store, persistence managers, versioning, journal):
+ 
+ [[http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-core/src/test/resources/org/apache/jackrabbit/core/cluster/repository-h2.xml?view=co&content-type=text/plain|jackrabbit-core/src/test/resources/org/apache/jackrabbit/core/cluster/repository-h2.xml]]
+ 
+ For details about H2 clustering see the [[http://h2database.com/html/advanced.html#clustering|H2 documentation]].
+ 
+ === File Journal ===
+ 
+ This section contains some sample cluster configurations. First, using a file based journal implementation, where the journal files are created in a share exported by NFS. Please note that for high availability, the NFS itself must be highly available (using a clustered file system).
  
  {{{
  <Cluster id="node1">
@@ -105, +115 @@

    </Journal>
  </Cluster>
  }}}
+ 
+ === Oracle Journal ===
  
  In the next configuration, the journal is stored in an Oracle database, using a sync delay of 2 seconds (2000 milliseconds):
  
@@ -119, +131 @@

    </Journal>
  </Cluster>
  }}}
+ 
+ === PostgreSQL Journal ===
  
  In the following configuration, the journal is stored in an PostgreSQL database, accessed via "JNDI" (See Also [[UsingJNDIDataSource]]):