...
This will create a release directories like:
phixflow-x.y.z-yyyymmdd
phixflow-x.y.z-yyyymmdd/schema
phixflow-x.y.z-yyyymmdd/webapps
Windows
Unzip the release package using WINZIP or similar.
phixflow-x.y.z-yyyymmdd
phixflow-x.y.z-yyyymmdd/schema
phixflow-x.y.z-yyyymmdd/webapps
Setting up the PhixFlow Database
...
Creating the database tables is the same regardless of platform, varying only in the URL used to reference the database.
cmd> java -jar ../../../bin/installer.jar
-url=jdbc:oracle:thin:@localhost:1521:cview -user=myuser -pass=mypass –install
See the appendices for how to specify URLs for the database platforms supported by PhixFlow.
...
Database | Create initial data |
Oracle: | cmd> sqlplus myuser/mypass @populate_schema.sql |
Sql Server: | cmd> sqlcmd -S hostname\myservice -i populate_schema.sql -v dbName="cview" |
MySQL: | cmd> mysql --user=root –-password mysql> exit; |
Set the Customer Name in the Database
...
Database | Create initial data |
Oracle: | cmd> sqlplus myuser/mypass |
Sql Server: | cmd> sqlcmd -S hostname\myservice –d cview |
MySQL: | cmd> mysql --user=root –-password –database=cview mysql> exit; |
...
Install the Webapp in the Tomcat application server
...
To install the PhixFlow web application into Tomcat:
Copy $RELEASE/webapps/phixflow to $TOMCAT/webapps/phixflow
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.
In In $TOMCAT/webapps/phixflow/WEB-INF/classes, copy phixflow-datasource.xml.<database>.example to phixflow-datasource.xml and edit the properties for <bean id="dataSource"...., e.g.:
<property name="url">
<value>jdbc:oracle:thin:@[SERVER IP ADDRESS]:1521:[SID]</value>
</property>
<property name="username">
<value>[USERNAME]</value>
</property>
<property name="password">
<value>[PASSWORD]</value>
</property>
See the appendices for how to specify URLs for the database platforms supported by PhixFlow.
...
<bean id="clusterInstance"
class="com.accipia.phixflow.service.cluster.main.ClusterInstance"
...
p:name="MAIN"
...
p:id=”1”
...
p:leaderOnStartup="true"
...
/>
See the appendices for more information on setting up a resilient configuration.
...
In $TOMCAT/webapps/phixflow/WEB-INF/classes, copy phixflow-email.xml.example to phixflow-email.xml and edit the properties for <bean id="emailConfiguration"...., e.g.:
...
<p:enabled="true">
<p:port="110">
<p:host="pop.your-mail-server.com">
<p:protocol="pop3">
<p:username="your username">
<p:password="your password">
Note that setting the enabled property to true will mean PhixFlow will poll the configured email server for incoming emails. Leave this value set to false if you do not require PhixFlow to process incoming emails.
...