Guide Autodigit Community Edition

Table of Content

Prerequisites

Prerequisites for tia® and kgs Software Components

Installation of the tia® Community Edition

Java and Tomcat need to be pre-installed and the community edition package needs to be downloaded. The following steps will show you how to deploy our software.

Step 1:

Open the Tomcat configuration page and go to “Manager App”.

Step 2:

Choose the war-file of the community edition and deploy it into the tomcat.

After this step the tomcat should create a folder in his webapps directory as well show the app in the application section of the manager.

Configuration of the tia® Community Edition

The application will be delivered with a repository “CE”, which is already partly configured. This repository is meant to be a configuration reference. It can be deleted of course.
The Community Edition supports two content repositories maximum.

Step 1

To create a new repository click on the Repository Management tile. After that you need to enter a repository Id.

Step 2

Configure the repository. The Community Edition includes the storage services “Filesystem - Encoded” and “ S3”. The metadata services, protocol services, data encryption and retention service are not supported in the Community Edition. After the configuration of the services, the interface specific options need to be configured. For more details about the parameters, please have a look into our parameter list. (Configuration Parameters (Communtiy Edition)).

After all the mandatory services and options are configured please save the repository.

Step 3

Finally, to apply the changes for productive use, click on the Apply Configuration tile.

After you have confirmed to load the configuration the repository status will be shown.

The services will be restarted immediately. If the repository is not running, please check your configuration again.

SAP Connection

Step 1

Open the transaction “OAC0” in SAP and add or change a content repository.

Step 2

Define the parameters for the content repository depending on your setup.

The HTTP Script is depending on the name of your application (the filename of the WAR containter file). The servlet endpoint is /contentserver.

Step 3:

Define your document types (OAC2) and business objects (OAC3) to use this repository for archiving.

Content Repository Configuration

Parameter	Mandatory / Optional	Options	Description
Storage Services	Mandatory	Filesystem Filesystem - Encoded S3 Storage S3 Storage - Managed Buckets kgs Store ZIP Container Azure Blob Storage without Storage	Defines the type of storage service to be used.
Metadata Services	Mandatory	elasticsearch kgs Store Apache Kafka Database Navigation without Metadata	Defines the type of service to be used for searching after metadata.
Keystore Services	Mandatory	PKCS12 Keystore without Keystore	Defines which type of keystore to be used.
Protocol Services	Mandatory	elasticsearch Database without Protocol	Defines the type of service to store and index protocol data.
Config Services	Optional	File System without Configuration	Defines how the metadata definition files are saved.
Data Encryption	Optional	AES Encryption with GCM without Encryption	Defines the type of algorythm to be used for content encryption.
Retention Service	Optional	Retention Provider without Retention	Defines how the retention management is handled.
Interfaces	Mandatory	ArchiveLink	Defines the type of interface to be used with this repository.

Interfaces

Interface	Parameter	Mandatory / Optional	Options	Description
ArchiveLink	Archive Mode	Optional	only Archivelink only Knowledge Provider mixed usage	Defines the structure the documents are stored.
ArchiveLink	AchiveLink Security	Mandatory	Security with automatic activated certs (requires Keystore) Security with manual activated certs (requires Keystore) Security inactive	Defines the certificate handling for the ArchiveLink SecKey scenario.
ArchiveLink	Default Document Protection	Optional	active / inactive	Defines the default document protection settings.

Storage Services

Storage Service	Parameter	Mandatory / Optional	Options	Description
Filesystem - Encoded	Storage Folder	Mandatory	Path	Sets the directory, where the documents should be stored to.
Filesystem - Encoded	Repository Id as Root Directory	Mandatory	active / inactive	Defines if the repository id will be used as root folder in the desired storage path.
S3	User	Mandatory		Depends on the used S3 endpoint. Examples: Amazon AWS → Access key ID
S3	Password	Mandatory		Depends on the used S3 endpoint. Examples: Amazon AWS → Secret access key
S3	Bucket	Mandatory		Defines the name of the bucket in which the documents will be stored.
S3	Repository Id as Root Directory	Mandatory	active / inactive	Defines if the repository id will be used as root folder in the desired bucket.
S3	Region	Mandatory		Specifys the aws region.
S3	Endpoint	Mandatory		URL for your S3 endpoint.

Config Service

Config Service	Parameter	Mandatory / Optional	Options	Description
File System	Directory to store the metadata definition files	Mandatory	Path	Defines a path, where the metadata definition files should be saved.

Keystore Service

Keystore Service	Parameter	Mandatory / Optional	Options	Description
PKCS12 Keystore	Filename	Mandatory	Filename	Defines the filename of the keystore.