Versions Compared

Old Version 17

changes.mady.by.user Chris Welford

Saved on

compared with

New Version Current

changes.mady.by.user Chris Welford

Saved on

Key

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

...

Change the owner and group of the release package to tomcat:phixflow:

Code Block
languagebash
chown phixflow-x.y.z-yyymmdd.zip tomcat:phixflow

...

Code Block
phixflow-x.y.z-yyyymmdd
phixflow-x.y.z-yyyymmdd/schemainstall
phixflow-x.y.z-yyyymmdd/webapps

...

Code Block
phixflow-x.y.z-yyyymmdd
phixflow-x.y.z-yyyymmdd/schemainstall
phixflow-x.y.z-yyyymmdd/webapps

Setting up the PhixFlow Database
Anchor
installingDatabase
installingDatabase

The schema installation has 4 main steps, regardless of platform:

...

Creating the database user is heavily dependent on the database platform, and will often have to be varied to meet local requirements regarding naming and security. These example commands will be adequate for basic installations.

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"


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


Populate the Database

Once you have created the database and/or database user, run the Installer to create the database tables and initial data.

...

Code Block
languagexml
<property name="url">
	<value>jdbc:oracle:thin:@[SERVER IP ADDRESS]:1521:[SID]<value>[CONNECTION STRING]</value>
</property>
<property name="username">
	<value>[USERNAME]</value>
</property>
<property name="password">
	<value>[PASSWORD]</value>
</property>

Connection Strings

See also Database URLs for  for how to specify connection string URLs for the various database platforms supported by PhixFlow.

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
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
jajdbc:mysql://hostname/phixflow

Configure phixflow-instance.xml

...

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

...