Advanced procedures
These manual procedures are for setting up various features that are supported by Spotfire. Many of the procedures assume prior knowledge of technologies such as LDAP, Kerberos, and so on.
- Tuning and logging
Beyond the administration activities described in other chapters, there are other things you can do to tune or troubleshoot your system. - Security administration
You can do a lot of things to ensure a secure environment. - Spotfire Server public web services APIs
Spotfire Server offers several web services application programming interfaces (APIs) for building custom applications that interact with Spotfire Server. There are both SOAP and REST APIs. - Session management
Configuring your server to close an idle session, to require users to log in when a session reaches its time-out limit, and to restrict the number of concurrent sessions allowed can contribute to a robust security strategy for your TIBCO Spotfire Server environment. - Scheduled updates and Automation Services rules
You can modify the following settings for scheduled updates and Automation Services rules. - Changing how long the server waits before assuming that a node manager is offline
You can configure the amount of time that Spotfire Server waits for a node manager to signal its presence. If the node manager does not send a signal within the configured time period, the server assumes that the node is offline. For setups that are experiencing a heavy load, you can raise this value to avoid unnecessarily restarting a node manager. - Switching the Java Development Kit
The Spotfire Server includes an Oracle Java Development Kit (JDK). This JDK is usually the most recent and secure version at the time of the TIBCO Spotfire Server release. However, if you always want to use the most recent Java version, or if you want to use a Java Development Kit from another vendor, you must upgrade to the newer Java version manually, whenever it is released. - Customizing Spotfire for the end users
It is possible to customize the Spotfire look and feel to your own company profile using cobranding. You might also have other reasons to modify the default environment for your end users.
- Tuning and logging
Beyond the administration activities described in other chapters, there are other things you can do to tune or troubleshoot your system. - Security administration
You can do a lot of things to ensure a secure environment. - Spotfire Server public web services APIs
Spotfire Server offers several web services application programming interfaces (APIs) for building custom applications that interact with Spotfire Server. There are both SOAP and REST APIs. - Session management
Configuring your server to close an idle session, to require users to log in when a session reaches its time-out limit, and to restrict the number of concurrent sessions allowed can contribute to a robust security strategy for your TIBCO Spotfire Server environment. - Scheduled updates and Automation Services rules
You can modify the following settings for scheduled updates and Automation Services rules. - Changing how long the server waits before assuming that a node manager is offline
You can configure the amount of time that Spotfire Server waits for a node manager to signal its presence. If the node manager does not send a signal within the configured time period, the server assumes that the node is offline. For setups that are experiencing a heavy load, you can raise this value to avoid unnecessarily restarting a node manager. - Switching the Java Development Kit
The Spotfire Server includes an Oracle Java Development Kit (JDK). This JDK is usually the most recent and secure version at the time of the TIBCO Spotfire Server release. However, if you always want to use the most recent Java version, or if you want to use a Java Development Kit from another vendor, you must upgrade to the newer Java version manually, whenever it is released. - Customizing Spotfire for the end users
It is possible to customize the Spotfire look and feel to your own company profile using cobranding. You might also have other reasons to modify the default environment for your end users.