TIBCO Spotfire Server 3.2.2 - TIBCO Product Documentation

Technical Reference
[domain_realm]
.research.example.com = RESEARCH.EXAMPLE.COM
research.example.com = RESEARCH.EXAMPLE.COM
[appdefaults]
autologin = true
forward = true
forwardable = true
encrypt = true
11.4 Database Connection Configuration
The Spotfire database, discussed previously in this manual, holds information
important to the Spotfire Servers. When logging into the configuration console for the
first time, a prompt will appear asking for a valid URL to the database. The
information entered here is stored by the configuration console and then distributed to
each server added to the cluster. See the section “Starting the Configuration Console”
on page 50 for more information about this.
If the connection information of the database changes for some reason, you need to
reconfigure the Spotfire Servers and the configuration console so that they are able to
connect to the database. For the configuration console, you must edit the file
connections.xml, found in the /tomcat/webapps/admin/WEB-INF/
directory on the machine running the configuration console. For the Spotfire Servers,
you can either remove them from the cluster and re-add them, or edit the file
database.xml, found in the tomcat/webapps/META-INF/ directory
on each Spotfire Server. Below is a description of how these files look.
connections.xml
Server.Default
0
Server.Default
[DriverClass]
[DBServerURL]
false
WAIT_CONSERVATIVE
-1
0
600
false
true
The strings [DriverClass] and [DBServerURL] will be automatically set to
appropriate values by the configuration console when you add a server to a cluster.
You can also change the string tibcosoftwareinc.jdbc.sqlserver.SQLServerDriver if
you intend to use a different database driver. See the section “Database Drivers” on
138 (144) TIBCO Spotfire® Server 3.2.2