Definitions of Terms (SAP Library - Knowledge Provider (BC-SRV-KPR))

Definitions of Terms

For the purposes of this section, a document comprises administrative data and content.

Administrative data identifies and describes a document.
The content of a document refers to closed datasets. The administrative data identifies and describes the content. A single closed dataset is known as a content unit.

In SAP terminology, a content server is any server that manages content. A content server may be a database, a file server, an SAP system, or an external archive.

The data administration terms content repository, document header, and component are of particular importance in identifying documents.

A content repository is the administrative entity that accesses the logical storage space for documents on a content server. Several content repositories can exist on one content server. A content repository is identified by the parameter contRep.

The document header is an administrative entity comprising several components. It is identified by the parameter docId. A document header is assigned to one particular content repository.

A component represents, on the administrative level, one particular content unit. It is assigned to one particular document header and is identified by the parameter compId.

The relationship between content repository, document header, component, and content is illustrated in the diagram below:

Note

It can happen that a document with only one component is created, and this component is later deleted. This results in an ‘empty’ document, that is, a document with no components. In order to avoid possible contradictions in this documentation, we will assume that empty documents and empty components can exist. This may be the case if, for example, a file with the file size 0 bytes is stored.

The combination contRep/docId is the unique address of a document header.

The combination contRep/docId/compId is the unique address of a component.

In certain circumstances, documents have a security level. This means that functions executed on the document must be authenticated. For each document header, you can define whether authorization is necessary for particular functions. However, this information is not defined in the document header for each function of the HTTP Content Server Interface, but via access modes. Access modes are discrete groups of SAP Content Server HTTP interface functions.

The Hypertext Transfer Protocol (HTTP) is the communication protocol typically used to access objects on the Internet. The W3C (World Wide Web Consortium, http://www.w3c.org) is currently further developing this protocol. There are two versions of the HTTP protocol, HTTP/1.1 and HTTP/1.0, and either can be used for the communication process. Request for Comment (RFC) 2068 specifies the protocol HTTP/1.1. HTTP/1.1 contains more specific regulations than HTTP/1.0 (RFC 1945), with the intention of making implementations of the protocol more reliable.

The SAP Content Server HTTP interface is designed in such a way that the client SAP system always initiates communication. The content server being addressed by the SAP system is always a server and never a client, which means that it never instigates communication with the SAP system.

Hypertext Markup Language (HTML) is a standard format and description language for Internet pages.

Uniform Resource Locators (URLs, see RFC 2396) are a standardized mechanism used to address uniquely defined objects on the WWW. As well as serving as addresses, URLs can also contain functions and parameters that are interpreted by the object being addressed.

UTC (the common abbreviation for Coordinated Universal Time) is used for all expressions of time in this specification.

Note

The following rules apply to the spelling of functions, parameters and key words in this section:

All terms defined in the Hypertext Transfer Protocol HTTP/1.1 (RFC 2068) are used here (for example, Content-Type). The terminology of the HTTP/1.0 (RFC 1945) protocol is also used.
Terms specific to this interface are not capitalized if they consist of one syntactical term (for example, info). A combination of lowercase and uppercase is used if a term consists of more than one syntactical term (for example, contRep).