Deployment using Container (tC)

Owned by Stefan Franz
Last updated: Oct 30, 2024 by Armin Franke
5 min read

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

An account is required. It is provided for licensed installations via kgs Customer Support.

Images that are no longer supported will be removed without further notice.

Example preparation with docker container runtime:

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

Docker will prompt for user and password.

 

Deploying tia Core

 

Deploying tia Core requires the following:

  • A license file. This file is provided by kgs Customer Support.

 

In addition, decide about and prepare these settings depending on your requirements in order to run the container.

docker run parameter

Placeholder name to be replaced

Mapping to container-configuration

Explanation

docker run parameter

Placeholder name to be replaced

Mapping to container-configuration

Explanation

--name

<Name>

 

Give the tia Core container a custom name. This name is also the application context name.

Hint: You can start multiple instances of the same containers with different ports and different names.

-p

<Hostport>

SERVER_PORT

<Hostport>: Listener port on host that forwards to the listener port in the container, which is configured by server.port application-wide setting (default: 8080).

-v

<Config Folder>

/application/config

The folder location on host system where the repository.cfg resides.

-v

<License Folder>

/application/config/license/

The location on host system where the license file resides. For more information refer to Location of the license file .

-v

<Temp Folder>

/temp/data

Optional: Mapping container’s temp directory to host file system.

-e

<Loglevel>

LOGGING_LEVEL_ROOT

The log level sets the verboseness of the log writing. Valid are: OFF; ERROR; WARN; INFO orDEBUG.It is recommended to use ERROR or WARN in production environments and WARN or INFO in test systems. Set DEBUG level only when being ask be kgs Customer Support. For more information on logging refer to Logging .

-e

<BcryptHash>

WEBAPP_SECURITY_AUTH_BASIC_PASSWORD

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 .

-d

 

 

Run as daemon in background

 

<Image>

 

Referencing the image as last parameter in the docker command.

The image is referenced like this:

images.docker.kgs-cloud.de/tia/core/<Product>:<Version>

with

<Product>: The tia Core product to be deployed: saphttp , cmis, or ilm.

<Version>: The version of tia Core to be deployed. kgs recommends to use the latest available version. For this use latest.

For information about the container environmental variables, refer to Reference of application-wide parameters

 

 

For example deployments see: