Spotfire® Server and Environment - Installation and Administration

Spotfire library introduction

The Spotfire library is used to store Spotfire analyses, Spotfire binary data format files (SBDF), data functions, shared data connections (or connection data sources) created with Spotfire connectors, information links and data sources used by Information Services, mods, and visualization color schemes.

The Spotfire library content (analyses, data, mods, and so on) can be stored in the Spotfire database or in the cloud using different external storage solutions. The library is accessible to users of the installed Spotfire client and the web client through the Spotfire Server, allowing users to easily share and reuse their work.

By default, items created by analysis authors that are imported into the Spotfire library are compressed using the gzip format. Items exported from the library are also compressed using gzip. This design provides more efficient use of library space, whether the library is stored in the Spotfire database or in an external storage system. Library compression works with all supported databases.

You can configure the library compression to meet your specific library needs, including disabling it altogether. If you disable library compression, then compressed items in the library are uncompressed in the background over time.

The library is organized into hierarchical folders, which are also used to control access to folder content. The administrator creates the folder structure, and assigns groups with the appropriate read and write permissions to the folders.

Important: If the database runs out of disk space, then the complete Spotfire environment becomes unresponsive. You must ensure that the database has enough space (either through external storage, or through file storage) for the lazy migration to increase and reduce as it uncompresses and compresses the content in the background.

To handle "lazy migration" (background) compression and uncompression of existing contents, Spotfire Server must use temporary storage space, which is created at <server installation directory>/tomcat/temp. To provide the best conversion and not stress the server resources, ensure that this temporary space is at least twice the size of the largest artifact in the library. (For example, you can follow this formula: largest_item_in_the_library * the_number_of_cores_in_the_host * 2).