Product: TIBCO Spotfire®
How to deploy a custom built extension to the Standalone Spotfire Desktop Client.
Version: All Versions
OS: All Supported Operating Systems
--------------------
Description:
The standard procedure for using the SDK Package Builder to create Spotfire packages (.*spk files) for custom extensions to be deployed onto the Spotfire Server, does not apply to the standalone Spotfire Desktop client. Deploying custom extensions to the standalone Spotfire Desktop client is a manual process.
Resolution:
The SDK Package Builder does not include a functionality to deploy packages directly to TIBCO Spotfire clients. This tool can only deploy packages directly to a TIBCO Spotfire Server. Additionally, TIBCO Spotfire clients can only download, extract and install Spotfire packages from an online connection to a Spotfire Server. When using the standalone Spotfire Desktop client, which does not have an online connection to a Spotfire Server, it is still possible to deploy your custom built extensions by following a manual procedure.
Manual Procedure:
You will need access to the custom extension build folder, where the custom extension compiled assemblies can be found. These are the steps to follow:
1). All Spotfire modules are loaded into the client by the configuration file which is the file you will need to edit. Locate the "Spotfire.Dxp.exe.config" file in the Spotfire Desktop installation root folder.
2). Edit the "Spotfire.Dxp.exe.config" file in a text editor and find the element tag named "modules".
3). Add a new folder path element (underneath the "modules" tag element) that points to your custom extension build folder. Leave the previously existing folder path element unchanged. For example:
------------
...
...
...
....
...
------------
4). Ensure that the argument "loadAllModules" is present, as well as the "arguments" parent element ( ... ). If it is not found, add it as in the example detailed above.
http://stn.spotfire.com/stn/PackageBuilder/PackageBuilder.aspx
Reference:
http://stn.spotfire.com/stn/PackageBuilder/PackageBuilder.aspx
Comments
0 comments
Article is closed for comments.