The shared directory in IBM Connections is used to store:

• common files for applications (/provision)
• message bus used for inter-service communication (/messageStores)
• customizations (/customization)
• uploaded data for Activities (/activities/content)
• uploaded data Blogs (/blogs/upload)
• uploaded data for Files (/files/upload)
• uploaded data for Forums (/forums/content)
• uploaded data for Wikis (/wikis/upload)
• uploaded data for CCM/FileNet (/ccm)

It must be shared and accessible for all nodes running IBM Connections.

In case you have to change the location of the shared directory, there are many places in the configuration where the directory path is specified.

Possible reason for changing the location of the shared directory could be:

• Transfer from a Windows network share to a dedicated Network Attached Storage
• Name change of the used network attached storage

These are the steps which are required to change IBM Connections infrastructure to use the new location of the shared directory.

1. Identify how much disk space is used by shared directory today
2. Ensure that the new data storage for the shared directory has sufficient disk space (including proper space for future growth)
3. Create an user account which can be used as service account
4. Ensure that the newly created user account is able to access the new data storage (read+write permissions)

Step 1: Stop IBM Connections

Step 2: Copy complete shared directory to a new disk space

Step 3: Change WebSphere variables

Step 4: Update configuration properties files for IBM Connections

Step 4: Update configuration of IBM Connections Content Manager

Step 5: Modify Connections services to run under the new service account

Step 6: Update HTTP server configuration

Step 7: Modify HTTP services to run under the new service account

Step 8: Start IBM Connections

Step 9: Restart HTTP servers

The current location of the shared directory can be identified by checking the WebSphere variable CONNECTIONS_CUSTOMIZATION_PATH

1. In WebSphere ISC, go to   Environment > WebSphere variables
2. Search for variable CONNECTIONS_CUSTOMIZATION_PATH

If the value of CONNECTIONS_CUSTOMIZATION_PATH is

C:\IBM\Connections\data\shared\customization

... then the shared directory is located at

C:\IBM\Connections\data\shared\

After you have stopped IBM Connections, copy all directories from shared directory to the new location.

 We will need to update the following WebSphere variables:

1. In WebSphere ISC, go to   Environment > WebSphere variables
2. Click symbol "Show filter function"
3. For "Filter", select "Value"
4. In "Search terms", enter the old server name or directory path. You can use wildcard, e.g.  *oldserver*
5. Update listed variables

For your reference: In IBM Connections 4.5, these WebSphere variables need to be updated:

	ACTIVITIES_CONTENT_DIR

	ACTIVITIES_STATS_DIR

	ACTIVITY_STREAM_SEARCH_REPLICATION_DIR

	AUDIT_FILE_ROOT_DIR

	BLOGS_CONTENT_DIR

	CATALOG_REPLICATION_DIR

	COMMUNITIES_STATS_DIR

	CONNECTIONS_CUSTOMIZATION_PATH

	CONNECTIONS_OPENSOCIAL_FEATURES

	CONNECTIONS_PROVISION_PATH

	DOGEAR_FAVICON_DIR

	EVENT_ROOT_DIR

	EXTRACTED_FILE_STORE

	FILES_CONTENT_DIR

	FORUM_CONTENT_DIR

	MAILIN_ATTACHMENT_DIR

	MESSAGE_STORE_PATH

	MOBILE_CONTENT_DIR

	OAUTH_CUSTOMIZATIONS_PATH

	PROFILES_STATS_DIR

	SEARCH_DICTIONARY_DIR

	SEARCH_INDEX_SHARED_COPY_LOCATION

	WIKIS_CONTENT_DIR

The following configuration properties files must be updated:

• LC_install_dir/config.properties
• LC_install_dir/ConfigEngine/properties/wkplc.properties
• APP_server_dir/profiles/Dmgr01/ConfigEngine/properties/wkplc.properties
• APP_server_dir/profiles/Dmgr01/ConfigEngine/properties/wkplc_comp.properties

where

• LC_install_dir is the directory of IBM Connections installation, e.g. C:\IBM\Connections
• APP_server_dir is the directory of IBM WebSphere Application Server installation, e.g. C:\IBM\WebSphere\AppServer

Search in each properties file for the old server name or directory path.

Replace the old server name and/or directory path by the new server and/or directory path.

Important notice:

If any of your directories in the path contain special characters like "$", you need to replace ${file.separator} by two back slashes "\\" (Windows).

Use the following notation by example:

Before

wikis.UploadDirectory=${file.separator}${file.separator}nasstorage.company.com${file.separator}ConnectionsShared\\wikis\\upload

After

wikis.UploadDirectory=\\\\nasstorage.company.com\\connshare$\\wikis\\upload

See also thes technotes:

• Update Installer for IBM Connections fails when installing CR fix when the shared directory path contains a "$" dollar sign
• Failed to perform extraction error when applying a CR or iFixes to IBM Connections 4.0 and 4.5

Update the configuration properties file of IBM Connections Content Manager, located at LC_install_dir\ccm\ccm\ccm\ccm.properties

In the configuration properties file ccm.properties, search for the property ccm.contentStore.shared.path

Before

ccm.contentStore.shared.path=C:${file.separator}IBM${file.separator}Connections${file.separator}data${file.separator}shared${file.separator}ccm

After

ccm.contentStore.shared.path=\\\\nasstorage.company.com\\connshare$\\ccm

In addition to ccm.properties, FileNet configuration needs to be updated.

1. Access FileNet admin client via http://filenet.company.com/acce and login as administrator
2. Go to    IC Domain > Object Stores > ICObjectStore > Administrative > Storage Areas > ICObjectStore
3. Change the value in "Root Directory path"

It is strongly recommended to configure HTTP server to be used for file download, see http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Configuring_file_downloads_through_IBM_HTTP_Server_ic45

In this case, HTTP server is accessing shared directory to retrieve files. Therefore, HTTP server configuration contains links to the shared directory which need to be updated.

IBM Connections and IBM HTTP Server need to run as service using an user account which is allowed to access the filesystem where the shared directory is located.

For Microsoft Windows, steps are outlined in product documentation: http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Accessing_Windows_network_shares_ic45

1. Access Connections
2. Notify an user of a file - the user should be notified by mail as well as in Homepage > Notifications
3. Download a file from personal files
4. Download a file from community
5. Download a file from a library inside community
6. Download a file attached to a wiki page
7. Download a file attached to an activities entry
8. Access a blog entry containing uploaded data (e.g. pictures)
9. Download a file attached to an forum entry