To make the demo database available to users, locate the folder called demodata in the Spotfire Server installation kit. Select the oracle or mssql sub-folder depending on your database server, and copy the file within this folder, demo.part0.zip to a shared disk location. See “Configuring a Specific Directory for Library Import and Export” on page 108. This ZIP file contains analysis files and an information model that links to the demo data.
When this file is in place, a Spotfire Administrator or Library Administrator can import these files to the Library.
To Import the demo files into the Library 1 Start Spotfire and log in as a Spotfire Admin.
2 Select Tools > Library Administration.
3 Navigate to the Library folder where you want to import the demo files. For instance, you can create a folder called Demo.
4 Select Import.
5 Click Browse and select the file demo.part0.zip. 6 Click OK.
7 Click OK.
8 Click Close when the dialog states Import Done.
A template data source will also be imported with this file. You must use the Informa-tion Designer to edit this and supply the URL and login informaInforma-tion of your database server for it to work. See the Information Designer Help for more information about how to set up and edit data sources.
6 Monitoring
Spotfire Server can be monitored. Reasons for monitoring include detecting problems with the server itself, problems with external systems such as databases and LDAP servers, network problems, misconfigured clients, and in some cases malicious behav-ior. The purpose is typically to reduce downtime, detect and fix problems before users notice them, and eliminate performance bottle necks.
Spotfire Server can be monitored using TIBCO Hawk® or any other Java Manage-ment Extensions (JMX) compliant monitoring tool, like JConsole, a part of the Java SDK which is bundled with Spotfire Server. JMX is a Java framework for monitoring and managing applications and devices. It is part of the Java Platform Standard Edition since version 5.0.
See “Action Logs and System Monitoring” on page 121 for information about how to log actions running on Spotfire Server, and also events from Spotfire, Spotfire Web Player, and Spotfire Automation Services.
6.1 Instrumentation
JMX consists of three levels:
1 Instrumentation level: Provides monitoring information and management operations.
2 Agent level: Server that provides applications access to the instrumentation level.
3 Remote Management level: Connectors and adaptors providing access to the agent.
Spotfire Server runs within the Tomcat application server, which provides the basic functionality needed, the server (Agent level), and a Java Remote Method Invocation (Java RMI) connector (Remote Management level).
Tomcat provides a rich instrumentation set for monitoring and managing the applica-tion server. For example, it monitors Tomcat configuraapplica-tion parameters and basic usage statistics. The Java shipped with Spotfire Server is also heavily instrumented using JMX, providing information about CPU and memory usage, garbage collection, and thread pools.
Spotfire Server has been instrumented with the following measures:
Note: Also see “Action Logs and System Monitoring” on page 121.
Server
Server address (IP)
Server hostname
Server version
Date and time the server was started
Uptime time since the server was started, both as a formatted string and in milliseconds since January 1, 1970, 00:00:00 GMT
Logging
Current log configuration file (configurable)
Available log configuration files (read only)
Lists all log configuration files in <installation dir>\tomcat\webapps\spotfire\
WEB‐INF
Number of logging events on warn, error, and fatal levels Logger
There may be several of these or none at all, depending on the log configuration.
Log appender name
Notifications: Outputs all log statements from a configured log4j appender as JMX notifications
Server Metrics
Number of attachments on the server
Number of running Information Services jobs
Number of authenticated HTTP sessions HTTP Status Codes
Number of HTTP response codes representing client or server errors, meaning the 4xx and 5xx ranges returned from the server.
Note: Responses in these series may be common, even in a system that works well.
Data Source
One entry for each currently running data source on the server, including the server’s own data source:
Name
URL
Configured minimum number of connections
Configured maximum number of connections
Current number of active connections
Current number of idle connections
The maximum number of concurrently active connections seen
6.2 Configuration
Because sensitive information may be provided through JMX, and Java, Tomcat, and Spotfire Server provide some management capabilities, it is important to restrict access. The JMX RMI connector is disabled by default; the administrator must enable it. Also consider the authentication, authorization, and encryption security features.
Authentication
Spotfire Server solution applies the existing database authentication mechanism using a separate database table. Passwords are hashed and the same principals may be used across an entire Spotfire Server cluster.
Authentication is enabled by default.
Authorization
Each user has either read, or read and write, permissions. This means that the user can either only read attribute values or, in addition, read and modify the attributes if they are writable.
Authorization is enabled by default. Authorization only works with the default authen-tication implementation.
JMX accounts and credentials are separated from Spotfire accounts and credentials.
The JMX accounts are only used for monitoring, since ordinary Spotfire login does not work.
Encryption
The RMI connector can be configured to encrypt the traffic using SSL. This is recom-mended since user names and passwords are otherwise transmitted in plain text.
SSL is not enabled by default. It requires a certificate.
Firewalls
A firewall can be configured to allow traffic to the desired ports. By default the RMI registry and the RMI connector share a common port (1099) to simplify firewall con-figuration.
JMX Configuration Commands
The following commands are used to configure and administrate JMX access to the monitoring component.
config‐jmx Configures the JMX RMI connector
create‐jmx‐user Creates a new JMX user account delete‐jmx‐user Deletes a JMX user
list‐jmx‐users Lists all JMX users
6.3 Example
This is the procedure to set up JMX monitoring using JConsole. This example does not use SSL:
1 Run the config‐jmx command: config config‐jmx ‐‐enabled=true
2 Import the configuration: config import‐config ‐‐comment=”Enabling JMX”
configuration.xml
3 Provide the configuration tool password.
4 Create a JMX user: config create‐jmx‐user ‐‐username=MyJMXUser 5 Provide the MyJMXUser password.
6 Provide the configuration tool password to write the user and password to database.
7 Restart Spotfire Server.
8 Launch the JConsole application. In a default Windows installation: C:\tibco\tss\6.5\
jdk\bin\jconsole.exe
9 In the JConsole New Connection dialog, select Remote Process, enter the
<hostname>:1099, and provide the JMX user name and password.
Comment: To view the Spotfire specifics, see the MBeans tab and the com.spotfire.server domain.