1. BOCS 구성에 필요한 서버 모듈
   1. Content Server
   2. Documentum Messaging Server(DMS)
   3. Branch Office Caching Services(BOCS)
   4. Documentum Administrator(DA)
2. 분산 환경 테스트 구성
   1. Lenovo T61에 Windows 2003 Server + CS + DMS + DA 설치
   2. VMWare에 Windows 2003 Server + BOCS 설치
   3. VMWare에 Windows XP + jre-6u17-windows-i586.exe 설치(UCF Client에서 JRE가 필요하기 때문에)
3. 분산 환경 설치 및 기본적인 환경 설정에 관련된 내용은 아래 문서 참조
   1. Distributed_Content_Configuration_And_Troubleshooting.pdf
   2. Documentum Content Server 6.5 Distributed Configuration Guide.pdf
   3. Documentum_BOCS_65_SP1_release_notes.pdf
4. ?:/Documentum/jboss4.2.0/server/DctmServer_MethodServer/deploy\acs.ear/APP-INF/classes/config/acs.properties

   #Mon Nov 23 13:49:44 KST 2009

   bocs.pulling.interval=10

   primary.content.store.quota=1000M

   mode.cachestoreonly=false

   jms.queue.name=/queue/null

   bocs.keystore=

   mode.debug=false

   java.naming.factory.url.pkgs=org.jboss.naming\:org.jnp.interfaces

   repository.acsconfig=XN-BONGACS1

   repository.name=xn_test_rep.xn_test_rep

   bocs.pulling.mode.enabled=

   repository.login=Administrator ß Content Server 관리자 계정

   repository.password=xxxxxx ß 매뉴얼에는 Trusted Connection이기 때문에 굳이 넣을 필요가 없다고 하지만 없을 경우 정상 작동이 안됨

   proxy.port=

   policy=Throttle,1,10,0

   jms.url=jnp\://XN-BONG\:9084

   policy.1=ReplaceRequest,50,1

   proxy.host=

   dms.pulling.url=

   primary.content.store.root=C\:\\Documentum\\acsCache

   jms.connection.factory=/MethodServerQueueConnectionFactory

   bocs.configuration.name=

   tracing.enabled=false

   jndi.factory=org.jnp.interfaces.NamingContextFactory

5. BOCS 서버의 ?:/Documentum/jboss4.2.0/server/DctmServer_BOCS/deploy/bocs.ear/APP-INF/classes/dfc.properties

   dfc.data.checkout_dir=${dfc.data.user_dir}/checkout

   dfc.data.dir=C:/Documentum/jboss4.2.0/server/DctmServer_BOCS/data/BOCS

   dfc.data.export_dir=${dfc.data.user_dir}/export

   dfc.data.user_dir=${dfc.data.dir}

   dfc.search.ecis.enable=false

   dfc.search.ecis.host=

   dfc.search.ecis.port=

   dfc.tokenstorage.dir=${dfc.data.user_dir}/apptoken

   dfc.tokenstorage.enable=false

   dfc.docbroker.host[0]=xn-bong ß Docbroker 가 있는 Host 정보

   dfc.docbroker.port[0]=1489 ß Docbroker Port 정보

6. BOCS 서버의 ?:/Documentum/jboss4.2.0/server/DctmServer_BOCS/deploy/bocs.ear/APP-INF/classes/config/acs.properties

   mode.cachestoreonly=true

   tracing.enabled=false

   mode.debug=false

    

   #Added for jboss

   jndi.factory=org.jnp.interfaces.NamingContextFactory

   jms.url=jnp\://BOCS_SVR\:8090

   java.naming.factory.url.pkgs=org.jboss.naming\:org.jnp.interfaces

   jms.connection.factory=/BOCSQueueConnectionFactory

   jms.queue.name=/queue/bocsQueue

    

   bocs.keystore=C\:/Documentum/bocs/config/bocs.keystore

   bocs.configuration.name=BOCS_Svr ß DA(Documentum Administrator)의 분상환경 구성 요소 중 BOCS Object Name을 입력

   bocs.pulling.mode.enabled=FALSE

   dms.pulling.url=

   bocs.pulling.interval=10

    

   proxy.host=

   proxy.port=

    

   policy=Throttle,1,10,0

   policy.1=ReplaceRequest,50,1

   cache.store.root=C\:\\Documentum\\acsCache

   cache.store.quota=1000M

   primary.content.store.root=C\:\\Documentum\\primeStore

   primary.content.store.quota=1000M

1. WDK 기반의 Client의 app.xml의 ACS/BOCS 관련 정보 수정(/apache-tomcat-6.0.18/webapps/da/wdk/app.xml)

<!-- Begin {D6 accelerated content transfer (ACS) settings} -->

<!-- <accelerated-read> :

This is for accelerated Read, and it replaces the correpsonding 5.3.x <acs> configurations.

It allows accelerated read and write to be switched on and off separately.

For backward compatibility, WDK D6 first looks up the <acs> tag before looking up the

<accelerated-read> tag.

-->

<accelerated-read>

<!-- when set to be "true", enables ACS, and, when optimal, BOCS read operations -->

<enabled>true</enabled>

<!-- the followings are the existing options under the 5.3.x "acs" tag -->

<attemptsurrogateget>true</attemptsurrogateget>

<maintainvirtuallinks>true</maintainvirtuallinks>

</accelerated-read>

<!-- <accelerated-write> :

A separate configuration block for accelerated Write

-->

<accelerated-write>

<!-- when set to be "true", enables ACS, and, when optimal, BOCS write operations -->

<enabled>true</enabled>

<!-- when set to:

1. "prohibit-async" - application doesn't allow BOCS write asynchronously

2. "default-sync" - application should see content written from BOCS to ACS synchronously by default

3. "default-async" - application should see content written from BOCS to ACS asynchronously by default

-->

<bcs-write-mode>default-sync</b霓cs-write-mode>

<!-- when set to "true", allows override of default BOCS write mode by users

(in general, it should be scoped with <filter> tag, e.g. role-based) -->

<allow-override-bocs-write-mode>true</allow-override-bocs-write-mode>

</accelerated-write>

<!-- End {D6 accelerated (ACS) content transfer settings} -->

1. ACS/BOCS 구성 화면
   1. Network Location이 적용된 Login 화면

      

       

   2. Distributed Content 구성 화면

      

   3. Network Location : BOCS_loc

      

       

   4. ACS Servers : XN-BONGACS1

      

1. BOCS Servers : BOCS_Svr

   

1. Distributed Transfer

   

1. Messaging Server

   

1. ACS/BOCS 테스트 화면
   1. Content 등록 화면

      

1. Web Client에서 컨텐츠 다운로드시 BOCS 서버의 Caching 정보 확인

   (?:/Documentum/acsCache/content/ 경로 아래로 파일이 쌓임)

   

    

2. Web Client에서 컨텐츠 전송시 BOCS 서버의 Caching 정보 확인

   (?:/Documentum/primeStore/ 경로 아래로 compressed/uncompressed 폴더에 임시적으로 컨텐츠를 Writing 한 후 일정 시간이 지나면 Content Server에 전송)