Page Comparison

tia Core tia® Content Server core has two main places for configuration:

• for application-wide settings

• for repository-wide settings

Application wide settings

Application-wide settings are made depending on the choosen type of deployment:

...

for

...

configuration

...

Example for environmental variables in a docker command:

docker run 
 [..]
 -e TIA_LICENSE_PATH=/application/config/tialic 
 -e WEBAPP_SECURITY_AUTH_BASIC_USERNAME=admin 
 -e WEBAPP_SECURITY_AUTH_BASIC_PASSWORD=\$2a\$10\$JKRQvv.bCNjlyLoBqORAq.79SlwpD8h9nWoo9ss35vt2Pi11KJ2B.
 [..]

• Java command line parameters: In a war-file deployment, the web application server is a Java application and therefore started by a java command line.

...

:

...

java -D"logging.config"="my.log4j2.xml" […]

...

...

• for

...

<?xml version="1.0" encoding="UTF-8"?> 
<!DOCTYPE Context> 
<Context>     
   <Parameter 
       name="logging.level.com.software.kgs"         
       value="info"
       override="true" />     
   <Parameter
       name="logging.config"
       value="C:/Program Files/tomcat/webapps/coreoftia/META-INF/my.log4j2.xml"
       override="true" /> 
</Context>

...

• application

...

• -

...

• wide settings

...

• for

...

By default,

• the file resides in containerized deployments /application/config/repository.cfg. It i best practice to use a volume mount in the container configuration:

...

• -

...

• For war deployments, find the repository.cfg here: <web server installation>/webapps/<context>/conf.

...

• wide settings

...

• configservice.class=file

• configDirectory=config

• configFile=repository.cfg

The parameter names in the repository.cfg file follow a hierarchical scheme. The format of parameters for services therefore follow this format:

<repository>.<service>.[etc]

For example:

...