jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Update of "Clustering" by ThomasMueller
Date Sat, 28 Jun 2008 19:45:44 GMT
Dear Wiki user,

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

The following page has been changed by ThomasMueller:
http://wiki.apache.org/jackrabbit/Clustering

The comment on the change is:
improve documentation

------------------------------------------------------------------------------
  
  == Prerequisites ==
  
- In order to cluster some repository nodes, the following prerequisites must be met:
+ In order to use clustering, the following prerequisites must be met:
  
-  * The persistence managers must store their data in the same, globally accessible location
+  * Each cluster node must have its own repository configuration
   * Every cluster node must be assigned a unique ID
   * A journal type must be chosen, either based on files or stored in a database
+  * The persistence managers must store their data in the same, globally accessible location
  
  Let's look at these steps in more detail:
- 
- === Persistence manager configuration ===
- 
- For performance reasons, only information identifying the modified items is stored in the
journal. This implies, that all cluster nodes must have access to the items' actual content.
Since file system based persistence managers are not transactional, one has to use persistence
managers storing their data in a database running standalone. The following sample shows a
workspace's persistence manager configuration using an Oracle database:
- 
- {{{
- <PersistenceManager class="org.apache.jackrabbit.core.persistence.db.OraclePersistenceManager">
-   <param name="url" value="jdbc:oracle:thin:@myhost:1521:mydb" />
-   <param name="user" value="scott"/>
-   <param name="password" value="tiger"/>
-   <param name="schemaObjectPrefix" value="${wsp.name}_"/>
-   <param name="externalBLOBs" value="false"/>
- </PersistenceManager>
- }}}
- 
- Since the file system BLOB store uses a repository local directory and is not transactional,
one should set the parameter '''externalBLOBs''' to ''false'' in order to store BLOBs in the
database as well.
  
  === Unique cluster node ID ===
  
@@ -82, +67 @@

  
  '''Note''': the journal implementation classes have been refactored in Jackrabbit 1.3. In
earlier versions, journal implementations resided in the package ''org.apache.jackrabbit.core.cluster''.
  
+ === Persistence manager configuration ===
+ 
+ For performance reasons, only information identifying the modified items is stored in the
journal. This implies, that all cluster nodes must have access to the items' actual content.
Since file system based persistence managers are not transactional, one has to use persistence
managers storing their data in a database running standalone. The following sample shows a
workspace's persistence manager configuration using an Oracle database:
+ 
+ {{{
+ <PersistenceManager class="org.apache.jackrabbit.core.persistence.db.OraclePersistenceManager">
+   <param name="url" value="jdbc:oracle:thin:@myhost:1521:mydb" />
+   <param name="user" value="scott"/>
+   <param name="password" value="tiger"/>
+   <param name="schemaObjectPrefix" value="${wsp.name}_"/>
+   <param name="externalBLOBs" value="false"/>
+ </PersistenceManager>
+ }}}
+ 
+ Since the file system BLOB store uses a repository local directory and is not transactional,
one should set the parameter '''externalBLOBs''' to ''false'' in order to store BLOBs in the
database as well.
+ 

Mime
View raw message