There are a lot of discussions on various forums/threads regarding the Content Server High Availability Environment. But I have not come across any documentation providing the precise steps to implement it. This is an attempt to list the steps that I have been using for the implementation. It’s basically an integration of bits and pieces from various sources combined along with my experience in order to put a clear picture. These steps may not be exactly as suggested and supported by EMC.
The procedure listed below is specific to the Content Server Linux Oracle 6.5 SP2 version.
- As it’s a HA environment, the content files should be present in a File Store that is shared across the Content Servers.
- The Installation Owner and the Installation Path should be same on each Content Server.
- Availability of a Database Server and its connectivity through each Content Server Host using Oracle Client.
- Update the /etc/hosts file of the Content Server Hosts so that they can resolve their IP addresses and hostnames.
Once the above prerequisites are satisfied, the below steps can be used to establish the HA environment.
- Install the Primary Content Server as per the standard procedure mentioned in Installation Guide.
- Install the docbroker on the Secondary CS host.
- Create a Secondary Server Config object using Documentum Administrator.
- Copy server.ini, aek.key, dbpasswd.txt, dm_start_docbase and dm_shutdown_docbase from Primary CS Host to Secondary CS Host.
- Update the server.ini on both the Hosts so that the docbrokers project to each other.
server.ini on the Primary CS:
[DOCBROKER_PROJECTION_TARGET] host = <primary docbroker> port = 1489 [DOCBROKER_PROJECTION_TARGET_1] host = <secondary docbroker> port = 1489
server.ini on the Secondary CS:
[DOCBROKER_PROJECTION_TARGET] host = <secondary docbroker> port = 1489 [DOCBROKER_PROJECTION_TARGET_1] host = <primary docbroker> port = 1489
- Update the dm_shutdown_docbase as follows:
- The line preceding to “shutdown,c,T,T” should be updated as follows:
./iapi <docbase> -U$DM_DMADMIN_USER -P -e << EOF
./iapi <docbase>.<secondary server config object name> -U$DM_DMADMIN_USER -P -e << EOF
- Update the dfc.properties of the Web Application as well as both the Content Server Hosts so that they point to both the docbrokers.
- Create an ACS Config object using the below command:
dmbasic -f dm_acs_install.ebs -e Install -- <docbase name> <installation owner> <password> <new acs config name> <secondary server config name> <JMS Port> <JMS protocol> <output log location>
Start the Primary CS and now both the CS should be in HA.