Copy the PhixFlow Webapp into Tomcat
...
Initially, simply copy the example file phixflow-login.xml.example to phixflow-login.xml.
Configure logback
...
.xml
| Anchor | ||||
|---|---|---|---|---|
|
The logback.xml file controls detailed event/error logging on the server.
The phixflow-logging.xml file contains the location of the main log file directory, used when downloading log files from the front end.
To configure for default logging:
...
Initially, simply copy the example file logback.xml.example to logback.xml.
For instructions on how to change the name of the log file generated, see below.
Please contact PhixFlow Support for instructions on how to integrate this into other logging frameworks (e.g. Google Cloud's stackdriver).
It is not normally necessary to make any further changes to these files this file unless so instructed by PhixFlow Support.
| Info |
|---|
| If it is ever necessary to change the logback.xml, those changes will take effect within a minute or so, without having to restart the Tomcat server. |
Configure phixflow-logging.xml
The phixflow-logging.xml file contains a list of directories that contain log files, and is used when downloading log files from the GUI.
Initially, simply copy the example file phixflow-login.xml.example to phixflow-login.xml.
It is not necessary to make any further changes to this file unless so instructed by PhixFlow Support.
Using Your own Logo in PhixFlow
Optionally, you can configure PhixFlow to display your own company logo. You need a vector graphic .svg file of your logo, renamed as customerLogo.svg (case sensitive). Add the file to $TOMCAT/webapps/phixflow/gui/images/
...
| Code Block |
|---|
cp $RELEASE/webapps/phixflow to $TOMCAT/webapps/alternative_namemywebapp |
where
...
“mywebapp” is the name of your test system.
phixflow-datasource.xml
Be sure to set up a separate user and schema in the database for the new PhixFlow instance and to set phixflow-datasource.xml as needed
...
.
logback.xml
| Anchor | ||||
|---|---|---|---|---|
|
My default, the settings in this file will send messages from all phixflow webapps to the same log file (phixflow.log); this can be confusing as it may not be clear which webapp has generated which messages, and for this reason we recommend that when installing multiple PhixFlow webapps in the same tomcat, you change each webapp to log to a separate log file, thus:
This example shows messages re-directed to mywebapp.log (and after daily rollover to mywebapp.yyyy-MM-dd.log).
| Code Block | ||||
|---|---|---|---|---|
| ||||
...
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>logs/mywebapp.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<!-- daily rollover -->
<fileNamePattern>logs/mywebapp.%d{yyyy-MM-dd}.log</fileNamePattern>
<maxHistory>30</maxHistory>
</rollingPolicy>
<encoder>
<pattern>%date %level [%thread] %logger{10} [%file:%line] %msg%n</pattern>
</encoder>
</appender>
... |