Hi Karimulla,
I hope that the following information could explain the design of SAP DMS and the Content Server better:
The Knowledge Provider (KPro)
is part of the SAP Web Application Server and is the central service for
managing and storing any documents. The KPro consists of the following
components:Document
Management Framework (DMF)Document
Management Service (DMS)
DMS is a service that is as near to an application provided by KPro.
The aim of the DMS is to provide an application with an interface (application
programming interface (API)) that the application can use to manage documents
efficiently without having to deal with the relevant special problems of
physical storage. The DMS cannot exist without appropriate infrastructure. It
is strictly based on the Content Management Service (CMS).Content
Management Service (CMS)
While the DMS permits an application-like view of the documents that are to be
managed, the CMS deals with the details that are relevant for storage and the
technical management details. This includes creating document versions,
recovering documents, managing the storage server, and so on.
The SAP content server is the server
component of the SAP Knowledge Provider (KPro). The basis of the SAP content
server is the content server engine. The engine receives all URLs, checks their
validity, and starts to process their requirements. The SAP content server
saves the data in an SAP MaxDB. However, the SAP content server
engine does not address the database directly; instead, it uses an adapter
called the content storage layer (the storage layer hides the specific access
mechanisms of the storage medium behind a uniform, byte stream-oriented
interface). The content storage layer uses ODBC to access the database. SAP MaxDB
manages the individual repository tables in which the data (documents) is
stored.
Best regards,
Christoph
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.