...
Copy the PhixFlow release package with a name matching phixflow-x.y.z-yyyymmdd.zip to the release area $RELEASE on the server. By default $RELEASE is at [c:]/opt/phixflow/release.
Unix
Style |
---|
.myPanelClass {
background-color: #800080 !important;
color: #800080 !important;
} |
Div | ||||
---|---|---|---|---|
| ||||
|
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 | ||
---|---|---|
| ||
susudo -i -lu tomcat |
Change back to the release directory and unzip / unpack the release:
Code Block | ||
---|---|---|
| ||
unzip phixflow-x.y.z-yyyymmdd.zip |
...
Windows
Unzip the release package using WINZIP or similar.
Release contents
On both linux and windows this will create a release directories likewith the following contents:
Code Block |
---|
phixflow-x.y.z-yyyymmdd phixflow-x.y.z-yyyymmdd/schemainstall 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/webappsREADME.txt |
Setting up the PhixFlow Database
Anchor | ||||
---|---|---|---|---|
|
The schema installation has 4 main steps, regardless of platform:
...
Platform | Create the database user | ||||
Oracle: | This command will prompt for the name of the user to be created.
| ||||
Sql Server: | This command requires the user, the password, the login and the database to be provided as parameters.
| ||||
MySQL: | Start a session the database:
Create the user, supplying the name of the database, the user and the password in the commands below:
|
...
Code Block |
---|
jdbc:oracle:thin:@hostname:1521/:phixflow |
Oracle (for containerised instances):
Code Block |
---|
jdbc:oracle:thin:@hostname:1521:phixflow |
/phixflow |
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
For Oracle 12c and above, you should use a '/' instead of ':' before [SID], so that [SID] is treated as a SERVICE name rather than an SID. This is due to Oracle 12c introducing pluggable databases (PDB's). There is also the option to add the line 'USE_SID_AS_SERVICE_listener=on' to the tnsnames.ora Oracle configuration file in order to treat SID's as service names by default. This is provided by Oracle as a workaround for users who have hard-coded connection strings that are difficult to change by hand, and so should not be necessary for phixflow configuration. For more information, please see the following Oracle documentation links: Introduction to the Multitenant Architecture (including an explanation of PDB's) |
...
SQL Server:
Code Block |
---|
jdbc:sqlserver://hostname\myservice;databaseName=phixflow |
MySQL:
Code Block |
---|
jajdbcjdbc:mysql://hostname/phixflow |
...
See Configuring for Resilience for more information.
Anchor | ||||
---|---|---|---|---|
|
Configure phixflow-domains.xml
...
For more information on how to configure for domain logins, see the PhixFlow ActiveDirectory Configuration userguidethe PhixFlow Active Directory Guide.
Configure log4j.properties
...