/
ArchiveLink configuration (tC)

ArchiveLink configuration (tC)

Content

Introduction

The repository configuration of a tia® Content Server Core needs to be provided as repository.cfg file. At the same time configuration on SAP side is required.

This article focuses on the specifics of an ArchiveLink setup without explaining all other requirements.

How to configure where to find the repository.cfg

The repository.cfg file is a text file and can be manually edited. It is recommended to stop tia® Content Server Core before editing and restart to apply the new configuration.

For the location of the repository.cfg file depending on the deployment, read Location of the repository.cfg file.

Configuration of ArchiveLink

For information about the configuration file like where to find it, syntax rules, and encryption of sensible parameter data like passwords, see chapterRepository-wide settings.

For information about available configuration parameters for a specific service, see chapter Services (tC).

In the repository.cfg file, configure the repositories required.

Example: Setup repositories with the names FI and HR.

repositoryfactory.repositorylist = FI,HR

Other configurations for the repositories like storage parameters of the content service are required.

SAP Configuration

OAC0 - Content Repository configuration

KGS CS is configured within SAP using the definition of Content Repositories. The transaction is OAC0. Following parameters have to be set:

  • HTTP server → Hostname or IP of the webserver

  • Port Number →  Port with which the webserver can be reached

  • HTTP Script →  <Servlet name>/contentserver

A container deployment doesn’t have a <Servlet name> and the HTTP Script here is just contentserver .

ArchiveLink Security (OAC0)

To use the ArchiveLink security, enable the signature and send (& activate) the certificate to the Content Server.

To see the signature parameter, access the Full administration.

To use the security No signature needs to be unchecked.

To send the certificate click on the envelope button. This sends a putCert request to the Content Server.

Activating a certificate

Manual activation of a certificate is only required, when for the repository the parameter security on Content Server side is set to 2.

  1. Access the CS Admin in the OAC0 transaction, after you send the certificate and open the Certificates tab.

  2. Enable the Edit mode

  3. Select the certificate

  4. Activate the certificate

Security

If the security is set to 1 or 2 it is necessary to have a keystore service configured.

If the keystore service of a repository has the status stopped when the application is started, the keystore service is probably not configured correctly.

Possible error could be that the keystoreservice type is set to none.