Step 1  Copy the PhixFlow Webapp into Tomcat

...

These strings cover most cases of connecting to PhixFlow's own database. For information about how connection strings are constructed for the various database platforms supported by PhixFlow; see Database URLs.

phixflow-secret.xml

If you have not already done so Configure a Keystore for Database Credentials. Use phixflow-secret.xml to specify the keystore details.

phixflow-login.xml

Anchor
phixflowDomainsXmlInstall phixflowDomainsXmlInstall

...

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/

...

For each instance, edit the logback.xml file and change all occurrences of the instance name to something unique. 

The following example uses the name mywebapp:

• on line 3: messages  messages are re-directed initially to logs/mywebapp.logon line 6: messages and logs/mysebapp-security.log
•  messages re-directed after daily rollover to logs/mywebapp.yyyy-MM-dd.log and logs/mywebapp-security.yyy-MM-dd.log.

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

...