...

...

Step1  Copy the PhixFlow Webapp into Tomcat

To install the PhixFlow web application into Tomcat:

Copy $RELEASE/webapps/phixflow to $TOMCAT/webapps/phixflow

Configure the Webapp

...

Step 2  Create Configuration Files

Copy the following example configuration files and, where required, update them for your system.

...

phixflow-datasource.xml

The PhixFlow webapp must be configured to give access to the database user that has been you have created to hold the PhixFlow data.

1. Copy phixflow-datasource.xml.<database>.example to phixflow-datasource.xml

...

1. .
2. Edit

...

1. phixflow-datasource.xml and find the section <bean id="dataSource"...

...

1. which includes:

<property name="url">
	<value>[CONNECTION STRING]<<value>CONNECTION-STRING</value>
</property>
<property name="username">
	<value>[USERNAME]<<value>USERNAME</value>
</property>
<property name="password">
	<value>[PASSWORD]<<value>PASSWORD</value>
</property>

Connection Strings

The connection strings given here should 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.

The platform-specific [CONNECTION STRING]s are:

Oracle:

...

3. Replace the temporary values with:

• USERNAME: the database user's name.
• PASSWORD: the database user's password.
• CONNECTION-STRING: this depends on the database platform, and is one of: 

Oracle:  jdbc:oracle:thin:@hostname:1521:phixflow

Oracle (> 12c with PDB containers):

...

   jdbc:oracle:thin:@hostname:1521/phixflow

SQL Server:

...

   jdbc:sqlserver://hostname\myservice;databaseName=phixflow

MySQL:

...

   jdbc:mysql://hostname/phixflow

...

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

Copy the example file phixflow-instance.xml.example to phixflow-instance.xml

...

.

phixflow-instance.xml identifies the webapp instance in a resilient configuration and sets whether the instance is active on startup.

...

phixflow-

...

login.xml

...

Anchor
phixflowDomainsXmlInstall phixflowDomainsXmlInstall

Copy the example file phixflow-

...

login.xml.

...

example to phixflow-login.xml

...

.

You will use this file if you need to configure PhixFlow to authenticate users’ usernames and passwords against an external

...

domain, or Active Directory, or a SAML Single Sign-on server

...

, such as the Active Directory Federation Services server.

...

Initially, simply copy the example file phixflow-login.xml.example to phixflow-login.xml.

See also Configure Login Forms.

...

For more information, see the pages in the User Administration topic.

logback.xml 

Anchor
logback logback

Copy the example file logback.xml.example to logback.xml.

The logback.xml file controls detailed event/error logging on the server.

...

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.

...

You only need to change this file:

• to rename the log file if you have multiple PhixFlow instances; see Renaming the Log File, below.
• as requested by PhixFlow Support.

If you want to integrate this into other logging frameworks

...

, such as Google Cloud's stackdriver

...

It is not normally necessary to make any further changes to this file unless so instructed by PhixFlow Support.

...

, please contact support@phixflow.com.

...

phixflow-logging.xml 

Anchor
phixflow-log phixflow-log

Copy the example file phixflow-logging.xml.example to 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-logging.xml.example to phixflow-logging.xml.

...

You only need to change this file as requested by PhixFlow Support.

Using Your own Logo in PhixFlow

Optionally, you can configure PhixFlow to display your own company logo.

...

The logo must be a vector graphic .svg file

...

with the name customerLogo.svg (case sensitive). Add the file to  $TOMCAT/webapps/phixflow/gui/images/

Step 3  Restart Tomcat

Whenever you make changes in $TOMCAT/webapps/phixflow, remember to restart Tomcat, so that the changes are used.

Multiple PhixFlow Webapps

To install multiple instances of PhixFlow on a single server, complete the installation steps above to create a first PhixFlow instance. Then install a further instance:

1. Create a second database user to hold the data for the new instance.
2. Copy the PhixFlow web application into the Tomcat again:

cp $RELEASE/webapps/phixflow to $TOMCAT/webapps/mywebappMYWEBAPP

where “mywebapp” MYWEBAPP is the name of your test systemnew instance.

For phixflow-datasource.xml

...

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

...

Renaming the Log File

Anchor
renamingLogFile renamingLogFile

By For logback.xml, by default, the settings in this file will send messages from all phixflow webapps to the same log file (phixflow.log); . When you have multiple instances, this can be confusing as it may not be . It is not clear which webapp has generated which messages, and for this reason we recommend that when installing . For multiple PhixFlow webapps in the same tomcatTomcat, we recommend that you change each webapp to log to into a separate log file, thus:

This example shows

.

For each instance, edit the logback.xml file and change the instance name to something unique. The following example uses the name "mywebapp":

• on line 3: messages are re-directed initially to logs/mywebapp.log
• on line 6: messages re-directed after daily rollover to logs/mywebapp.yyyy-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>
...

...