2 Documentum Administrator as to enable a single server application
<Connector port="9001" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="9101" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />
<Connector port="9201"
enableLookups="false" redirectPort="9101" protocol="AJP/1.3" />
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
<Context docBase="da" path="">
</Context>
</Host>
<!--<Host appBase="da-prd" name="da-prd"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
<Context docBase="da" path="">
</Context>
</Host> -->
</Engine>
</Service>
Best Answer
-
(It's been a slow day... can you tell?) I'll take a stab at this, but I'm a little confused on what you want to do. Are you wanting to:
1. Have two separate instances of Documentum Administrator on the same application server? (Example: http://myserver:9001/da and http://myserver:9002/da are two installs of DA on the same physical server.)
2. Have two separate instances of Documentum Administrator on two separate application servers. (Example: http://myserver:9001/da and http://mysecondserver:9001/da are two installs of DA on two separate physical servers.)
For Option 1, other than customizing one instance of DA, it's not going to do you any good in terms of redundancy. If myserver were to crash, it's going to take out both installs of your DA. Option 2, at the cost of an additional server, gives you redundancy and failover possibilities.
Generally, you can install as many instances of DA on a single application server (although I don't know why) as you want. Just follow the guidelines for Tomcat as outlined in the WDK deployment guides and the Tomcat server instructions. If you're looking to automate some kind of failover mechinism then I need more detail on your setup.
0
Answers
-
(It's been a slow day... can you tell?) I'll take a stab at this, but I'm a little confused on what you want to do. Are you wanting to:
1. Have two separate instances of Documentum Administrator on the same application server? (Example: http://myserver:9001/da and http://myserver:9002/da are two installs of DA on the same physical server.)
2. Have two separate instances of Documentum Administrator on two separate application servers. (Example: http://myserver:9001/da and http://mysecondserver:9001/da are two installs of DA on two separate physical servers.)
For Option 1, other than customizing one instance of DA, it's not going to do you any good in terms of redundancy. If myserver were to crash, it's going to take out both installs of your DA. Option 2, at the cost of an additional server, gives you redundancy and failover possibilities.
Generally, you can install as many instances of DA on a single application server (although I don't know why) as you want. Just follow the guidelines for Tomcat as outlined in the WDK deployment guides and the Tomcat server instructions. If you're looking to automate some kind of failover mechinism then I need more detail on your setup.
0 -
Thanks again Chris,
We took option 2. Actually we made a VM image from Server1 and created Server2, then we configured the second so we could manage the second CS. At first we were short of servers so I thought having both DA on same machine would suffice. But I agree with you that on a server crash we would be left with nothing.
By the way, both CS are on different servers as well as their Databases.
Regards,
Ruben
0
Categories
- All Categories
- 111 Developer Announcements
- 49 Articles
- 104 General Questions
- 123 IM Services
- 40 OpenText Hackathon
- 31 Developer Tools
- 20.6K Analytics
- 4.1K AppWorks
- 8.9K Extended ECM
- 897 Cloud Fax and Notifications
- 77 Digital Asset Management
- 9.3K Documentum
- 29 eDOCS
- 123 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 1 XM Fax