Home > DOCUMENTUM > BOCS Implementation Contd-Single Model 2

BOCS Implementation Contd-Single Model 2

November 15, 2010

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.

%d bloggers like this: