Defining multiple content stores for Activities
The Activities content store stores the content, like files, that users add to their activities. The location of the content store can be defined during or after installation. You can configure Activities to use a content store that is different from the one defined during installation. Define more content stores if the current disk space on your system reaches capacity, or if you expand your infrastructure to add a drive. Adding a content store enables you to take advantage of the enhanced content store implementation that was introduced in version 4.
Before you begin
Use the wsadmin client to edit configuration files. For details, see Starting the wsadmin client.
The <store> element that contains the default attribute set to true is the active content store for Activities. The active content store is where activity content that users upload is saved to. All older content stores are read-only. Updates to files in the read-only stores are written to the active store.
About this task
- Resources from one activity are distributed and stored across multiple directories. In previous releases, the resources were all stored in subdirectories of a single directory. The new method helps to prevent busy implementations from reaching the maximum number of allowed subdirectories. For example, a directory on an EXT2 or EXT3 file system or Journal File System (JFS) and JFS2 on AIX® allows for a maximum of 32K subdirectories. When the maximum number of subdirectories is reached, the administrator must add a content store to the deployment.
- The new implementation uses a unique identifier to name the file, instead of using the file name that is given by the person who uploads the file. File metadata such as its mime type and user-defined name, is stored separately. As a result, someone with access to the disk cannot view the file without doing so through the product user interface.
Procedure
Example
The following sample shows two content stores. The second <store> is the active store and is where new content or revisions of existing content are uploaded to. It uses the new implementation. The first content store uses the old implementation and is inactive. The two implementations can coexist, but should reside in a mapped disk location that is separate from each other.
<store
default="false"
class="com.ibm.openactivities.objectstore.filesystem.FileSystemObjectStore">
<id>filesystem</id>
<property name="use.historic">false</property>
<property name="root.directory">
\\enterprise.server\LotusConnections\Data\activities\content
</property>
</store>
<store
default="true"
class="com.ibm.openactivities.objectstore.filesystem.ContentStore">
<id>filesystem2</id>
<property name="use.historic">false</property>
<property name="root.directory">${ACTIVITIES_CONTENT_DIR}</property>
</store>
What to do next
Check in the updated configuration files. The check-in must be done during the same wsadmin session in which you checked them out for the changes to take effect. See Applying property changes for details. Restart the Activities server and review the WebSphere Application Server SystemOut.log file to ensure that the Activities application was able to initialize with the modified configuration.
.