...
Copy the PhixFlow release package with a name matching phixflow-x.y.z-yyyymmdd.zip to the release area $RELEASE on the server. By default $RELEASE is at [c:]/opt/phixflow/release.
Unix
| Style |
|---|
.myPanelClass {
background-color: #800080 !important;
color: #800080 !important;
} |
| Div | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| |||||||||
|
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 |
|---|
jdbc:oracle:thin:@hostname:1521:phixflow |
| Panel | ||||
|---|---|---|---|---|
| ||||
For Oracle, 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) |
...
Find the line containing the call to window.open and change the 2nd parameter from ‘PhixFlow’ to ‘alternative_name’