Sites

You can create multiple Spotfire environments that share the same Spotfire database, including the library and user directory. These environments, which are called sites, can be configured to reduce latency for multi-geographic deployments. Sites also enable the use of a variety of authentication methods, along with different user directories, within the same deployment.

Each site includes one or more Spotfire Servers along with their connected nodes and services. A site's servers, nodes, and services can only communicate within the site, but because the Spotfire database is shared among the sites, all of the sites have access to the users, groups, and library in your Spotfire implementation.

If the site will contain more than one server, clustering must be enabled for that site; for more information, see Clustered server deployments.
Note: All the sites in an implementation must use the same clustering method.

You assign a Spotfire Server to a site when bootstrapping the server. You can change the assignment afterwards by following the instructions in Moving a server and its nodes to a different site. When you assign a Spotfire Server to a site, any nodes that are connected to the server are automatically included in the site.

As of Spotfire version 7.9, all upgraded servers and nodes belong to the Default site. To assign the upgraded components to a site that you created, use the procedure Moving a server and its nodes to a different site.

The potential reduced latency occurs between the servers and the service instances within a site, resulting in quicker manipulation of data that is already present in the site. To optimize the end-user experience, a best practice when configuring sites is to create scheduled updates so that data and analyses are downloaded from the database before users request them. For more information, see Scheduled updates to analyses.

These are typical uses of Spotfire sites:
  • To route user requests from a particular office to the servers and nodes that are physically closest to that office. This reduces the impact of network latency between servers that are located in different geographic regions.
  • To enable different authentication methods for different sets of users who share a Spotfire implementation. For example, internal users may use Kerberos authentication while external users such as customers and partners may use username and password authentication.

Administrators who oversee several sites can switch sites from the landing page of the administration interface.

In a deployment that contains sites, the following items are site specific and not shared with any other sites:
The following items are "global", so shared among all the sites in a deployment:
  • Library
  • User directory
  • Groups
  • Deployments
  • Server configuration file
  • Service configuration files
  • LDAP synchronization
  • Signing certificates
  • Login page RSS feed