The Spotfire Package (SPK)
A Spotfire SPK is usually created and tested by developers to package and deploy third-party extensions to the Spotfire Server, which can then be distributed to the Spotfire Server node for use by another service (and in some cases, distributed to Spotfire clients).
Note: Even though they are both called “packages”, the R package
and the Spotfire package (SPK) are different.
- The R package (usually downloaded from a repository, such as CRAN) contains specialized R functions.
- The SPK is a means to deploy extensions to the Spotfire Server, which either distributes its contents to Spotfire Analyst users, or installs for a service, such as TERR service, to use from the Spotfire Server node.
To make it easy to create SPK files containing
TERR functions, use the package SpotfireSPK, which
has the following two functions:
buildSPK
, which creates an SPK containing packages suitable for distribution to other Spotfire Analyst clients to create analyses using data functions.Note: This use case applies only to TERR and not TERR service, so it is not covered in the TERR service documentation.buildServerSPK
, which creates an SPK containing packages suitable for distribution to a Spotfire Server for use by the TERR service.
This documentation does not cover Spotfire SPKs in general, only those packages built using the SpotfireSPK package that contain R packages. For more general information about extending Spotfire using the SPK, see the Spotfire Developer documentation available at docs.tibco.com.
- Obtaining the SpotfireSPK toolset
Using the SpotfireSPK package, you can generate a Spotfire SPK containing your TERR packages, and then automatically distribute them to Spotfire Analyst installations in your organization. - Spotfire SPK versioning
Typically, you create the SPK (.spk) file that contains the packages, and then you install it on a service running on a Spotfire Server node. You might need to change or update the packages that you distribute, which requires updating the .spk file. - Creating an SPK to put a CRAN Package on Spotfire Server
By running a few lines of TERR code, you can create a Spotfire SPK that you can deploy to Spotfire Server for use by the Spotfire web clients. - Adding CRAN Packages to an existing SPK to put on Spotfire Server
By editing the DCF and then running a few lines of TERR code, you can add packages to a Spotfire SPK that you can deploy to Spotfire Server for use by the TERR service and the Spotfire web clients. - Removing CRAN Packages from an existing SPK to put on Spotfire Server
By editing the DCF and then running a few lines of TERR code, you can remove packages from a Spotfire SPK that you can deploy to Spotfire Server for use by the TERR service and Spotfire web client users.
- Obtaining the SpotfireSPK toolset
Using the SpotfireSPK package, you can generate a Spotfire SPK containing your TERR packages, and then automatically distribute them to Spotfire Analyst installations in your organization. - Spotfire SPK versioning
Typically, you create the SPK (.spk) file that contains the packages, and then you install it on a service running on a Spotfire Server node. You might need to change or update the packages that you distribute, which requires updating the .spk file. - Creating an SPK to put a CRAN Package on Spotfire Server
By running a few lines of TERR code, you can create a Spotfire SPK that you can deploy to Spotfire Server for use by the Spotfire web clients. - Adding CRAN Packages to an existing SPK to put on Spotfire Server
By editing the DCF and then running a few lines of TERR code, you can add packages to a Spotfire SPK that you can deploy to Spotfire Server for use by the TERR service and the Spotfire web clients. - Removing CRAN Packages from an existing SPK to put on Spotfire Server
By editing the DCF and then running a few lines of TERR code, you can remove packages from a Spotfire SPK that you can deploy to Spotfire Server for use by the TERR service and Spotfire web client users.
Parent topic: Package Management for the Service