Posts Tagged ‘BOCS’

D2 Jobs and Monitoring

August 26, 2019 Leave a comment

Hello Readers !!!! In my previous post we have learned about the D2 Security aspects and the workflows & lifecycles, as mentioned I wanted to write something on the several  jobs that are available in D2 and how to monitor them, at the end of this post I will try to mention a little information on the Session timeout settings.

D2 Monitoring


D2 Jobs






Session timeout and cookie


Enjoy Reading!!!


BOCS Implementation Contd-Single Model 2

November 15, 2010 Comments off

In my Previous Post , we have discussed the Single Model 1 implementation of BOCS. Another approach of executing BOCS can be put in Single Model 2 as in below:

Single repository with content in a distributed storage area.

In this model, content is stored in a distributed storage area. A distributed storage area is a storage area with multiple component storage areas. One component is located at the repository’s primary site. Each remote site has one of the remaining components. Each site has a full Content Server installation (a content-file server, also called a content-file server or RCS) and an ACS server installation for the repository. Content is replicated from its source component to the remaining

Components by user-defined content replication jobs. This model can be used for either web-based clients or Desktop clients. If a remote site is using web-based clients, the site should configure the use of the ACS server or a BOCS server to access content, to provide optimal performance for the web-based users. Desktop clients use the Content Server at the remote site to access content. In this configuration, metadata requests are handled by the Content Server at the primary site and requests to write content to storage are handled by the Content Servers (RCS) at the remote sites.

Note: This figure depicts geographic locations, not individual machines.

Single Model-2 Distributed Architecture BOCS


In this model, users in the small branch offices say in Singapore and Thailand access the content Stored in the distributed storage component at the larger India branch office. Similarly, users in the small branch offices at Europe or  Australia  access content stored in the larger Australia branch office. If the users are logging in using a web-based client, content requests are handled through the ACS server at the appropriate branch office in Australia or India. If the users are logging in using a Desktop-based client, content requests are handled by the Content Server in Australia or India. (The graphic shows only users logging in using web browsers.) In this model, the remote sites using web-based clients could have BOCS servers, rather than just a web browser, to contact the branch offices for content requests.

Benets and best use

For sites using web-based clients, this model is best if Single Model 1 is not acceptable for any particular reason. For sites using Desktop clients, this model is the only model available for a single-repository distributed configuration.

Prerequisites and Installation of BOCS

November 11, 2010 Comments off

Unlike ACS , BOCS does come with an installer , lets see what are the various steps involved in Installing  BOCS.

Prerequisites for BOCS:

a) Content Server.

b) Global registry Repository.

c) Windows 2000 sp4 (Recommended).

Installation of BOCS:

a)    Double click on the BOCS installable

b) Accept the terms and condition for licensing

c)    If you are not using any services on the default port then select default else specify the port number.

d)     Enter the installation owner password

e)Installation information

f)    Installation complete

g) Restart your Computer to Start the services

In my next post , i will try to explain the various steps involved in Configuring BOCS.

Categories: DOCUMENTUM Tags:

Introduction to ACS and BOCS

November 9, 2010 Comments off

The Accelerated Content Server (ACS ) server is a content server dedicated to serving content. It does not process metadata nor write content to storage. It only processes content requests. It gets installed automatically while installing the Documentum Content Server. After installation administrator needs to configure it for distributed environment.

Branch Office Caching Services (BOCS) is a lightweight server product running in the Apache Tomcat servlet container. BOCS serves content files to Web client end users from a local content cache. BOCS servers communicate only with ACS servers and do not interact with Content Servers or a repository’s supporting database. BOCS servers cannot write content to a repository. BOCS servers use the HTTP or HTTPS protocol to serve content. BOCS is used in distributed environments. BOCS is easily installed and has minimal administration requirements. The BOCS server is supported on the same platforms as Content Server. It needs to be configured for each repository.

%d bloggers like this: