Spotfire Integration with Statistica

TIBCO Spotfire® can call external analytic engines through Data Functions. Statistica uses this capability to give Spotfire users a way to drive their dashboards using Statistica analytic models and workspaces.

TIBCO Statistica™ analytic engine is available as a Spotfire extension to allow seamless native distribution of the engine.

Each Spotfire application instance has a local copy of Statistica engine as an extension or add-on for Spotfire Analyst. The Spotfire extension also supports the use of an installed Statistica Desktop instance.
Note: The installed Statistica version must include the command line interface of the Unified Statistica Engine that is available in 13.4 or later.

Spotfire Integration Application and Uses

Spotfire Integration runs Statistica tasks in the form of workspaces. Workspaces are visual no-code expressions of advanced analytic models used for subsequent deployment into automated scenarios for data processing and decision making. These workspaces can be stored locally or in a centralized version-controlled Statistica Enterprise metadata store. Both these sources are supported in Spotfire Integration.

Workspaces authored in Statistica can be exposed in Spotfire as a Statistica Data Function.
Note: Data Functions are reusable named operators with input and output parameters. For more information, see the To map and execute a previously registered data function from the Insert menu.

Statistica Data Functions can be registered through Statistica Integration dialog box.

When you pick a Statistica workspace on the local disk or from Statistica Enterprise, Spotfire extension creates a Data Function in Spotfire. You can then configure the Data Function inputs and outputs to Spotfire content.

Linking and Embedding

Spotfire integration supports linking and embedding of the workspace artifact.
  • Linking: The document stays where it came from, either disk or Enterprise store, and is only referenced in the Data Function definition. Linking maintains the single sourcing, but can cause accessibility and permission issues.
  • Embedding: The workspace is serialized into the Data Function definition itself. When a workspace is embedded into the data function, that copy is used during data function execution. The original workspace can be disconnected, but can potentially cause maintenance issues.