Content-Repository configuration (CS)

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.

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

GET HTTP Redirect

String

This Parameter can only be used from a Non-SAP Client!

If a valid link is entered, a ArchiveLink GET-Request is redirected to the new target. The response will be handled directly by the 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.

Empty

GET HTTP Forward

String

This Parameter can only be used from a Non-SAP Client!

If a valid link is entered, a ArchiveLink GET-Request is forwarded to the new target. The response will be handled by the actual Content Server.

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 Content Server.

Also Non-KGS Servers can be used as Target.

Empty