TIBCO Spotfire Server 3.2.2 - TIBCO Product Documentation
TIBCO Spotfire Server 3.2.2 - TIBCO Product Documentation
TIBCO Spotfire Server 3.2.2 - TIBCO Product Documentation
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Advanced Procedures<br />
sqlplus @DB<strong>Server</strong> @create_server_env.sql "spotfire_server"<br />
Microsoft SQL <strong>Server</strong><br />
When populating a <strong>Spotfire</strong> database residing on a Microsoft SQL <strong>Server</strong> the<br />
create_databases script passes certain variables to these scripts. These variables<br />
include:<br />
• SERVERDB_NAME<br />
• DEMODB_NAME<br />
When you run the SQL scripts manually, you must make sure to pass these variables<br />
along to the scripts. For example:<br />
sqlcmd -S DB<strong>Server</strong>\DBInstance -i create_server_db.sql -v<br />
SERVERDB_NAME="spotfire_server"<br />
9.14 Resizing Temporary Tablespace<br />
The tablespaces/database files for <strong>Spotfire</strong> <strong>Server</strong> using Oracle/MSSQL Database uses<br />
autoextend/autogrowth by default. If this turns out to be inappropriate for your needs<br />
alter this settings. It might be desirable to alter the amount the files should be extended<br />
by with each increment. For Oracle there is a maxsize for each tablespace which<br />
should be reviewed. For MSSQL, there is an unlimited growth this should also be<br />
reviewed.<br />
9.15 Modifying the Virtual Memory<br />
<br />
If many simultaneous users intend to perform heavy data pivoting via Information<br />
Services or in other ways stress the server, you may need to modify the amount of<br />
memory available to the virtual machine. The application server’s JVM must have<br />
equal settings for the initial and maximum heap sizes, otherwise data pivoting in<br />
Information Services will not work properly and there might be a risk that the server<br />
will run out of memory.<br />
Note: Do not allocate too much heap memory because every JVM has a specific upper<br />
limit for how much memory it can handle. If the memory allocation exceeds this limit,<br />
the JVM may not start. The recommended setting that will work for most installations<br />
is the default value of 1024 MB.<br />
To Set Up the Start Script (not running as a Windows service):<br />
1 Open the file /tomcat/bin/setenv.bat/.sh in a text editor.<br />
2 Find the line that sets the variable JAVA_OPTS:<br />
set JAVA_OPTS=-server -XX:+DisableExplicitGC -XX:MaxPermSize=256M -Xms1024M -Xmx1024M<br />
or<br />
<strong>TIBCO</strong> <strong>Spotfire</strong>® <strong>Server</strong> <strong>3.2.2</strong> 103 (144)