Implementing a Content Model for a Document Area

Purpose

If your requirements concerning document attributes, relations between documents, etc. cannot be satisfied by the content models that come with the Training, Documentation, and Intranet-Management areas of the Knowledge Warehouse you can create a dedicated area and content model.

In addition to creating the content model you need to configure the Knowledge Warehouse storage environment so you can store the info objects of your area.

Content modeling and content storage configuration in the Knowledge Warehouse are done with the Document Modeling Workbench (DMWB) and the Implementation Guide (IMG), respectively. If your content model includes structures, you also need to configure the SAP Structure Repository.

To facilitate the creation of a content model for a new area, the KWCA (Knowledge Warehouse: Templates) area provides virtual info object classes and attributes which you should use as templates for your own content model. Also, the virtual classes in KWCA are partially pre-defined and already associated with run-time tables for document management data and for structures (which are stored in the SAP structure repository). Therefore, using them as a starting point will save you the effort of creating these table sets and of configuring the content storage environment.

A content model for a Knowledge Warehouse area must comprise the following entities:

·        LOIO classes

·        PHIO classes

·        A class connection space

Optionally, a content model may comprise these additional entities:

·        Relation classes (if you define additional relations)

·        Info object attributes (if you define additional attributes)

·        Context classes (these are not yet supported in Knowledge Warehouse 5.0)

Prerequisites

You need to have the authorizations associated with the role SAP_KM_KW_MODEL_ALL.

Process Flow

Implementing a content model for a document area involves several kinds of activities:

·        Specifying the content model

·        Mapping the content model to the storage environment

·        Specifying the web server and RFC destinations for accessing content.

·        Activating index generation

...

       1.      You create an area, specify its properties, and activate it.

       2.      You look at the virtual info object classes in area KWCA to find out which of them suit your needs best.

       3.      You replicate KWCA virtual classes as virtual classes in the new area. If necessary, you modify the class properties and the instance attributes of the virtual info object classes.

       4.      You activate the virtual classes.

       5.      You replicate the virtual classes as real classes. You maintain the standard property WEBSERVER_PROGRAM in all real LOIO classes (except the folder class). If you want to create structure objects with the SAPgui front-end you need to maintain the free properties IWB_CLASS_TOPIC_DEFAULT and IWB_CLASS_TOPIC_TYPE_DEF of the structure LOIO class(es).

       6.      You activate the real classes.

       7.      You create and define a class connection space in the new area. You specify which relation classes you want to hold between the info object classes you created. The built-in relation classes that are available for defining a class connection space are defined in the SYSTEM area.

       8.      You activate the class connection space.

       9.      You create content templates for info objects.

   10.      You create a content repository for content objects in the SAP System and on the SAP Content Server.

   11.      You map the content category CUSTCONT onto this content repository.

   12.      You specify the web server and RFC destinations for viewing and editing content.

   13.      You activate the indexing service for the new area's content.