So you want to add a Content Server to your existing Documentum repository – how hard can it be? Not too much, but the process seems to change with every service pack. The good thing is that it is easier now, if you get it right.
We will not discuss clustering, automatic failover and such here.
- Install Content Server binaries. Complete any other steps such as hotfixes for Centera, if being used.
- Under %DM_HOME%\install there is a file cfsConfigurationProgram.exe. CFS stands for Content-File Server – which is what the additional Content Servers are called. Run this program and follow prompts. Most of the things will be straightforward – just make sure when admin/superuser account information is asked installation owner information is provided (rather than the repository owner). It will create server config, copy and modify the needed files, etc. These steps used to involve manual interaction earlier.
- Check the file stores in use, particularly filestore_01. If its location points to a local drive it would mean that each Content Server will be looking at different physical locations when this file store needs to be used. This would need to change.
- You can either move the filestore to a new shared location or share the existing location on the first Content Server. This location looks like data/repo_name/content_storage_01 and the path is stored in a dm_location object named content_storage_01. The instructions for moving a file store can be found in the Content Server Admin guide under the heading of Maintenance. Mapping a drive might not work but UNC names such \\server\share\path can be used in dm_location.
- In production you might prefer to use a SAN/NAS type of storage rather than a simple folder share.
Haven’t done this on UNIX recently but sharing a storage/path is easier in UNIX since it looks like any other file path.