Home

 

Define multiple content stores

Overview

You can configure Activities to use a different content store in addition to the one defined at installation time. You might want to add another content store if the current disk space reaches capacity or you augment your infrastructure and there is a new drive with more disk space available, for example. Another situation in which you would want to add another content store is if the number of entries in the current file system approaches the maximum number supported. For example, a directory on JFS and JFS2 on AIX allows for a maximum of 32K subdirectories only.

To edit configuration files, use wsadmin. See Start the wsadmin client for details.

The Activities content store is used to store files and other content that users add to their activities. During the installation, you can modify the location on disk on which the content store is created. You must maintain the existing content store to hold any files uploaded and stored in the original content store. New files are added to the new content store.

Change content stores

1. Use wsadmin to access and check out the Activities configuration files.

   1. Access the Activities configuration file:

      • Stand-alone deployment:
        execfile("activitiesAdmin.py")

      • Network deployment:
        execfile("profile_root/config/bin_lc_admin/activitiesAdmin.py")

      If prompted to specify which server to connect to, type 1.

      The information about which server to connect to is only used by wsadmin when you are running administrative commands to collect statistics.

   2. Check out the Activities configuration files...
      ActivitiesConfigService.checkOutConfig("<working_directory>", "cell_name")

      where:

      • <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft Windows operating system.

      • cell_name is the name of the WAS cell hosting the Lotus Connections feature. This argument is required even in stand-alone deployments. This argument is also case-sensitive, so type it with care. If you do not know the cell name, do one of the following to determine it:

        • Stand-alone deployment: From the file system...
          WAS_HOME\profiles\profile_name\config\cells\

        • Network deployment: From wsadmin...
          print AdminControl.getCell()

      For example:

      • AIX/Linux:
        ActivitiesConfigService.checkOutConfig("/opt/act/temp","foo01Cell01")

      • Microsoft Windows:
        ActivitiesConfigService.checkOutConfig("c:/act/temp","foo01Cell01")

2. Edit oa-config.xml

3. Find the existing <store> element, which defines the current content store location.

   Copy the <store> element, and then paste it below the existing <store> element.

4. Edit the default attribute of the existing <store> element; change its value to

   false

   Only one <store> element can have the default attribute set to true. If you change to a new content store, retain the original store, or any data that was saved there will be inaccessible and will adversely affect the existing activities. When you add a new content store, and set the default attribute to true, you are indicating that new content will be saved to the new content store; existing content remains in the existing content store.

5. Modify the new <store> element to point to the new file system location.

   <id> element

   Specify a unique name for the file system. This name must contain no more than 32 characters.

   Activities relies on the <id> element to map to the content store configuration. Do not change the value of the <id> element after the system is in use.

   root.directory property

   Edit the value of the property to reflect the file path of the new file system location.

   • For stand-alone deployments:

     • AIX or Linux:
       /opt/IBM/LotusConnections/Data/activities/content

     • Microsoft Windows:
       C:\LotusConnections\Data\activities\content

   • For network deployments:

     Type the file path to a network share directory using the Universal Naming Convention (UNC) format. For example: \\server_name\share_name. Specify the same directory on each node to which you install Activities.

   For example:

   <store default="false" 
          class="com.ibm.openactivities.objectstore.filesystem.FileSystemObjectStore">
   
       <id>filesystem</id>
   
       <property name="root.directory">
           C:\LotusConnections\Data\activities\content
       </property>
   
       <property name="use.historic">false</property>
   
   </store>
   
   <store default="true" 
          class="com.ibm.openactivities.objectstore.filesystem.FileSystemObjectStore">
   
       <id>new_file_system</id>
   
       <property name="root.directory">
           D:\new_content_store
       </property>
   
       <property name="use.historic">false</property>
   
   </store>
   

6. Save and close the oa-config.xml file.

7. After making changes, check the configuration files back in.

8. After restarting the Activities server, review the WAS SystemOut.log file to ensure that the Activities feature was able to initialize with the modified configuration.

 

Related tasks

Manage uploaded files
Move the content store
Start wsadmin
Apply property changes

+

Search Tips   |   Advanced Search