Meta Integration® Model Bridge (MIMB)
"Metadata Integration" Solution

MIMB Bridge Documentation

MIMB Import Bridge from TIBCO Spotfire Server (Repository)

Bridge Specifications

Vendor TIBCO Software Inc.
Tool Name Spotfire Server
Tool Version 7.13 or newer
Tool Web Site https://spotfire.tibco.com
Supported Methodology [Business Intelligence] Multi-Model, BI Report (Relational Source, Expression Parsing, Report Structure) via Java API

BRIDGE INFORMATION
Import tool: TIBCO Software Inc. Spotfire Server 7.13 or newer (https://spotfire.tibco.com)
Import interface: [Business Intelligence] Multi-Model, BI Report (Relational Source, Expression Parsing, Report Structure) via Java API from TIBCO Spotfire Server (Repository)
Import bridge: 'TibcoSpotfireServer' 10.1.0

BRIDGE DOCUMENTATION
This bridge imports from Tibco Spotfire Server.

This bridge connects to Spotfire server using the WebService API and OAuth 2.0 protocol for authentication and authorization.
Before the API can be used, an OAuth 2.0 API client must be registered.
You must complete the following configuration steps to register an OAuth 2.0 API client in the Spotfire server:
- On the computer running Spotfire Server, open a command line as an administrator
- Change the directory to the location of the command line configuration tool (config.bat on Windows, config.sh on Linux).
The default location is $server installation dir$/tomcat/bin
- Export the active server configuration from the Spotfire database into a local configuration.xml file by using the export-config command.
Example: config export-config --tool-password=mypassword
- Use the register-api-client command to register an OAuth API client.
Example: config register-api-client -n OAuthClient1 -Sapi.soap.library-service
All information needed to use the client, including a client ID and a client secret, will be shown after successful completion of the command.
For example:
Client ID: eeb2e41a2ae5d7df13cc600b5973727e.oauth-clients.spotfire.tibco.com
Client secret: 797fc101fbb1d0aa599e65413b33a90b713a65f7f667ee61f61506cc1e76a9a5
To view the full oauth client configuration, you can use the 'show-oauth2-client' command.

To verify that the server is up and running and check the server properties, you may point your web browser to URL:
http://server:port/spotfire/manifest

To verify that the WebService API is available, you may point your web browser to URL:
http://server:port/spotfire/api/soap/LibraryService/wsdl
This WebService API is available since Spotfire server version 7.13.0
Older versions of the WebService API are deprecated, and therefore not supported.


Bridge Parameters

Parameter Name Description Type Values Default Scope
Server URL Specify here the Tibco Spotfire Server URL.
The default URL is usually: http://localhost:8080/spotfire

Accessing Spotfire Server via HTTPS:
In order to connect to the Spotfire Server via HTTPS, you need to import the server certificate into the client machine java trust store.
1. Copy the Spotfire Server certificate to the client machine, for example in jre\lib\security\server.cer
2. Open a command prompt window, and set the local directory:
cd jre\lib\security
3. If the jssecacerts trust store is missing, make a copy of the default cacerts file:
copy cacerts jssecacerts
4. Import the server certificate file into the trust store:
..\..\bin\keytool.exe -importcert -alias serveralias -file server.cer -keystore jssecacerts
Enter keystore password: changeit
Trust this certificate? [no]: yes
STRING   http://localhost:8080/spotfire Mandatory
Login User Enter the username which the bridge will use to log in. Be sure this user name has necessary permissions to access the objects you wish to import.
This corresponds to the Client ID for an OAuth 2.0 authentication method.
STRING     Mandatory
Login Password Enter the password associated with the username which the bridge will use to log in.
This corresponds to the Client secret for an OAuth 2.0 authentication method.
PASSWORD     Mandatory
Library subset This option is used to access objects stored in the Spotfire library.
You can specify here multiple IDs of reports and/or folders, to be retrieved, separated by semicolon (;) character.
REPOSITORY_SUBSET      
Incremental import Specifies whether to import only the changes made in the source or to re-import everything (as specified in other parameters).

True - import only the changes made in the source.
False - import everything (as specified in other parameters).

An internal cache is maintained for each metadata source, which contains previously imported models. If this is the first import or if the internal cache has been deleted or corrupted, the bridge will behave as if this parameter is set to 'False'.
BOOLEAN
False
True
True  
Miscellaneous Specify miscellaneous options identified with a -letter and, if applicable, a value.
-r to remove the report pages and their graphical structure
-c Connection1=ORACLE;Connection2=TERADATA; to explicitly specify database connection(s) type(s).
When Spotfire connects to a database using ODBC the database type is not stored in the DXP file.
This option allows one to specify the database connection type in order to successfully parse the SQL query syntax.
Here is a list of major supported database connection types:
ORACLE
MICROSOFT SQL SERVER
DB2/UDB
TERADATA
SYBASE
NETEZZA
POSTGRESQL
MYSQL
HIVE
ACCESS
-pi import the document's preview image, storing the PNG image in base64
STRING      

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"TIBCO Spotfire Server (Repository)"
Metamodel
Tibco Spotfire (Server)
Mapping Comments
     
DirectoryStructureModel Server  
Name Name  
Folder Folder  
Description Description  
Name Name  
NativeId Native Id  
NativeType Native Type  
StoreContent Data Source, Data Connection, Document  
Description Description  
Name Name  
NativeId Native Id  
NativeType Native Type  

Last updated on Wed, 11 Dec 2019 18:39:35

Copyright © Meta Integration Technology, Inc. 1997-2019 All Rights Reserved.

Meta Integration® is a registered trademark of Meta Integration Technology, Inc.
All other trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.