...
...
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
A number of configuration files must be copied from supplied templates and configured.
Info |
---|
All template and configured configuration files are in |
Configure phixflow-datasource.xml
The PhixFlow webapp must be configured to give access to the database user that has been created to hold the PhixFlow data. The actual username and password are stored in an encrypted keystore; see Configure a Keystore for Database Credentials
...
Code Block | ||
---|---|---|
| ||
<property name="url"> <value>[CONNECTION STRING]</value> </property> <property name="username"> <value>[ALIAS-USERNAME]</value> </property> <property name="password"> <value>[ALIAS-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.
...
Code Block |
---|
jdbc:mysql://hostname/phixflow |
Configure phixflow-instance.xml
phixflow-instance.xml identifies the webapp instance in a resilient configuration and sets whether the instance is active on startup.
Initially, simply copy the example file phixflow-instance.xml.example to phixflow-instance.xml.
Configure phixflow-login.xml
Anchor | ||||
---|---|---|---|---|
|
The PhixFlow webapp can be configured to authenticate users’ usernames and passwords against an external Domain / Active Directory or SAML Single Sign-on server e.g. Active Directory Federation Services server.
...
See also Configure Login Forms.
Configure logback.xml
Anchor | ||||
---|---|---|---|---|
|
The logback.xml file controls detailed event/error logging on the server.
...
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
Anchor | ||||
---|---|---|---|---|
|
The phixflow-logging.xml file contains a list of directories that contain log files, and is used when downloading log files from the GUI.
...
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/
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:
...
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 | ||||
---|---|---|---|---|
|
By 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:
...