Moving the content store 

You can configure Activities to use a different content store from the one defined at installation time. You might want to change content stores if you augment your infrastructure and there is a new drive with more disk space available, for example.


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. To change the location of the content store after installing Activities, you can do so by performing the steps in this procedure. If you want to maintain the existing content store, you can create a new content store in addition to the existing one. See Define multiple content stores for more information.

To move the content store...


Procedure

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

    1. Access the Activities configuration file:

        execfile("activitiesAdmin.py")

        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:

        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.

            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:

            ActivitiesConfigService.checkOutConfig("/opt/act/temp","foo01Cell01")

        • Microsoft Windows:

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

  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. Edit the following property of the <store> element to point to the new directory location:

      root.directory 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 Activities is installed.

      Note: Do not change the value of the <id> element. Activities relies on the <id> element to map to the content store configuration.

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

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

  6. If you used a WAS environment variable to specify the content store location, edit the value of the variable by completing the following steps:

    1. Use an administrator ID, log into the WAS Integrated Console associated with the profile to which you installed Activities.

    2. Expand Environment, and then click WebSphere Variables.

    3. Find the ACTIVITIES_CONTENT_DIR environment variable from the list, and then edit its value.

    4. Save, and then apply your changes

  7. Copy the content store data from the old content store location to the new location.

  8. Restart the Activities application.

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

  10. After the content store is successfully copied to the new location, you can remove the original content store.


Parent topic

Manage uploaded files


Related tasks


Define multiple content stores


   

 

});