Page Comparison

...

Web Application Context Name

Choose a desired web application context name and rename the downloaded .war file accordingly.

Example:

The downloaded .war- file is called tiaContentServer-saphttp-3.8.0.war. But the desired URL for accessing the Status UI is: https://1.2.3.4:8443/tiaCore-CS/info.

So Then the application context name is: tiaCore-CS

And To achieve this, the .war -file before deployment needs to must be renamed into as follows: tiaCore-CS.war.Step 2:

Configure

...

the configuration location

The Tomcat context file is a an XML file with the same name as the web application context name (respective the .war - file deployed. E.g. tiaCore-CS.xml) and is located in <tomcat installation>/conf/Catalina/localhost directory. For more information see Apache Tomcat documentation: https://tomcat.apache.org/tomcat-10.0-doc/config/context.html.

To access and edit the context file

...

shut down the app

...

Best practice Example:

Shut down Apache Tomcat
Navigate to <tomcat installation>/conf/Catalina/localhost directory
edit there the Create a file called like the application context name with .xml extension
navigate toC:/Program Files/Apache Software Foundation/Tomcat 10.1/conf
edit there a new folder license and put the license into the folder

take the logback-spring.xml and the repository.cfg and put it into the C:/Program Files/Apache Software Foundation/Tomcat 10.1/conf folder

View file

name	logback-spring.xml

View file

name	repository.cfg

Info
During the deployment the WAR file will be extracted and the default configuration will be available at `/WEB-INF/classes/config/repository.cfg` . In the context.xml the location of repository.cfg can be changed.

Note
The folder and file for `repository.cfg` as well as the key store configuration needs to be readable by tomcat process. Don't put these configuration inside an user folder of another user like your login user! Otherwise the app inside tomcat don't have access permissions and will not start.

...

e.g. tiaCore-CS.xml. The advantage of this procedure is that the web context and the configuration are not overwritten even if the .war file is updated, as long as the name of the .war file remains the same as before the update.

Example configuration of the context file e.g tiaCore-CS.xml:

Code Block

<?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/Apache Software Foundation/Tomcat 10.1/conf/logback-spring.xml"
        override="true" />
    <Parameter
        name="volumecounter.file.counterSender.targetUrl"
        value="https://vcrs.kgs-cloud.de"
        override="true" />
    <Parameter
        name="volumecounter.file.counterSender.isActive"
        value="true"
        override="true" />
    <Parameter
        name="volumecounter.file.counterSender.proxy.uri"
        value=<yourProxyURL>
        override="true" />
    <Parameter
        name="volumecounter.file.counterSender.proxy.user"
        value=<yourProxyUser>
        override="true" />
    <Parameter
        name="volumecounter.file.counterSender.proxy.password"
        value=<yourProxyPassword>
        override="true" />
    <Parameter
		name="configDirectory"
		value="C:/Program Files/Apache Software Foundation/Tomcat 10.1/conf/repository"
        override="true" />
	<Parameter
		name="configFile"
		value="repository.cfg"
        override="true" />
	<Parameter
        name="tia.license.path"
        value="C:/Program Files/Apache Software Foundation/Tomcat 10.1/conf/license"
        override="true" />
	<Parameter
		name="webapp.security.auth.type"
		value="basic"
        override="true" />
	<Parameter
		name="webapp.security.auth.basic.username"
		value="admin"
        override="true" />
	<Parameter
		name="webapp.security.auth.basic.password"
		value="$2a$10$eswhIo8VjEviekZxaq1FLukR7I59dEdHiLE.kGEINbfSjA1cZWjG2"
        override="true" />
</Context>

Navigate toC:/Program Files/Apache Software Foundation/Tomcat 10.1/conf
Create a new folder license and put the license into it

Take the logback-spring.xml and the repository.cfg and put it into the C:/Program Files/Apache Software Foundation/Tomcat 10.1/conf folder

View file
name logback-spring.xml

View file
name repository.cfg

Info
During the deployment the .war file will be extracted and the default configuration is available at `/WEB-INF/classes/config/repository.cfg` . In the context.xml the location of repository.cfg can be changed - see example above.

Note
The folder and file for `repository.cfg` as well as a key store configuration, if any, needs to be readable by tomcat process. Don't put these configuration inside a user folder of another user like your login user! otherwise the webapp within tomcat does not have the access permission and will not start.

restart the the Tomcat Service

...

WAR file deployment

Choose the tiaCore-CS.war -file and deploy it into the webapps folder of the Apache Tomcat installation:

...

After this step the tomcat should deploy and create a folder in its webapps directory as well show the app in the application section of the manager.

Image ModifiedStep 4:

Apache Tomcat Manager App

Open the Tomcat configuration page and go to “Manager App”Click on the Manager App button.

...

Verify Installation

Apache Tomcat Manager App

Choose the deployed .war - file from tomcat manager e. g. /tiaCore-CS.

...

The base URL of the deployed application should forward to the web console, which looks like thissuccessfully installed tiaCore-CS now presents the UI of tia core:

Versions Compared

Old Version 23

New Version 24

Key

Web Application Context Name

Configure

the configuration location

WAR file deployment

Apache Tomcat Manager App

Apache Tomcat Manager App