Infrastructure at your Service

Middleware Team

Documentum story – HA configuration best practice

We went to a performance issue and some failed failover regarding the content server and the JMS. Thus we asked EMC for recommendations and it seems that the configuration can be slightly different than the official documentation.

Here are the steps for the High Availability configuration for the content server and JMS. At this point you must already have a Primary Content Server (CS1) with its own JMS (JMS1) and a Remote Content Server (CS2) with its own JMS2.

Login to your CS1 and CS2 and backup your dfc.properties file:

cp $DOCUMENTUM_SHARED/config/dfc.properties $DOCUMENTUM_SHARED/config/dfc.properties.old

Then edit it and remove all unnecessary docbrokers (where [x] is not [0]):

dfc.docbroker.host[x] = whateverserver
dfc.docbroker.port[x] = 1489

Save and close the file.

Login to CS2 then run:

$DM_HOME/install/dm_launch_cfs_server_config_program.sh

When the AEK info are asked, enter your AEK info. When the Lockbox info are asked enter your Lockbox info.

In the “Select an Action” screen, select “Create Content-file server”, enter the Primary connection broker information (CS1)

In the “Configure repository” screen enter the Remote content server host name (CS2) then enter the CS2 connection broker information.

Update the server.ini and dfc.properties files in CS1 and CS2 with the following setup:

CS1
server.ini
[DOCBROKER_PROJECTION_TARGET]
host = SERVER1
port = 1489
proximity = 1

CS1
dfc.properties
dfc.docbroker.host[0] = SERVER1
dfc.docbroker.port[0] = 1489

CS2
server.ini
[DOCBROKER_PROJECTION_TARGET]
host = SERVER2
port = 1489
proximity = 1

CS2
dfc.properties
dfc.docbroker.host[0] = SERVER2
dfc.docbroker.port[0] = 1489

Restart CS2 and CS1 and login to DA1 and DA2 and verify the following:

In Administration/Basic Configuration/Content Servers you must have 2 CS, the primary and the remote. In the primary CS properties (Connection Brokers tab) you must have 1 target, the remote server with proximity 2. If it’s not the case update it. In the remote CS properties you must have 1 target, the primary server with proximity 2. Verify that it’s the same in both DA1 and DA2.

Navigate to Administration/Basic Configuration/Java Method Server, you must have 2 JMS declared. One for the local primary and one for the remote server. Both must be selected as PRIMARY in the properties for the CS1. For the CS2 do the same, for both JMS properties set it to primary. What does it means? For each CS, both JMS will be considered as local, hence they are not crossed between CS. We aren’t making crossed projections.

And you’re done, with all these configurations you should have increased performances and an HA configured. Note that the JMS configuration is a “specific case” configuration

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Middleware Team
Middleware Team