Copy the PhixFlow Webapp into Tomcat
...
| 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.
...
| Anchor | ||||
|---|---|---|---|---|
|
Configure phixflow-login.xml
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.
Initially, simply copy the example file phixflow-login.xml.example to phixflow-login.xml.
Configure log4j.properties
The log4j.properties file controls detailed event/error logging on the server.
...
| Info |
|---|
| If it is ever necessary to change this file, those changes will take effect within a few seconds, without having to restart the Tomcat server. |
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:
...
| Code Block |
|---|
log4j.appender.myAppender.file=logs/ alternative_name.log |
...