Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Switch to the tomcat user (makes sure that login scripts are run. The syntax for this may vary between operating systems:

Code Block
languagebash
susudo -i -lu tomcat

Change back to the release directory and unzip / unpack the release:

Code Block
languagebash
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
installingDatabase
installingDatabase

...

Platform

Create the database user

Oracle:

This command will prompt for the name of the user to be created.

Code Block
sqlplus SYS/SYSPassword@SID as SYSDBA @schema/oracle/install/create_user


Sql Server:

This command requires the user, the password, the login and the database to be provided as parameters.

Code Block
sqlcmd -S localhost\myservice -i schema/sql_server/install/create_database_and_user.sql -v dbName="phixflow" dbLogin="phixflow" dbUser="phixflow" dbPassword="mypass"
If you are installing PhixFlow on SQLServer locally and you have followed the standard installation process above, then no Server Specification (the '-S' modifier on the SQLCMD) is required


MySQL:

Start a session the database:

Code Block
mysql --user=myrootuser --password

Create the user, supplying the name of the database, the user and the password in the commands below:

Code Block
create database phixflow
    CHARACTER SET = 'utf8'
    COLLATE = 'utf8_bin';
grant all privileges on phixflow.* to 'myuser'@'%' identified by 'mypass';
exit


...

Panel
bgColor#e6f0ff
titleBGColor#99c2ff
titleOracle PDB containers

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:

USE_SID_AS_SERVICE_listener

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
phixflowDomainsXmlInstall
phixflowDomainsXmlInstall

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

...

Find the line containing the call to window.open and change the 2nd parameter from ‘PhixFlow’ to ‘alternative_name’