...
Change the owner and group of the release package to tomcat:phixflow:
Code Block | ||
---|---|---|
| ||
chown phixflow-x.y.z-yyymmdd.zip tomcat:phixflow |
...
Code Block |
---|
phixflow-x.y.z-yyyymmdd phixflow-x.y.z-yyyymmdd/schema phixflow-x.y.z-yyyymmdd/webapps |
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 |
---|
cd $RELEASE/phixflow-x.y.z-yyyymmdd/install |
Oracle:
Code Block |
---|
java -jar bin/installer.jar -url="jdbc:oracle:thin:@hostname@localhost:1521:phixflow |
...
" -user=myuser -pass=mypass -install -customer="Your Customer Name" |
SQL Server:
Code Block |
---|
jdbc:oracle:thin:@hostname:1521/phixflow |
Info |
---|
The only difference between the connection strings is to 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). |
SQL Server:
Code Block |
---|
java -jar bin/installer.jar -url="jdbc:sqlserver://hostnamemyhost\myservicemyserver;databaseNamedatabase=phixflow" -user=myuser -pass=mypass -install -customer="Your Customer Name" |
MySQL:
Code Block |
---|
java -jar bin/installer.jar -url="jdbc:mysql://hostnamelocalhost/phixflow" -user=myuser -pass=mypass -install -customer="Your Customer Name" |
Further information on the installer
...
See also Database URLs for how to specify connection string URLs for the various database platforms supported by PhixFlow.
Once you have created the database and/or database user, run the Installer to create the database tables and initial data.
The customer name in the commands below must exactly match the customer name used by PhixFlow Support to generate licence files. This argument (–customer="Your Customer Name") is optional, but without a valid customer name and matching licence key you will not be able to run any tasks in PhixFlow.
Code Block |
---|
cd $RELEASE/phixflow-x.y.z-yyyymmdd/install
|
Oracle:
Code Block |
---|
java -jar bin/installer.jar -url="jdbc:oracle:thin:@localhost:1521:phixflow" -user=myuser -pass=mypass -install -customer="Your Customer Name" |
SQL Server:
Code Block |
---|
java -jar bin/installer.jar -url="jdbc:sqlserver://myhost\myserver;database=phixflow" -user=myuser -pass=mypass -install -customer="Your Customer Name" |
MySQL:
...
The platform-specific [CONNECTION STRING]s are:
Oracle:
Code Block |
---|
jdbc:oracle:thin:@hostname:1521:phixflow |
Oracle (for containerised instances):
Code Block |
---|
jdbc:oracle:thin:@hostname:1521/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 |
---|
jajdbc:mysql://hostname/phixflow |
Configure phixflow-instance.xml
...
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
...