Documentum

Install_Server_42_UNIX_Ora.pdf
On UNIX machines, you can have multiple installations on the same machine.
Within each installation, you can have multiple Docbases, each with its own
eContent Server process. You can also have multiple eContent Server
processes running against a single Docbase.

MISC
Database deals with structured data,whereas CM deals with semi-structured and unstructured such as
web pages,pdfs,Audio &Vidio ,etc.
cm Lowering cost and increase of operational efficiency (speed) by automating of processes and
providing the right content to the right people at the right time.


Docbases
A Docbase is the repository for the persistent objects managed by Content Server. A
Docbase stores the object metadata and, sometimes, content files. A Documentum
installation can have multiple Docbases. Each Docbase is uniquely identified by a
Docbase ID, and each object stored in the Docbase is identified by a unique object ID.
(Identifiers, page 26, in the Content Server Object Reference contains information about the
identifiers recognized by Content Server.)
Docbases consist of two sets of tables in the underlying RDBMS: object type tables and
type index tables.

A DocBroker
 is a name server for the Documentum Content Server. When a Connect
method is issued, the request goes to a DocBroker identified in the client¡¯s dmcl.ini file.
The DocBroker returns the connection information for the Docbase or particular server
identified in the Connect method.
DocBrokers do not request information from the Content Servers, but rely on the servers
to regularly broadcast their connection information to them. Which DocBrokers are sent
a server¡¯s information is configured in the server¡¯s server config object.
Which DocBrokers a client can communicate with is configured in the client¡¯s dmcl.ini
file. You can define primary and backup DocBrokers in a dmcl.ini file. Doing so ensures
that users will rarely encounter a situation in which they cannot obtain a connection
to a Docbase.
For more information about how servers, clients, and DocBrokers interact, refer to the
Content Server Administrator¡¯s Guide.