PhixFlow Help
Install PhixFlow Webapp
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.
All template and configured configuration files are in $TOMCAT/webapps/$WEBAPP/WEB-INF/classes
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.
copy phixflow-datasource.xml.<database>.example to phixflow-datasource.xml, then
edit the properties for <bean id="dataSource"...., e.g.:
<property name="url"> <value>[CONNECTION STRING]</value> </property> <property name="username"> <value>[USERNAME]</value> </property> <property name="password"> <value>[PASSWORD]</value> </property>
Connection Strings
The connection strings given here should cover most cases of connecting to PhixFlow's own database. For more details, see Database URLs for how connection strings are constructed for the various database platforms supported by PhixFlow.
The platform-specific [CONNECTION STRING]s are:
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
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-domains.xml
The PhixFlow webapp can be configured to authenticate users’ usernames and passwords against an external Domain / Active Directory server.
Initially, simply copy the example file provided.
For more information on how to configure for domain logins, see the PhixFlow Active Directory Guide.
Configure log4j.properties
The log4j.properties file controls detailed event/error logging on the server.
To configure for default logging:
- Open or cd to $TOMCAT/webapps/phixflow/WEB-INF/classes
- Copy log4j.properties.example to log4j.properties
It is not necessary to make any changes to this file unless so instructed by PhixFlow Support.
Multiple PhixFlow instances
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:
- Create a second database user to hold the data for the new instance.
- Copy the PhixFlow web application into the Tomcat again:
cp $RELEASE/webapps/phixflow to $TOMCAT/webapps/alternative_name
where “alternative_name” is the name of your test system.
- 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
- To ensure log messages are sent to a separate file, change the following line in log4j.properties
log4j.appender.myAppender.file=logs/ alternative_name.log
Please let us know if we could improve this page feedback@phixflow.com