Versions Compared

Version Old Version 37 New Version 38
Changes made by

Tobias Stein (Unlicensed)

Tobias Stein (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

Available from tia® Content Server core Version 2.1.0

Public Access (RELEASE TAG) :

requires account on https://images.docker.kgs-cloud.de

Login to kgs harbour with:

docker login https://images.docker.kgs-cloud.de

docker will prompt for user and password.

Start with docker:

If docker is not installed yet on your system, please follow the docker installation instruction for linux e.g Debian.

Before you continue the setup, make sure that the command "docker --version" returns the following message.

If you want to set up a test instance of tia core, our default repository.cfg should be suitable for this purpose.

Otherwise feel free to customize the repository.cfg. Please also take note of the following configuration options /wiki/spaces/WIKI/pages/1368064007

View file
namerepository.cfg

  • place repository.cfg to in a folder

  • replace <Name> with your custom name for the tia core container

  • replace <Folder> with the Folderpath that contains the repository.cfg

  • replace <License> with the Folderpath that contains your license file

  • replace <Loglevel> with a log level of your choice e.g. DEBUG,INFO,ERROR

  • replace <BcryptHash> with a password of your choice encrypted with bcrypt (for an example please have a look on the section “Environment Variables” below)

  • replace <Version> with a available tia core version on harbor

Info

The following docker run command will deploy a tia core ArchiveLink (SAPHTTP) instance. If you want to install a tia core CMIS instance, please use the corresponding tag e.g. "-d docker.kgs-software.com/tia/core/cmis:latest"

Code Block
docker run --name <Name> -p 8080:8080 -v data_volume:/temp/data  -v <License>:/application/config/license/ -v <Folder>/repository.cfg:/application/config/repository.cfg -e LOGGING_LEVEL_ROOT=<Loglevel> -e WEBAPP_SECURITY_AUTH_BASIC_PASSWORD="<BcryptHash>" -d docker.kgs-software.com/tia/core/<product>:<Version>

Example:

Code Block
docker run --name tiacore-AL -p 8080:8080 -v data_volume:/temp/data  -v ./tiacore/license:/application/config/license/ -v ./tiacore/repository.cfg:/application/config/repository.cfg -e LOGGING_LEVEL_ROOT=INFO -e WEBAPP_SECURITY_AUTH_BASIC_PASSWORD="\$2a\$10\$5E1KpGIKSq6xuWmGf92bheB17V0l4fEMnVmYPqhWiazKddcx1TF/e" -d images.docker.kgs-cloud.de/tia/core/saphttp:latest

How to access the tia Core WebUI:

After you have successfully executed the docker run command, you can access the WebUI via the web browser <http://<server>>:<port>

Please login with your combination of username (default:admin) + password

How to connect SAP to tia Core contentserver:

use the transaction code OAC0 to create the repository T1

specify the required connection information for your tia core contentserver

  1. perform the connection test → the result should be as following

  1. send out the sap certificate to the tia core contentserver

Congratulations, you are now able to use tia core for archiving documents via ArchiveLink (smile)

Configuration:

Docker command:

This parameter -v data_volume:/temp/data is only required when data are stored in /temp/data. When you plan to use other storages (like S3) you no not need these parameter. For different location modify repository.cfg and the command accordingly.

Environment Variables

CONFIGDIRECTORY

Directory where repository.cfg is expected. Default is “/application/config/“

LOGGING_LEVEL_ROOT

Log Level for core of tia. Default is “Debug”. Recommended for Production is “WARN” or “ERROR”.

LOGGING_CONFIG

Point to a log4j2 configuration to overwrite the default one

WEBAPP_SECURITY_AUTH_BASIC_PASSWORD

Set Password for Status Webapp with bcrypt. Password “admin” for testing: $2a$10$5E1KpGIKSq6xuWmGf92bheB17V0l4fEMnVmYPqhWiazKddcx1TF/e

TIA_LICENSE_PATH

Path to the license file (if different from /application/config/license/)

You can overwrite these with -e <key>=value

FAQ

Expand
titleI do not want log files inside my container (for tia® Content Server core < 2.6.0 )
Info

This is no longer required for tia® Content Server core 2.6.0 or higher

  • Use e.g this log4j2.xml without file appender

View file
namelog4j2.xml


Map it to the container with -v <Folder>/log4j2.xml:/application/config/log4j2.xml

And set environment variable for the container -e LOGGING_CONFIG=/application/config/log4j2.xml

Expand
titleI want to use ILM or SAPHTTP?

Both is available on Nexus/Harbor

Expand
titleI want to check the container logs

You can do that with the following command

Code Block
sudo docker container logs <container name / or / container-id>
Expand
titleIs respository.cfg shared?

In the example repository.cfg is shared when mutiple container use the same repository.cfg. Change one and restart container so that new repository.cfg works for both.

Expand
titleWhere is the tomcat?

Tomcat is now embedded and maintained by kgs.

Expand
titleHow do I update a container

Pull the new image sudo docker pull [docker_image]

Find the ID of the running container sudo docker ps

Stop Container sudo docker stop [container_id]
Remove Container sudo docker rm [container_id]

Start Container docker run -p 8080:8080 -v data_volume:/temp/ -v <Folder>/repository.cfg:/application/config/repository.cfg -d docker.kgs-software.com/tia/core/cmis:<Version>

Expand
titleAre there files or directories that need to be mapped in the container and need to be permanent with read/write access?

  • Yes, but it depends on your configuration.

    • tia® Content Server core requires a metadata directory (<repo>.configdata.filesystem.root)

    • tia® Content Server core can require a keystore, when you configure it, make sure this file is available for all

      • <repo>.keystoreservice.pkcs12.name

      • <repo>.keystoreservice.pkcs12.path

    • tia® Content Server core requires a temp directory to cache files it is /tmp there are only temporary files stored for short time.