Entering content frame

Background documentation Content Repositories Locate the document in its SAP Library structure

Transaction Code

Name in the SAP System

IMG Activity

OAC0

Content Repositories

Defining Content Repositories

 

In this transaction you define the content repositories in the SAP system, and thus the storage systems (the content servers) on which documents can be stored.

The fields on the Details and Create tab pages differ, depending on what storage type you choose for your repository. In the field for storage type, you set what kind of physical storage medium you want for your repository:

Choose this setting if you want to store your content on a HTTP content server, for example, the SAP Content Server, or third-party HTTP content servers.

Choose this setting if you want to store your content directly into the SAP database. See below for more information.

Choose this setting if you want to store documents in an Structure linkSAP ArchiveLink or Structure linkArchive Development Kit (ADK) environment, or in an application that uses SAP ArchiveLink (see also Structure linkSAP ArchiveLink – Application Scenarios) or ADK (see also Structure linkArchiving Application Data).

Usually, you do not need to make any settings here. The structure repository is only used in the SAP Knowledge Warehouse environment.

Note

You can opt for simple or full administration. The number of fields displayed depends on your selection.

After you have saved your content repository, the time of creation, the creator’s user name, and the creator’s real name are automatically inserted. If you have made changes to an existing repository, details about the changes are also inserted. The time is set in accordance with the time zone specified in the user settings.

HTTP Content Server

To store content in a content server, choose HTTP Content Server in transaction OAC0 for your content repository. A prerequisite for this is that you have defined your content repository using CSADMIN (see also Content Server and Cache Server Administration). You can go directly from OAC0 to CSADMIN by choosing This graphic is explained in the accompanying text.

You can also send certificates here. To do this, choose This graphic is explained in the accompanying text. You need to send certificates to be able to work with signed URLs. After the certificate has been sent to the content server, it must be activated on the content server before you can work with the server and store documents.

You can also carry out a connection test (This graphic is explained in the accompanying text) and call status information (This graphic is explained in the accompanying text). The status information then appears on the lower half of the screen.

Besides the version number, you also need to know the host name of the HTTP server where your repository is. You also need the port number, the SSL port number if applicable, and the HTTP script.

You specify all this information in the simple administration function for HTTP content server repositories in transaction OAC0.

Example

Example of a HTTP content server repository in OAC0:

This graphic is explained in the accompanying text

Usually, the simple administration function is sufficient.

However, you may need the full administration function in the following situations:

Note

The flag no signature is deactivated by default; in other words, the signature is activated by default. This option controls the availability of the functions for checking and creating signatures.

R/3 Database Repositories

To store content in an R/3 database, choose R/3 Database in transaction OAC0 for your content repository. When selecting this storage medium, you can specify for the sub-storage medium whether you want to store the actual document content or URLs. After specifying the version number, you also need a content table (client-specific or cross-client), that is, a table in which your documents are stored in the database. The structure of the content table should correspond to the table SDOKCONT1. The field CLUSTID, however, can be larger than the corresponding CLUSTID field in SDOKCONT1. Also, the client may be available (for example, in table BDS_CONT1).
This is all the information you need to set in the simple administration function for R/3 database repositories in transaction OAC0.

Example

Example of an R/3 database in OAC0:

This graphic is explained in the accompanying text

As before, simple administration is usually sufficient here.

You only need to use full administration in special cases, such as the following:

Note

The flag no signature is deactivated by default; in other words, the signature is activated by default. This option controls the availability of the functions for checking and creating signatures.

 

 

 Leaving content frame