基于MOSS的海量数据的企业内容管理（ECM）平台level 200.ppt

媒体文件、工程图纸 银行、制造业、医药行业 数据增长的速度很快 SQL Server存取几百兆上G单个文件的效率 * Getting Started with Documentum 1-* Purpose of the Slide: To give a basic 30k foot overview of the Documentum architecture and some of its core content services Script: The foundation of the Documentum Content Server architecture is the Repository. The Repository consists of 3 components, a file store, a RDBMS, and a search engine (allows content searches as well as full text searching). The file store is where the content actually resides while the RDBMS contains the property or metadata information related to the content (It is possible to store content in the RDBMS but typically this is not the best approach) Some key aspects of this architecture include: Each repository can support multiple local or distributed content stores. Object-oriented design with an object-relational database. Content can be stored on a file system or in a database. The database contains all of the data captured within Documentum including content and object meta-data. Documentum supports the following databases (Oracle, Microsoft SQL Server, Sybase, Informix) Multiple repositories can be connected as a Federation to simplify administration (more on that later) Content can be replicated between multiple Docbases or distributed storage areas (more on that later) Searches, document links and virtual documents can be defined across Docbases. Protected Directory (if needed) Only the Documentum installation owner account can directly access the files on the file system. The Content Server renames files very obscurely, so that its contents, format, and filenames are not obvious. Client applications communicate with e-Content Server through the DFC (Documentum Foundation Classes), the server API methods (DMCL), or DQL (Document Query Language). Getting Started with Documentum 1-* Purpose of the Slide: To give a basic 30k foot overview of the Documentum architecture and some of its core content services. Builds off of previous ar