...
| Code Block | ||
|---|---|---|
| ||
<property name="url"> <value>[CONNECTION STRING]</value> </property> <property name="username"> <value>[USERNAME]</value> </property> <property name="password"> <value>[PASSWORD]</value> </property> |
Connection Strings
See also The connection strings given here should cover most cases of connecting to PhixFlow's own database. For more details, see Database URLs for how to specify connection string URLs connection strings are constructed for the various database platforms supported by PhixFlow.
...
| Code Block |
|---|
jdbc:oracle:thin:@hostname:1521:phixflow |
Oracle (for containerised instances> 12c with PDB containers):
| 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 |
...