...
Change the owner and group of the release package to tomcat:phixflow:
| Code Block | ||
|---|---|---|
| ||
chown phixflow-x.y.z-yyymmdd.zip tomcat:phixflow |
Switch to the tomcat user (makes sure that login scripts are run. The syntax for this may vary between operating systems:
| Code Block | ||
|---|---|---|
| ||
su -l tomcat |
Change back to the release directory and unzip / unpack the release:
| Code Block | ||
|---|---|---|
| ||
unzip phixflow-x.y.z-yyyymmdd.zip |
This will create a release directories like:
| Code Block |
|---|
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.
| Code Block |
|---|
phixflow-x.y.z-yyyymmdd |
...
phixflow-x.y.z-yyyymmdd/schema |
...
phixflow-x.y.z-yyyymmdd/webapps |
Setting up the PhixFlow Database
...
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.:
| Code Block | ||
|---|---|---|
| ||
<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 Database URLs for how to specify URLs for the database platforms supported by PhixFlow.
...
In such a configuration, set the instance name and id for each PhixFlow webapp instance to unique values and set leaderOnStartup to “true” for an instance if it should become active immediately on startup.
e.g.:
| Code Block |
|---|
|
<!-- The instance name must be different for each member of the cluster -->
...