If you have a multiple-Content Server Documentum Infrastructure, you should install and configure manually the second Content Server instance. Assuming the first (main) CS is already installed and configured, below are the steps to install manually the second one (no wizzard). Ensure it will be on a different host machine (you can use a virtual one if you don’t want to buy a new box ;) ).
1) Connect to the repository as the installation owner by using Documentum Administrator and create a new server config object (below sample values):
Name: CS_NAME_LB1
Web server location: [server name of the CS Workstation]
Web server port: 80
Locale name: en
Default client codepage: ISO_8859-1
Server OS codepage ISO_8859-1
SMTP server [smtp_dns]
Workflow Content
Migration Threads: 10
Maximum Login Ticket 43200
Default Login Ticket 5
* Set other settings to fit the first config object.
Update the owner name for the new created object using the DQL
update dm_server_config objects set owner_name = '[docbase_owner]' where bject_name='[object_name]'
Disconnect from the repository
2) Create a server.ini file for the new Content Server
Create the folder [docbase_name] in the following path on the new Content Server:
…\Documentum\dba\config
Copy in this folder ([docbase_name]) the server.ini file from the first Content Server, for this repository.
Change the server_config name
server_config_name = CS_NAME_LB1
and the docbroker configurations
[DOCBROKER_PROJECTION_TARGET]
host = [docbroker2]
port = 1489
[DOCBROKER_PROJECTION_TARGET_1]
host = [docbroker1]
port = 1489
proximity = 100
* if additional projections required (add as many as required):
[DOCBROKER_PROJECTION_TARGET_2]
host = [docbroker3]
port = [port]
3) Create the repository Windows service by running the following command file:
@echo off
setlocal
set docbase=[docbase_name]
set instowner=[installation_owner_user]
set iodomain=[domain]
set iopass=[password]
set binPath=E:\Documentum\product\6.5\bin\documentum.exe -docbase_name %docbase% -security acl -init_file E:\Documentum\dba\config\%docbase%\server.ini -run_as_service -install_owner %instowner% -logfile E:\Documentum\dba\log\%docbase%.log
sc create DmServer%docbase% binPath= "%binPath%" start= demand DisplayName= "Documentum Docbase Service %docbase%" obj= %iodomain%\%instowner% password= %iopass%
sc description DmServer%docbase% %docbase%_clone
endlocal
5) Configure port numbers
Edit C:\WINDOWS\system32\drivers\etc\Services file and add the following entries at the end of the file:
dm_[docbase_name] [prev+1]/tcp #Documentum Docbase Service [docbase_name]
dm_[docbase_name]_s [prev+1]/tcp #Documentum Docbase Service [docbase_name] (secure service)
6) Update the windows registry
* sample values used, set the ones from your system
[HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\DOCBASES\[docbase_name]]
"DM_CONFIGURE_STATUS"=hex(2):43,00,6f,00,6d,00,70,00,6c,00,65,00,74,00,65,00,\ 00,00
"DM_AUTH_LOCATION"="[domain]"
"DM_DATABASE_NAME"=""
"DM_DOCBASE_CONNECTION"="[DB_TNS]"
"DM_DATABASE_USER"="[docbase_name]"
"DM_DATABASE_ID"="db_id"
"DM_SERVER_VERSION"="6.5 SP2"
"DM_HOME"="E:\\Documentum\\product\\6.5"
"DM_CONFIGURE_TIME"="Fri Jan 14 12:34:00 CET 2011"
"DM_SERVICE_NAME"="[service_name]"
"DM_RDBMS"="Oracle"
"DOCUMENTUM"="E:\\Documentum"
7) Copy the dbpasswd.txt and webcache.ini file from first CS to second CS, in following path:
…\Documentum\dba\config\[docbase_name]
8) Create the folder for the session log files
…\Documentum\dba\log\[docbase_name]
9) Start the docbase services on both content servers
10) Using DA create the dm_LogPurge_LB1 job, as a clone of dm_LogPurge. Set as designated server the second CS (the one installed now). Set other settings similar to original LogPurge job (method, arguments, etc.).
11) Advice: in a multiple-CS environment, it is recommended to set a designated server for each job (otherwise it can happen a job is started simultaneously on 2 CS). User job sequences, if necessary.
12) Create the ACS object for the second Content Server
dmbasic -fE:\Documentum\product\6.5\install\admin\dm_acs_install.ebs -eInstall – [docbase_name].[CS_name] [install_owner] [password] [server_host_name]ACS1 [CS_name] 9080 http F "" ]dm_acs_install.log
Update the acs.properties file with the newly created ACS object by adding in the properties file
…\[method_server_path]\deploy\acs.ear\APP-INF\classes\config\acs.properties
the entries for the new created object:
repository.name.i=[docbase_name].[CS_name]
repository.login.i=[install_owner]
repository.password.i=[password]
repository.acsconfig.i=[acs_config_object_name]
* i – number not used yet in this file settings
13) Start the JMS.
Test and enjoy!
