About storing StreamServe documents Content Server

StreamServer applications use OpenText Enterprise Library Services to store documents in Content Server. Enterprise Library Services provide an interface to ELS and manage the document types, metadata and content types of content stored in the Content Server storage.

Document type requirements

StreamServe applications that store documents via Enterprise Library must use document types. Each document type used by a StreamServer application must be mapped to a document model in Enterprise Library.

In addition to being mapped to a document model, each document type can also (optionally) be assigned to one or more Content Server Categories.

Note:

If a StreamServe document type is mapped to both a document model and Category, the document model and Category do not need to be associated with one another.

To store custom metadata with documents, such as customer name or number, the StreamServe metadata must have either a corresponding ELS property (in the document model) or a corresponding attribute (in the Category).

Example 1

Example of a document type, document model, and Category mapping

This example shows a StreamServe document type that is mapped to both a document model and a Category. The metadata in the document type are mapped to attributes in the Category.

 

Example 2

Document type and document model mapping

This example shows a StreamServe document type with three metadata (Customer number, Customer name, and Due date) that is mapped to an Enterprise Library document model which contains corresponding properties.

 

 

Enterprise Library properties for storing StreamServe documents

Two Enterprise Library properties are required for StreamServe documents that are stored:

•	Document name

•	Content Server folder ID – which is the Content Server Workspace folder

These are global properties in Enterprise Library. Global properties are available for all document models in Enterprise Library.

You can use other global Enterprise Library properties to store StreamServe documents. For example, if you want to specify the content type of a document, which controls the viewer used in Content Server.