Prerequisites for connecting to Tibco Spotfire

To integrate with Tibco Spotfire, particularly for getting data, you must deploy Metric Insights' Remote Data Collector (RDC) to your server and install a custom MIAddIn package (extension) on a Spotfire server. 

This article assumes that you have already configured a Remote Data Collector profile in the Metric Insights UI and installed Insightd on your remote Tibco Spotfire Windows Server

1. Connect to Spotfire Remote Desktop client

  1. Enter the hostname of the computer with the installed Remote Desktop client
  2. Specify the User name of the remote computer
  3. Click [Connect]
  4. Provide your Password credential
  5. Click [OK] to proceed

2. Access Spotfire server

  1. Open your browser and type "localhost" in the address bar
    • When you press enter, you will be redirected to the Spotfire Homepage
  2. Click Deployments & Packages icon in the Homepage navigation menu

3. Add the Extension to Deployment area

Spotfire extensions are functional units included in Spotfire add-ins. When added, they enable custom capabilities.

Extension artifacts are compiled and packaged into Spotfire packages, .spk files (containing the .dll's for the extension code and other resources as well as a module.xml file describing the metadata of the extension).

Since the .spk (extension) file can be large, we recommend uploading this file from the Spotfire server directly (localhost). Otherwise, you may get the error "Request Entity Too Large" (413).

  1. Deployment areas page will display available areas for deploying your extension
  2. [Add packages]: click to add a package to a deployment area
  3. [Choose File]: click to access the MICustomTasks.spk file
    • The file is located in the Tibco plugin directory C:\Program Files (x86)\Metric Insights\Insightd\plugins\tibco\MICustomTasks.spk
  4. Open
  5. Upload

4. Save the new Distribution

  1. The .spk extension file will be uploaded as an MIAddIn package with the "Add" status
  2. [Save]: click to save and validate the new distribution

5. Update Automation Services

After adding the MIAddIn extension package, you need to update Automation Services to the new deployment.

  1. From the navigation menu dropdown, select Nodes & Services
  2. Click the tree view symbol [+] to open the hierarchical structure of Network components and select the required Automation Service
  3. Go to More actions > Update Service
    • Updating the Service will get the latest modules from the deployment area and create a new Service

6. Migrate Instances to the new Service

After the new Service has been created, you need to migrate Instances from the old to the new Automation Service.

  1. Go to More actions > click Migrate

7. Restart your Instances

  1. Access the newly created Automation Service
  2. Verify that the Service has been installed successfully
  3. Click the name of the Instance to access its configuration page
  4. Restart the Instance
  5. Make sure that Service can communicate successfully

If the new Automation Service runs successfully, you can optionally delete the old Service.

8. Add configuration file to Insighd directory

To connect the MI server to the Tibco Spotfire server, you need to create the spotfire.conf file and add it to the Insightd package.

  1. In the file, specify the parameter (RDC hostname) as rdchostname=ip-address or hostname
    1. For example, rdchostname=10.8.0.27
  2. Optionally, you can override the port via rdcPort=port
    1. For example, rdcPort=81
    2. The default port used for TCP socket communication from Spotfire to RDC is 4444
  3. Place the configuration file in the Insightd/plugins directory

After that, run RDC and Test Connection from the Metic Insights UI (as available in the Tibco Spotfire connection profile).

8.1. How to obtain the ip-address (for spotfire.config)

To get the ip-address of the machine with the installed RDC, enter ipconfig in the Windows Command Prompt.

If there are several ip-addresses listed, use the first.

0 Comments

Add your comment

E-Mail me when someone replies to this comment