Home

 

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

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

To move the content store...

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

    1. Access the Activities configuration file:

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

    3. 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 WebSphere Application Server 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")

    4. Microsoft Windows: 

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

  2. From the temporary 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 location:

      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:\Program Files\LotusConnections\Data\activities\content

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

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

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

  6. 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 Applying property changes for details.

  7. If you used a WebSphere Application Server environment variable to specify the content store location, edit the value of the variable by completing the following steps:

    1. Using an administrator ID, log into the WebSphere Application Server 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

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

  9. Restart the Activities application.

  10. After restarting the Activities server, review the WebSphere Application Server SystemOut.log file to ensure that the Activities feature was able to initialize with the modified configuration.

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


Manage uploaded files

 

Related tasks

Define multiple content stores

+

Search Tips   |   Advanced Search