Define multiple content stores 

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 directory entries in the current file system approaches the maximum number supported. 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 only.

Before you begin

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

About this task

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. To change the location of the content store after installing Activities, you can do so. You must maintain the existing content store because it continues to hold any files uploaded and stored in the original content store. New files are added to the new content store.

To change content stores...


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

    1. Access the Activities configuration file:


        If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, pick the node where the file is stored.

    2. Check out the Activities configuration files using the following command:



        • <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.

            Note: AIX and Linux™ only: The directory must grant write permissions or the command will not run successfully.

        • <cell_name> is the name of the WAS cell hosting the IBM Connections application. This argument is case-sensitive, so type it with care. If you do not know the cell name, you can determine it by typing the following command in the wsadmin command processor:

            print AdminControl.getCell()

        For example:

        • AIX/Linux:


        • Microsoft Windows:


  2. From the temporary directory to which you just checked out the oa-config.xml file, open the file in a text editor.

  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.
        Note: 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. property

        Edit the value of the property to reflect the file path of the new file system location by typing 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:

          <property name="">
          <property name="use.historic">false</property>
          <property name="">
          <property name="use.historic">false</property>

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

  7. After making changes, check the configuration files back in and do so during the same wsadmin session in which you checked them out for the changes to take effect. See Apply property changes for details.

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

Parent topic

Manage uploaded files

Related tasks

Moving the content store
Starting the wsadmin client
Apply property changes in Activities