Author: thomas.heute(a)jboss.com
Date: 2010-11-11 09:52:44 -0500 (Thu, 11 Nov 2010)
New Revision: 5042
Modified:
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/extras/Advanced_Development_JCR_Configuration/orig.xml
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR.xml
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/configuration.xml
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/intro.xml
Log:
JBEPP-623: Remove eXo JCR documentation that applies to eXo JCR standalone
Modified:
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/extras/Advanced_Development_JCR_Configuration/orig.xml
===================================================================
---
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/extras/Advanced_Development_JCR_Configuration/orig.xml 2010-11-11
12:16:48 UTC (rev 5041)
+++
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/extras/Advanced_Development_JCR_Configuration/orig.xml 2010-11-11
14:52:44 UTC (rev 5042)
@@ -1,96 +1,65 @@
-<repository-service default-repository="repository">
- <repositories>
- <repository name="db1" system-workspace="ws"
default-workspace="ws">
- <security-domain>exo-domain</security-domain>
- <access-control>optional</access-control>
- <session-max-age>1h</session-max-age>
-
<authentication-policy>org.exoplatform.services.jcr.impl.core.access.JAASAuthenticator</authentication-policy>
- <workspaces>
- <workspace name="production">
- <!-- for system storage -->
- <container
class="org.exoplatform.services.jcr.impl.storage.jdbc.optimisation.CQJDBCWorkspaceDataContainer">
- <properties>
- <property name="source-name" value="jdbcjcr" />
- <property name="multi-db" value="false" />
- <property name="update-storage" value="false" />
- <property name="max-buffer-size" value="200k" />
- <property name="swap-directory"
value="../temp/swap/production" />
- </properties>
- <value-storages>
- <value-storage id="system"
class="org.exoplatform.services.jcr.impl.storage.value.fs.TreeFileValueStorage">
- <properties>
- <property name="path" value="../temp/values/production"
/>
- </properties>
- <filters>
- <filter property-type="Binary" />
- </filters>
- </value-storage>
- </value-storages>
- </container>
- <initializer
class="org.exoplatform.services.jcr.impl.core.ScratchWorkspaceInitializer">
- <properties>
- <property name="root-nodetype" value="nt:unstructured"
/>
- </properties>
- </initializer>
- <cache enabled="true"
class="org.exoplatform.services.jcr.impl.dataflow.persistent.LinkedWorkspaceStorageCacheImpl">
- <properties>
- <property name="max-size" value="10k" />
- <property name="live-time" value="1h" />
- </properties>
- </cache>
- <query-handler
class="org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex">
- <properties>
- <property name="index-dir"
value="../temp/jcrlucenedb/production" />
- </properties>
- </query-handler>
- <lock-manager>
- <time-out>15m</time-out>
- <persister
class="org.exoplatform.services.jcr.impl.core.lock.FileSystemLockPersister">
- <properties>
- <property name="path" value="../temp/lock/system" />
- </properties>
- </persister>
- </lock-manager>
- </workspace>
-
- <workspace name="backup">
- <container
class="org.exoplatform.services.jcr.impl.storage.jdbc.optimisation.CQJDBCWorkspaceDataContainer">
- <properties>
- <property name="source-name" value="jdbcjcr" />
- <property name="multi-db" value="false" />
- <property name="update-storage" value="false" />
- <property name="max-buffer-size" value="200k" />
- <property name="swap-directory"
value="../temp/swap/backup" />
- </properties>
- <value-storages>
- <value-storage id="draft"
class="org.exoplatform.services.jcr.impl.storage.value.fs.TreeFileValueStorage">
- <properties>
- <property name="path" value="../temp/values/backup"
/>
- </properties>
- <filters>
- <filter property-type="Binary" />
- </filters>
- </value-storage>
- </value-storages>
- </container>
- <initializer
class="org.exoplatform.services.jcr.impl.core.ScratchWorkspaceInitializer">
- <properties>
- <property name="root-nodetype" value="nt:unstructured"
/>
- </properties>
- </initializer>
- <cache enabled="true"
class="org.exoplatform.services.jcr.impl.dataflow.persistent.LinkedWorkspaceStorageCacheImpl">
- <properties>
- <property name="max-size" value="10k" />
- <property name="live-time" value="1h" />
- </properties>
- </cache>
- <query-handler
class="org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex">
- <properties>
- <property name="index-dir"
value="../temp/jcrlucenedb/backup" />
- </properties>
- </query-handler>
- </workspace>
- </workspaces>
- </repository>
- </repositories>
-</repository-service>
+ <!-- Portal system data -->
+ <workspace name="portal-system">
+ <container
class="org.exoplatform.services.jcr.impl.storage.jdbc.optimisation.CQJDBCWorkspaceDataContainer">
+ <properties>
+ <property name="source-name"
value="${gatein.jcr.datasource.name}${container.name.suffix}"/>
+ <property name="dialect"
value="${gatein.jcr.datasource.dialect}"/>
+ <property name="multi-db" value="false"/>
+ <property name="update-storage" value="true"/>
+ <property name="max-buffer-size"
value="204800"/>
+ <property name="swap-directory"
value="${gatein.jcr.data.dir}/swap/portal-system${container.name.suffix}"/>
+ </properties>
+ <value-storages>
+ <value-storage id="portal-system"
class="org.exoplatform.services.jcr.impl.storage.value.fs.TreeFileValueStorage">
+ <properties>
+ <property name="path"
value="${gatein.jcr.storage.data.dir}/portal-system${container.name.suffix}"/>
+ </properties>
+ <filters>
+ <filter property-type="Binary"/>
+ </filters>
+ </value-storage>
+ </value-storages>
+ </container>
+ <initializer
class="org.exoplatform.services.jcr.impl.core.ScratchWorkspaceInitializer">
+ <properties>
+ <property name="root-nodetype"
value="nt:unstructured"/>
+ <property name="root-permissions"
value="*:/platform/administrators read;*:/platform/administrators
add_node;*:/platform/administrators set_property;*:/platform/administrators
remove"/>
+ </properties>
+ </initializer>
+ <cache enabled="true"
class="org.exoplatform.services.jcr.impl.dataflow.persistent.jbosscache.JBossCacheWorkspaceStorageCache">
+ <properties>
+ <property name="jbosscache-configuration"
value="${gatein.jcr.cache.config}" />
+ <property name="jgroups-configuration"
value="${gatein.jcr.jgroups.config}" />
+ <property name="jgroups-multiplexer-stack"
value="true" />
+ <property name="jbosscache-cluster-name"
value="jcr-${container.name.suffix}-portal-system" />
+ </properties>
+ </cache>
+ <query-handler
class="org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex">
+ <properties>
+ <property name="index-dir"
value="${gatein.jcr.index.data.dir}/portal-system${container.name.suffix}"/>
+ <property name="changesfilter-class"
value="${gatein.jcr.index.changefilterclass}" />
+ <property name="jbosscache-configuration"
value="${gatein.jcr.index.cache.config}" />
+ <property name="jgroups-configuration"
value="${gatein.jcr.jgroups.config}" />
+ <property name="jgroups-multiplexer-stack"
value="true" />
+ <property name="jbosscache-cluster-name"
value="jcrindexer-${container.name.suffix}-portal-system" />
+ <property name="max-volatile-time" value="60" />
+ </properties>
+ </query-handler>
+ <lock-manager
class="org.exoplatform.services.jcr.impl.core.lock.jbosscache.CacheableLockManagerImpl">
+ <properties>
+ <property name="time-out" value="15m" />
+ <property name="jbosscache-configuration"
value="${gatein.jcr.lock.cache.config}" />
+ <property name="jgroups-configuration"
value="${gatein.jcr.jgroups.config}" />
+ <property name="jgroups-multiplexer-stack"
value="true" />
+ <property name="jbosscache-cluster-name"
value="jcrlock-${container.name.suffix}-portal-system" />
+ <property name="jbosscache-cl-cache.jdbc.table.name"
value="jcrlock_portal_system" />
+ <property name="jbosscache-cl-cache.jdbc.table.create"
value="true" />
+ <property name="jbosscache-cl-cache.jdbc.table.drop"
value="false" />
+ <property name="jbosscache-cl-cache.jdbc.table.primarykey"
value="pk" />
+ <property name="jbosscache-cl-cache.jdbc.fqn.column"
value="fqn" />
+ <property name="jbosscache-cl-cache.jdbc.node.column"
value="node" />
+ <property name="jbosscache-cl-cache.jdbc.parent.column"
value="parent" />
+ <property name="jbosscache-cl-cache.jdbc.datasource"
value="${gatein.jcr.datasource.name}${container.name.suffix}" />
+ </properties>
+ </lock-manager>
+ </workspace>
Modified:
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/configuration.xml
===================================================================
---
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/configuration.xml 2010-11-11
12:16:48 UTC (rev 5041)
+++
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/configuration.xml 2010-11-11
14:52:44 UTC (rev 5042)
@@ -14,21 +14,64 @@
<programlisting language="Java" role="Java"><xi:include
parse="text"
href="../../../extras/Advanced_Development_JCR_Configuration/NMTOKEN.java"
xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
- To configure the JCR Service;
+ To modify the configuration of the JCR Service, you would need to modify the file
found at
<filename>/<replaceable>JBOSS_AS</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/jcr/repository-configuration.xml</filename>.
+ <programlisting><![CDATA[
+<repository-service default-repository="repository">
+ <repositories>
+ <repository name="repository" system-workspace="system"
default-workspace="portal-system">
+ <security-domain>gatein-domain</security-domain>
+ <access-control>optional</access-control>
+
<authentication-policy>org.exoplatform.services.jcr.impl.core.access.JAASAuthenticator</authentication-policy>
+
+ <!-- System -->
+ <workspaces>
+ [... Workspaces definitions ...]
+ </workspaces>
+ </repository>
+ </repositories>
+</repository-service>]]>
+
+ </programlisting>
</para>
<procedure>
<step>
<para>
- Familiarize yourself with the DTD file above and the either the example
configuration file below or the one in your &PRODUCT; deployment (found at;
<filename>/<replaceable>JBOSS_AS</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/jcr/repository-configuration.xml</filename>).
+ In JBoss Enteprise Portal Platform you will see several configured workspaces
required for the portal.
+ <itemizedlist>
+ <listitem>
+ <para>
+ <literal>system</literal>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+
<literal>portal-system</literal>: To store portal metadata such as page
compositions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+
<literal>portal-work</literal>: To store elements that are temporary such as
tokens
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+
<literal>wsrp-system</literal>: To store WSRP related data
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+
<literal>wsrp-system</literal>: To store Portlet Container related data (such
as portlet preferences
+ </para>
+ </listitem>
+
+ </itemizedlist>
</para>
</step>
+ <step>
+ <para>Locate the workspace to modify.
+ <step>
<step>
<para>
- Replace the element values marked below with those of your deployment environment.
- </para>
- </step>
- <step>
- <para>
The repository configuration supports human-readable values. They are not
case-sensitive.
</para>
<para>
@@ -122,162 +165,27 @@
</step>
</procedure>
<section
id="sect-Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration">
- <title>Repository Service Configuration</title>
+ <title>Example of the portal-system workspace</title>
<!--DOCS NOTE: The callout configuration below is not rerndering correctly in Publican
builds. The callout list icons do not rener from number 15 onwards. -->
<programlistingco>
<areaspec>
- <!--1-->
- <area coords="1 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-default-repository"/>
+ <!--1-->
+ <area coords="2 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-workspace-name"/>
<!--2-->
- <area coords="2 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-repositories"/>
+ <area coords="3 90"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-container"/>
<!--3-->
- <area coords="3 80"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-name"/>
+ <area coords="23 90"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_initializer"/>
<!--4-->
- <area coords="3 85"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-system-workspace"/>
+ <area coords="29 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_cache"/>
<!--5-->
- <area coords="3 90"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-default-workspace"/>
+ <area coords="37 100"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_query-handler"/>
<!--6-->
- <area coords="4 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-security-domain"/>
- <!--7-->
- <area coords="5 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-access-control"/>
- <!--8-->
- <area coords="6 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-session-max-age"/>
- <!--9-->
- <area coords="7 100"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-authentication-policy"/>
- <!--10-->
- <area coords="8 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-workspaces"/>
- <!--11-->
- <area coords="9 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-workspace-name"/>
- <!--12-->
- <area coords="11 90"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-container"/>
- <!--13-->
- <area coords="30 90"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_initializer"/>
- <!--14-->
- <area coords="35 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_cache"/>
- <!--15-->
- <area coords="41 100"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_query-handler"/>
- <!--16-->
- <area coords="47 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_lock-manager-timeout"/>
- <!--17-->
- <area coords="48 100"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_lock-manager-persister"/>
- <!--18-->
- <area coords="50 90"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_lock-manager-path"/>
- <!--19-->
- <area coords="57 110"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_workspace-container-class"/>
- <!--20-->
- <area coords="58 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_workspace-container-properties"/>
- <!--21-->
- <area coords="65 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_workspace-container-value-storages"/>
- <!--22-->
- <area coords="66 90"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_workspace-container-value-storage"/>
- <!--23-->
- <area coords="66 95"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_workspace-container-value-class"/>
- <!--24-->
- <area coords="67 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_workspace-container-value-properties"/>
- <!--25-->
- <area coords="70 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_workspace-container-value-filters"/>
- <!--26-->
- <area coords="76 90"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_initializer_implementation_class"/>
- <!--27-->
- <area coords="77 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_initializer_implementation_properties"/>
- <!--28-->
- <area coords="81 90"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_cache_enabled"/>
- <!--29-->
- <area coords="81 95"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_cache_class"/>
- <!--30-->
- <area coords="82 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_cache_properties"/>
- <!--31-->
- <area coords="87 100"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_query-handler-class"/>
- <!--32-->
- <area coords="88 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_query-handler-properties"/>
+ <area coords="50 60"
id="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_lock-manager-timeout"/>
</areaspec>
<programlisting language="XML" role="XML"><xi:include
parse="text"
href="../../../extras/Advanced_Development_JCR_Configuration/orig.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<calloutlist>
- <!--<title>Repository Service configuration:</title>-->
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-default-repository">
- <para>
- The name of a default repository (one returned by
RepositoryService.getRepository())
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-repositories">
- <para>
- The list of repositories is configured within the <repositories>
element.
- </para>
- </callout>
- <!--</calloutlist>
- <calloutlist>
- <title>Repository configuration:</title>-->
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-name">
- <para>
- The name of the repository being configured.
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-default-workspace">
- <para>
- The name of a workspace. This can be obtained using Session's
<literal>login()</literal> or
<literal>login(Credentials)</literal> methods for workspaces without an
explicit name.
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-system-workspace">
- <para>
- The name of workspace where /jcr:system node is placed.
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-security-domain">
- <para>
- The name of a security domain for JAAS authentication
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-access-control">
- <para>
- The name of an access control policy. There can be three types:
- </para>
- <variablelist>
- <varlistentry>
- <term>optional</term>
- <listitem>
- <para>
- AN ACL is created on demand. This is the default policy.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>disable</term>
- <listitem>
- <para>
- Disables access control.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>mandatory</term>
- <listitem>
- <para>
- An ACL is created for each added node. This function is not supported in
this release.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-session-max-age">
- <para>
- The amount of time before an idle session will be removed (called logout). If it
is not set, the idle session will never be removed.
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-authentication-policy">
- <para>
- The name of an authentication policy class.
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-workspaces">
- <para>
- The list of workspaces.
- </para>
- </callout>
- <!--</calloutlist>
- <calloutlist>
- <title>Workspace configuration:</title>-->
<callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_configuration-workspace-name">
<para>
The name of the workspace.
@@ -303,172 +211,11 @@
Query handler configuration.
</para>
</callout>
- <!--</calloutlist>
- <calloutlist>
- <title>Lock Manager configuration:</title>-->
<callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_lock-manager-timeout">
<para>
The amount of time before the unused global lock is removed.
</para>
</callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_lock-manager-persister">
- <para>
- A class for storing lock information for future use. For example; remove lock
after restarting JCR.
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_lock-manager-path">
- <para>
- Each workspace has its own lock folder.
- </para>
- </callout>
- <!--</calloutlist>
- <calloutlist>
- <title>Workspace data container configuration:</title>-->
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_workspace-container-class">
- <para>
- A workspace data container class name.
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_workspace-container-properties">
- <para>
- The list of properties (in name-value pairs) for the concrete Workspace data
container.
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_workspace-container-value-storages">
- <para>
- The list of value storage plugins.
- </para>
- </callout>
- <!--</calloutlist>
- <calloutlist>
- <title>Value storage plugin configuration (optional
feature):</title>-->
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_workspace-container-value-storage">
- <para>
- <emphasis role="bold">Optional</emphasis>: Value storage
plugin definition. If this element is not included, the values will be stored as BLOBs
inside the database.
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_workspace-container-value-class">
- <para>
- A value storage plugin class name (attribute).
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_workspace-container-value-properties">
- <para>
- The list of properties (in name-value pairs) for a concrete value storage plugin.
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_workspace-container-value-filters">
- <para>
- The list of filters defining conditions when this plugin is applicable.
- </para>
- </callout>
- <!--</calloutlist>
- <calloutlist>
- <title>Initializer configuration (optional):</title>-->
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_initializer_implementation_class">
- <para>
- Initializer implementation class.
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_initializer_implementation_properties">
- <para>
- The list of properties (in name-value pairs). Properties are supported:
- </para>
- <variablelist>
- <varlistentry>
- <term>root-nodetype</term>
- <listitem>
- <para>
- The node type for root node initialization.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>root-permissions</term>
- <listitem>
- <para>
- Default permissions of the root node. It is defined as a set of
semicolon-delimited permissions containing a group of space-delimited identities and the
type of permission.
- </para>
- <para>
- For example any read;:/admin read;:/admin add_node;:/admin
set_property;:/admin remove means that users from group admin have all permissions and
other users have only a 'read' permission.
- </para>
- <para>
- Configurable initializer adds a capability to override workspace initial
startup procedure.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </callout>
- <!--</calloutlist>
- <calloutlist>
- <title>Cache configuration:</title>-->
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_cache_enabled">
- <para>
- Defines if the workspace cache is enabled.
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_cache_class">
- <para>
- Cache implementation class. This is optional from JCR version 1.9.
- </para>
- <para>
- The default value is
<literal>org.exoplatform.services.jcr.impl.dataflow.persistent.LinkedWorkspaceStorageCacheImpl</literal>.
- </para>
- <para>
- The cache can be configured to use concrete implementations of the
<literal>WorkspaceStorageCache</literal> interface.
- </para>
- <para>
- The JCR core has two implementations to use:
- </para>
- <para>
- <emphasis
role="bold">LinkedWorkspaceStorageCacheImpl</emphasis>
- </para>
- <para>
- The default implementation, with configurable read behavior and statistics.
- </para>
- <para>
- <emphasis role="bold">WorkspaceStorageCacheImpl</emphasis>
- </para>
- <para>
- This implementation is a legacy from pre 1.9 versions of the JCR. However, it can
still be used.
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_cache_properties">
- <para>
- The list of properties (in name-value pairs) for the workspace cache:
- </para>
- <variablelist>
- <varlistentry>
- <term>max-size</term>
- <listitem>
- <para>
- The maximum size of the cache.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>live-time</term>
- <listitem>
- <para>
- Cached item live time.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </callout>
- <!--</calloutlist>
- <calloutlist>
- <title>Query Handler configuration:</title>-->
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_query-handler-class">
- <para>
- A Query Handler class name.
- </para>
- </callout>
- <callout
arearefs="Reference_Guide-Portal_and_Standalone_configuration-Repository_service_query-handler-properties">
- <para>
- The list of properties (name-value pairs) for a Query Handler
(<literal>indexDir</literal>) properties and advanced features described in
<xref linkend="sect-Reference_Guide-Search_Configuration"/>.
- </para>
- </callout>
</calloutlist>
</programlistingco>
Modified:
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/intro.xml
===================================================================
---
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/intro.xml 2010-11-11
12:16:48 UTC (rev 5041)
+++
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR/intro.xml 2010-11-11
14:52:44 UTC (rev 5042)
@@ -5,11 +5,17 @@
]>
<section id="sect-Reference_Guide-Introduction">
<title>Introduction</title>
+ <warning>
+ <title>eXo JCR usage</title>
+ <para>
+ The JBoss Enterprise Portal Platform is using a JCR API to store its
information for internal usage. We do not support usage of the JCR to store application
infornation. The information below only exists if one need to understand particular low
level details on how the JBoss Enterprise Portal Platform works and how it can be
fine-tuned.
+ </para>
+ </warning>
<para>
The term <emphasis role="bold">JCR</emphasis> refers to the Java
Content Repository. The JCR is the data store of JBoss Enterprise Portal Platform. All
content is stored and managed via the JCR.
</para>
<para>
- The eXo JCR included with JBoss Enterprise Portal Platform 5.1 is a (<ulink
type="http"
url="http://www.jcp.org/en/jsr/detail?id=170">JSR-170</ulink>)
compliant implementation of the JCR 1.0 specification. The JCR provides versioning,
textual search, access control, content event monitoring, and can be used for storing text
and binary data. The backend storage of the JCR is configurable and can be a filesystem or
a database.
+ The eXo JCR included with JBoss Enterprise Portal Platform 5.1 is a (<ulink
type="http"
url="http://www.jcp.org/en/jsr/detail?id=170">JSR-170</ulink>)
compliant implementation of the JCR 1.0 specification. The JCR provides versioning,
textual search, access control, content event monitoring, and is used to storing text and
binary data for the portal internal usage. The backend storage of the JCR is configurable
and can be a filesystem or a database.
</para>
<section id="sect-Reference_Guide-Introduction-Concepts">
<title>Concepts</title>
Modified: epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR.xml
===================================================================
---
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR.xml 2010-11-11
12:16:48 UTC (rev 5041)
+++
epp/docs/branches/EPP_5_1_Branch/Reference_Guide/en-US/modules/Advanced/JCR.xml 2010-11-11
14:52:44 UTC (rev 5042)
@@ -6,8 +6,7 @@
<chapter id="chap-Reference_Guide-eXo_JCR">
<title>eXo JCR</title>
<xi:include href="JCR/intro.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
- <!--<xi:include href="JCR/configuration.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />-->
- <!--Section removed as JCR requirements already configured in EPP-->
+ <xi:include href="JCR/configuration.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="JCR/jdbc-data-container-config.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
<!--<xi:include href="JCR/external-value-storages.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />-->
<!--Section removed as JCR requirements already configured in EPP-->