Content-Repository configuration (CS)

Owned by Former user (Deleted)
Last updated: Jan 13, 2022 by Simone Conrad

Some parameters can be defined content repository specific. These can be set by following the menu option Main →  ContentServer4ArchiveLink as shown below:

Security

Parameter Name
DataType
Description
Default

Security

Int

0: Security Inactive

1: Security Active

2: Security Active. Seperate administration via CSAdmin necessary

This parameter can be defined Content Repository specific.


SecurityChangeOnCommand

CSV list of ArchiveLink requests (non-case sensitive), e.g. create, delete, update, etc.

When a request that is maintained in this list arrives, the value set in the Security parameter is inverted to process this request.

Example 1:

Security=2 the SecKey procedure is active.

SecurityChangeOnCommand=get,delete,info

The incoming GET request is processed WITHOUT checking the SecKeys incl. Expiration.

Example 2:

Security=0 the SecKey procedure is not active.

SecurityChangeOnCommand=get,delete,info

The incoming GET request is processed WITH examination of the SecKeys incl. Expiration.

This parameter can be defined Content Repository specific.


Allowed Clients

Only the clients specified here (IPs or hostnames) may write to the archive (create, update etc.). If no client is specified, all clients may write. The parameter is to be created as a CSV list. If a client is not listed, they receive the RC 401 à unauthorized.

This parameter can be defined Content Repository specific.

Allowed CSAdmin Clients

Only the IP addresses or hostnames specified here (SAP server) are authorized to use the CSAdmin function in SAP.

Requests from other IPs or hosts receive the RC 401 →  unauthorized. This parameter is to be created as a CSV list. The last IP segment can be used a wildcard. For example; ContentServer.AllowedCSAdmin=sapadm,192.168.1.2,192.168.2.*

This parameter can be defined Content Repository specific.


RFC

Parameter Name
DataType
Description
Default

RFC connection

Dropdown

Select the RFC connection configured in the KGS SAP Connector


For older versions

Configuration for SAP communication (CS)#RFCconfiguration(untilv5.1.0)


Viewer

Parameter Name
DataType
Description
Default

Enable Viewer

Checkbox

To use the tia® H5 Viewer (EN) with the KGS ContentServer, the Enable Viewer checkbox must be set within the desired repository.


Viewer Context

Dropdown list

Name of the used KGS Viewer profile.


Index Export

Parameter Name
DataType
Description
Default

Index Export

Dropdown list

Off: Function deactivated.

Internal: Additional attributes of the documents are determined via the ContentServer after creation of a document by RFC (pull procedure).

External: Additional attributes are transferred to the ContentServer (push procedure) via the SAP Event Mechanism.

off

Common

Parameter Name
DataType
Description
Default
Description
Description for the specific Content Repository
Disable Delete
Delete requests will not be processed/rejected for this Content Repository.

Backend

Parameter Name
DataType
Description
Default
Check Backend Mode

Dropdown list

If activated, when processing the serverInfo request, access to a random DocId for each Content Repository is checked.

This parameter can be defined Content Repository specific.

CAUTION: Only use this for troubleshooting!

Off

HTTP

Parameter NameDataTypeDescriptionDefault
GET HTTP RedirectString

If a valid Link is entered, a ArchiveLink GET-Request is redirected to the new target. The following fields are mandatory and substituted with the actual request Parameter:

  • {CONTENT_REP_ID}
  • {ARCHIVE_DOC_ID}
  • {COMPONENT_ID}

So, an Example would be:

http://<Serveraddress>:<Port>/KGSAdmin-CS/contentserver?get&pVersion=0047&contRep={CONTENT_REP_ID}&docId={ARCHIVE_DOC_ID}&compId={COMPONENT_ID}

which Results in a redirect for GET-Requests to the new Server. 

Caution: Only GET-Requests are forwarded. PUT and POST Requests will still be performed (and therefore archived) in the actual Contentserver.

Also Non-KGS Servers can be used as Target.


Components

Parameter Name
DataType
Description
Default

Sign and Verify Content

Checkbox

Creates a hash value and signs this with a timestamp. When the data is called, the hash value is verified against the signature.

This parameter can be defined Content Repository specific.

Inactive

SecurityProvider

Dropdown list

Currently only timestamp signatures with certificate are available.

This parameter can be defined Content Repository specific.


TrustedTimestamp with Certificate

Exclude Components from signingString

Excludes individual components from signing.

This parameter can be defined content repository specific.		note;kgsannotation;descr;pagelist

Compression Size (Mb)

Double

Defines that components equal or greater than the value specified here (in MB) should be compressed. This function is only supported if the DMS supports the “DMS_COMP_PROPERTY_COMPRESSI

ONSTRING” property. For example:

1 →  1 MB

0.0488 → 50KB

0.1953 → 200KB

12.5 → 12.5MB

0.6835 → 700KB

0.0009765 → 1KB

This parameter can be defined Content Repository specific.

0.0

Compression Mime TypesString

CSV list of MimeTypes that should be compressed. If this parameter is not

defined, the compression will be applied to all MimeTypes (=*). For example;

CompressMimeType=application/pdf,image/tiff

Apart from MimeTypes, document types can also be defined, if the SAPMimeExtentionLookup parameter was configured. The MimeType for the document category is then determined by RFC using the SAP table TOADD.

This parameter can be defined Content Repository specific.


Convert Single to Multipage Tiff

Checkbox

If enabled, during runtime, single page-tiffs (data1, data2, etc. components) are converted to multipage tiff format for display. The document in the archive will not be changed.

This parameter can be defined Content Repository specific.

Inactive


→ Configuration for SAP communication (CS) | Configuration (CS)