...
...
...
Configure the Webapp
...
...
...
...
...
...
...
Code Block | ||
---|---|---|
| ||
<property name="url">
|
...
<value>CONNECTION-STRING</value> </property> <property name="username"> |
...
<value>ALIAS-USERNAME</value> </property> <property name="password"> |
...
<value>ALIAS-PASSWORD</value> </property> |
Connection Strings
The connection strings given here should cover most cases of connecting to PhixFlow's own database. For information about how connection strings are constructed for the various database platforms supported by PhixFlow, see Database URLs.
The platform-specific [CONNECTION STRING]s are:
Oracle:
4. Replace the temporary values with:
- USERNAME: the database user's name.
- PASSWORD: the database user's password.
- CONNECTION-STRING: this depends on the database platform, and is one of:
Oracle: jdbc:oracle:thin:@hostname:1521:phixflow
Oracle (> 12c with PDB containers):
...
jdbc:oracle:thin:@hostname:1521/phixflow
SQL Server:
...
jdbc:sqlserver://hostname\myservice;databaseName=phixflow
MySQL:
MariaDB: jdbc:mariadb://
...
localhost/phixflow
Configure phixflow-instance.xml
phixflow-instance.xml identifies the webapp instance in a resilient configuration and sets whether the instance is active on startup.
...
These strings cover most cases of connecting to PhixFlow's own database. For information about how connection strings are constructed for the various database platforms supported by PhixFlow; see Database URLs.
phixflow-secret.xml
If you have not already done so Configure a Keystore for Database Credentials. Use phixflow-secret.xml to specify the keystore details.
phixflow-login.xml
Anchor | ||||
---|---|---|---|---|
|
Copy the example file phixflow-login.xml.example
to phixflow-
...
login.xml
.
...
Configure phixflow-login.xml
...
You will use this file if you need to configure PhixFlow to authenticate users’ usernames and passwords against an external
...
domain, or Active Directory, or a SAML Single Sign-on server
...
, such as the Active Directory Federation Services server. For more information, see the pages in the User Administration topic.
logback.
...
xml
Anchor | ||||
---|---|---|---|---|
|
Copy the example file logback.xml.example
to
...
logback.xml
...
.
...
The logback.xml
file controls detailed event/error logging on the server.
...
The phixflow-logging.xml file contains the location of the main log file directory, used when downloading log files from the front end.
To configure for default logging:
...
You only need to change this file:
- to rename the log file if you have multiple PhixFlow instances; see Renaming the Log File, below.
- to change the logging level when troubleshooting; see Server Log Files
- as requested by PhixFlow Support.
Tip |
---|
Changes to logback.xml take effect within a one or two minutes. You do not need to restart the Tomcat servlet. |
phixflow-logging.xml
Anchor | ||||
---|---|---|---|---|
|
Copy the example file phixflow-logging.xml.example
to phixflow-logging.xml
.
...
The phixflow-logging.xml
...
It is not necessary to make any further changes to these files unless so instructed by PhixFlow Support.
...
file contains a list of directories that contain log files, and is used when downloading log files from the GUI. You only need to change this file as requested by PhixFlow Support.
Using Your own Logo in PhixFlow
Optionally, you can configure PhixFlow to display your own company logo.
...
The logo must be a vector graphic .svg file
...
with the name customerLogo.svg
(case sensitive). Add the file to $TOMCAT/webapps/phixflow/
gui/images/
Step 3 Restart Tomcat
Whenever you make changes in $TOMCAT/webapps/phixflow
, remember to restart Tomcat, so that the changes are used.
Multiple PhixFlow Webapps
Anchor | ||||
---|---|---|---|---|
|
To install multiple instances of PhixFlow on a single server, complete the installation steps above to create a first PhixFlow instance. Then install a further instance:
- Create a second database user to hold the data for the new instance.
- Copy the PhixFlow web application into the Tomcat again:
Code Block |
---|
cp $RELEASE/webapps/phixflow to $TOMCAT/webapps/ |
...
<mywebapp> |
where
...
<mywebapp>
is the name of your
...
new instance.
...
Remember to set up a separate user and schema in the database for the new PhixFlow instance and to
...
configure phixflow-datasource.xml
...
with the user, password and connection-string.
Renaming the Log File
For logback.xml, by default, the settings send messages from all PhixFlow webapps to the same log file, phixflow.log. When you have multiple instances, it is not clear which webapp has generated the messages. In this case, we recommend that you change each webapp to log into a separate log file.
For each instance, edit the logback.xml file and change the instance name to something unique. The following example uses the name mywebapp
:
- on line 3: messages are re-directed initially to
logs/mywebapp.log
- on line 6: messages re-directed after daily rollover to
logs/mywebapp.yyyy-MM-dd.log
.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
...
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>logs/mywebapp.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<!-- daily rollover -->
<fileNamePattern>logs/mywebapp.%d{yyyy-MM-dd}.log</fileNamePattern>
<maxHistory>30</maxHistory>
</rollingPolicy>
<encoder>
<pattern>%date %level [%thread] %logger{10} [%file:%line] %msg%n</pattern>
</encoder>
</appender>
... |