Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 33 Next »

Available from Core of tia 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:

Prepare repository.cfg to map it to directory /application/config

  • place repository.cfg to in a folder

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

  • replace <Version> with a available version on nexus

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

Example:

docker run -p 8080:8080 -v data_volume:/temp/ -v C:/cmis/repository.cfg:/application/config/repository.cfg -d docker.kgs-software.com/tia/core/cmis:2.4.0

Configuration:

Docker command:

This parameter -v data_volume:/temp/ is only required when data are stored in /temp/. 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.

Environmane 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

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

FAQ

 I do not want log files inside my container (from core of tia <2.6.0 )

This is no longer required for tia Core 2.6.0 or higher

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


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

 I want to use ILM or SAPHTTP?

Both is available on Nexus/Harbor

 Where do I store the metadata.xml?

In the example repository.cfg the files are stored in /temp/meta. Make sure you map these data in a volume so that multiple started images can access the same data

 Is 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.

 Where is the tomcat?

Tomcat is now embedded and maintained by kgs.

 How 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>

 Are 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.

    • Core of tia requires a metadata directory (<repo>.configdata.filesystem.root)

    • Core of tia can require a keystore, when you configure it, make sure this file is available for all

      • <repo>.keystoreservice.pkcs12.name

      • <repo>.keystoreservice.pkcs12.path

    • Core of tia requires a temp directory to cache files it is /tmp there are only temporary files stored for short time.

  • No labels