Deployment using Container (tC)
Preparing container runtime
Read more here: https://kgs-software.atlassian.net/wiki/spaces/DOCUEN/pages/4034854915
Deploying tia Content Server Core
Deploying tia Core requires the following:
A license file. This file is provided by kgs Customer Support.
repository.cfgfile. A defaultrepository.cfgfile is attached below, which is suitable for test systems only. For repository configuration settings refer to https://kgs-software.atlassian.net/wiki/spaces/DOCUEN/pages/2749104148.
Example of a repository.cfg file:
In addition, decide about and prepare these settings depending on your requirements in order to run the container.
| Placeholder name to be replaced | Mapping to container-configuration | Explanation |
|---|---|---|---|
| <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. |
| <Hostport> |
| <Hostport>: Listener port on host that forwards to the listener port in the container, which is configured by |
| <Config Folder> |
| The folder location on host system where the |
| <License Folder> |
| The location on host system where the license file resides. For more information refer to https://kgs-software.atlassian.net/wiki/spaces/DOCUEN/pages/2726854657 . |
| <Temp Folder> |
| Optional: Mapping container’s |
| <Loglevel> |
| The log level sets the verboseness of the log writing. Valid are: |
| <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 https://kgs-software.atlassian.net/wiki/spaces/DOCUEN/pages/2740158485 . |
|
|
| Run as daemon in background |
| <Image> |
| Referencing the image as last parameter in the The image is referenced like this:
with <Product>: The tia Core product to be deployed: <Version>: The version of tia Core to be deployed. kgs recommends to use the latest available version. For this use |
For information about the container environmental variables, refer to https://kgs-software.atlassian.net/wiki/spaces/DOCUEN/pages/2753986751
When host is running Windows, pay attention to the volume mappings. The host volume path contains drive letter with colon ( : ) and backslashes ( \ ). Use quotation marks and double the backslash to allow correct interpretation.
Example volume mapping: "G:\\host\\location":/container/location
For example deployments see: