Info |
---|
Available from tia® Content Server core Version 2.1.0 |
Public Access (RELEASE TAG) :
...
Preparing container runtime
Deploying software as containers requires a container runtime. This documentation provides the required information. It also provides examples for docker container runtime.
Installation of docker or another container runtime following Open Container Initiative (OCI) standard is prerequisite for deploying tia Core as container.
Images for deployment of tia Core are stored at https://images.docker.kgs-cloud.deLogin to kgs harbour with .
An account is required. It is provided for licensed installations via kgs Customer Support.
Info |
---|
On this image hub images are available no older than tia® Content Server core Version 2.1.0. |
Example preparation with docker container runtime:
docker login https://images.docker.kgs-cloud.de
docker 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
Deploying tia Core
Deploying tia Core requires the following:
repository.cfg
file. A defaultrepository.cfg
file is attaches below, which is suitable for test systems only. For repository configuration settings refer to Repository-wide settings.license file. This file is provided by kgs.
View file | ||
---|---|---|
|
place repository.cfg to in a folder
replace <Name> with your custom name for the tia core container (application context name).
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
...
In addition, decide about these settings depending on your requirements:
<Name> : Give the tia Core container a custom name. This name is also the application context name.
<Hostport> : Listener port on host that forwards to the <Containerport>.
<Containerport> : Listener port on the container. This is always
8080
.<Folder> : The location on host system where the
repository.cfg
resides.<License folder> : The location on host system where the license file resides. For more information refer to Location of the license file .
<Loglevel> : The log level sets the verboseness of the log writing. Valid are:
OFF
;ERROR
;WARN
;INFO
orDEBUG.
It is recommended to useERROR
orWARN
in production environments andWARN
orINFO
in test systems. SetDEBUG
level only when being ask be kgs Customer Support. For more information on logging refer to Logging .<BcryptHash> : To login to the tia Status UI, a password is required that when being hashed must match this value. For more information refer to tia® Status UI Authentication .
<Product> : The tia Core product to be deployed:
saphttp
,cmis
<Version> : The version of tia Core to be deployed. kgs recommends to use the latest available version. For this use
latest
.
Fill in the values into the docker run command below:
Code Block |
---|
docker run --name <Name> -p 8080<Hostport>:8080<Containerport> -v data_volume:/temp/data -v <License <License>folder>:/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><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 the container has successfully started und is running, access the Status UI via the web browser <httphttp://<server>><hostserver>:<port><hostport>
Please login Login with your combination of username (default:admin) + password
...