Archive

Posts Tagged ‘repository’

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 ,Installation and Configuration of ACS

November 10, 2010 Comments off

In my previous post i tried to bring out what is ACS , today lets see how we can install and configure an ACS , to start off with the Prerequisites for ACS:

a) Content Server.

b) Global registry Repository.

Installation and configuration of ACS:

Administrator doesn’t need to install it explicitly; it gets installed automatically when Content server 5.3 sp1 and above are installed. An ACS config. Object is also created automatically in the menu:

Administration-> Configuration->ACS Servers. As shown in following diagram:

 

The Administrator can check whether this service is running or not by going to following link in his system http://[system ip address]: [port no]/ACS/servlet/ACS. Or he can see the ACS service running in the services of his operating system service manager.

The Configuration of ACS means configuration of ACS server for the repository which will serve by that ACS server to specified network locations. We need to configure the ACS server config. Object for each repository, irrespective of the content server under which it is created. This configurations will be as following:

1)    Go to the Servers in Administration->configuration->Servers and click on information button to edit the properties for that server config. Object.

Go to “Connection Broker Proj” Tab and add the address of host name on which the ACS server is installed and also specify the Proximity for that Server. Administrator can add more than one connection broker to one repository at any time.

Now after following the above steps , you will see that the ACS server got added to server config object:

2)    Go to the “Network Location Proj “ tab to add the network location to be served by the repository.

Network Location got added to Server Config Object as in below:

3)    Now save and come out of the server config object to the ACS server config Object. And verify the “Connection Broker Projection” and “Network Location projection” for correct entries.

Now the ACS server is configured to the Repository server through a Connection broker to serve a set of network location.

Note: While creating the connection broker object take care for false host name because the Documentum never verifies for fake/non existing hosts.

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.

Web Content Management Systems – Getting Started

October 26, 2010 Comments off

A Web Content Management System (WCMS) is a software tool used for managing and publishing content (text, graphics, links, etc) in the web.  Systems of these kind are often used for storing, controlling, versioning, and publishing industry-specific documentation such as news articles, operators’ manuals, technical manuals, sales guides, and marketing brochures.

Benefits of WCMS:

A content management system supports the following features:

  1. Import and creation of documents and multimedia material.
  2. Identification of all key users and their content management roles.
  3. The ability to assign roles and responsibilities to different content categories or types.
  4. Definition of the content workflow tasks, often coupled with event messaging so that content managers are alerted to changes in content.
  5. The ability to track and manage multiple versions of a single instance of content.
  6. The ability to publish the content to a repository to support access to the content. Increasingly, the repository is an inherent part of the system, and incorporates enterprise search and retrieval.
  7. Some content management systems allow the textual aspect of content to be separated to some extent from formatting. For example the CMS may automatically set default color, fonts, or layout

When one can choose WCMS:

  1. If you are publishing a lot of content from a number of authors, and yet the content are to be published in the single format (eg. Portal for a world wide reputed company) you should consider a Web Content management system (WCMS).  It can allow you to manage your content efficiently and cost-effectively.
  2. When you have resources who are non – technical editors (not strong HTML, programming), you can consider WCMS as it allows to create, edit and publish content on a website.
  3. When the published contents needs frequent edition or updation we can consider WCMS as this tool makes it easier to update a content and also to maintain the old version of the content.
  4. When you want to publish large volumes of data or web pages in a short span of time you can consider WCMS. This is an important issue for the modern organization. The quicker you get key content published, the more value it creates.

Hope this info is worthy for Newbies.

Will come out with  more points about WCMS in my next Post.

Categories: WEB-CMS Tags: , , ,

Functioning aspects of Documentum

March 21, 2010 Comments off

Documentum has the following functioning sectors:

  1. Client-WebTop or Desktop client – The client can be a web based client (WebTop client) or can be a desktop client.
  2. Content repository – The content repository contains the actual files. It stores data either as File system or External storage
  3. Database – The database contains the address about where the files are actually Stored (metadata).
  4. Web development kit (WDK) – The WDK contains a set of API’s which help to retrieve the relevant data.
%d bloggers like this: