Start of Content Area

Object documentation Info Object Classes  Locate the document in its SAP Library structure

Definition

An info object is a document or a document-like object in the Knowledge Provider. We differentiate between logical and physical objects.

The info object class (IO class) provides information about the characteristics of an IO. The IO class of a logical info object is called a LOIO class, and the IO class of a physical info object is called a PHIO class.

A LOIO class can be, for example, a class for MIME objects or glossary entries. A PHIO class can be, for example, a class for pictures, videos, or text, or a class for glossary entries in HTML, .doc, or any other file format.

Use

There are two types of IO classes: virtual and real. In the entity tree in the left-hand frame of the DMWB window, the symbol This graphic is explained in the accompanying text appears to the left of the names of all virtual IO classes. Real IO classes have the symbol This graphic is explained in the accompanying text and are subordinate to the virtual IO classes in the entity tree.

This graphic is explained in the accompanying text

Virtual and real IO classes of a logical IO

With the DMWB, you can either create new content models, or take existing models and modify them to suit your requirements.

There are a number of ways of creating a new content model:

Note

IO classes and relationship classes that are derived from virtual classes inherit the (instance) attributes of the virtual class.

When you activate real IO classes, the KPro runtime system can administrate IOs of the classes involved.

IO classes, on the other hand, exist only in the development layer. They can be used as models from which real IO classes are derived.

Note

The IO classes that you incorporate into connection spaces must be real and active.

Deriving Real Classes from Virtual Classes

If you want to replicate new LOIO and PHIO classes from existing IO classes of other document areas, you first have to derive a new virtual class from an existing virtual class. Once you have done this, add to or change the attributes as required. You can then replicate real classes from the virtual class in your document area.

We do not recommend that you derive real classes directly from an existing virtual class in another document area. This is because you would have to make any required changes in the virtual class of the other document area, and not in the real class itself.

Note

Note that the inheritance mechanism, which passes on properties from virtual classes to real classes, only handles instance attributes, and not standard properties or free properties.

When you create an IO class, we recommend that you add the suffix _V to the end of the name of the class. This makes it easier to quickly identify the virtual classes.

Example

Name of superordinate virtual LOIO class: IWB_GLOS_V

Name of subordinate real LOIO class: IWB_GLOS

Names of virtual IO classes can have a maximum of 30 characters. Names of real IO classes can have a maximum of 10 characters.

End of Content Area