Skip to main content

Datasource Templates



These are basic templates that will get you started, you may need to do additonal mappings etc in some cases. let me know if you find anything and I am more than happy to update the template here

Vertica


<jdbc-type-settings>
   <type-name>Vertica</type-name>
   <driver>com.vertica.jdbc.Driver</driver>
   <connection-url-pattern>jdbc:vertica://host:port/db,dbadmin,dbpassowrd</connection-url-pattern>
   <ping-command>SELECT 1 FROM DUAL</ping-command>
</jdbc-type-settings>

 

Netezza

<jdbc-type-settings>
  <type-name>netezza</type-name> 
  <display-name>netezza</display-name> 
  <driver>org.netezza.Driver</driver> 
  <connection-url-pattern>jdbc:netezza://<host>/<database></connection-url-pattern> 
  <ping-command>Select 1</ping-command> 
  <fetch-size>10000</fetch-size> 
  <batch-size>100</batch-size> 
  <table-types>TABLE, VIEW</table-types> 
  <supports-catalogs>true</supports-catalogs> 
  <supports-schemas>true</supports-schemas> 
  <supports-procedures>true</supports-procedures> 
</jdbc-type-settings>

 JTopen / AS400



<!-- START of new AS400 Driver com.ibm.as400.access.AS400JDBCDriver.class -->
  <data-source-template>
        <enabled>true</enabled>
        <definition><![CDATA[<jdbc-type-settings>
    <type-name>as400_jdbc_jtopen</type-name>
    <driver>com.ibm.as400.access.AS400JDBCDriver</driver>
  <connection-url-pattern>jdbc:as400://&lt;systemName&gt;/&lt;defaultSchema&gt;;&lt;listOfProperties&gt;</connection-url-pattern>
  </jdbc-type-settings>]]></definition>
        <name>AS400 (JTOPEN)</name>
    </data-source-template>
  <!-- END of new AS400 Driver com.ibm.as400.access.AS400JDBCDriver.class -->



KDB


<jdbc-type-settings>
<type-name>KDB</type-name>
<driver>jdbc</driver>
<connection-url-pattern>jdbc:q:&lt;host&gt;:&lt;port1521&gt;</connection-url-pattern> <ping-command>SELECT 1</ping-command>
<metadata-provider>com.spotfire.ws.im.ds.sql.BasicJDBCMetadataProvider</metadata-provider>
<fetch-size>10000</fetch-size>
<batch-size>100</batch-size>
<table-types>TABLE, VIEW</table-types>
<supports-catalogs>false</supports-catalogs>
<supports-schemas>false</supports-schemas>
<supports-procedures>false</supports-procedures>
<max-in-clause-size>1000</max-in-clause-size>
</jdbc-type-settings>

VectorWise

<jdbc-type-settings>
  <type-name>VectorWise</type-name>
  <display-name>vectorwise</display-name>
  <driver>com.ingres.jdbc.IngresDriver</driver>
  <connection-url-pattern>jdbc:ingres://&lt;host&gt;:&lt;port&gt;/&lt;dbname&gt;</connection-url-pattern>
  <supports-catalogs>true</supports-catalogs>
  <supports-schemas>true</supports-schemas>
</jdbc-type-settings>

Postgres / Redshift

(when using redshift you may have to increase batchsize and fetch size to a big number like 100000)
<jdbc-type-settings>
  <type-name>PostgreSQL</type-name>
  <driver>org.postgresql.Driver</driver>
  <connection-url-pattern>jdbc:postgresql://&lt;host&gt;:&lt;port&gt;/&lt;database&gt;</connection-url-pattern>
  <ping-command>SELECT 1</ping-command>
  <metadata-provider>com.spotfire.ws.im.ds.sql.BasicJDBCMetadataProvider</metadata-provider>
  <fetch-size>10000</fetch-size>
  <batch-size>100</batch-size>
  <table-types>TABLE, VIEW</table-types>
  <supports-catalogs>true</supports-catalogs>
  <supports-schemas>true</supports-schemas>
  <supports-procedures>true</supports-procedures>
  <max-in-clause-size>1000</max-in-clause-size>
  <condition-list-threshold>7000</condition-list-threshold>
  <expand-in-clause>false</expand-in-clause>
  <table-expression-pattern>[$$schema$$.]$$table$$[@$$catalog$$]</table-expression-pattern>
  <procedure-expression-pattern>[$$schema$$.]$$procedure$$[@$$catalog$$]</procedure-expression-pattern>
  <create-temp-table-command>CREATE GLOBAL TEMPORARY TABLE $$name$$ $$column_list$$ ON COMMIT PRESERVE ROWS</create-temp-table-command>
  <drop-temp-table-command>TRUNCATE TABLE $$name$$;DROP TABLE $$name$$</drop-temp-table-command>
  <lob-threshold>2000</lob-threshold>
  <procedure-table-jdbc-type>-10</procedure-table-jdbc-type>
  <sql-runtime>com.spotfire.ws.im.ds.sql.postgresql.PostgresSQLRuntime</sql-runtime>
</jdbc-type-settings>

TEIID


    <jdbc-type-settings>
    <type-name>teiid</type-name>
    <driver>org.teiid.jdbc.TeiidDriver</driver>
    <connection-url-pattern>jdbc:teiid:&lt;vdb-name&gt;@mm:&lt;host&gt;:&lt;port&gt;</connection-url-pattern>
    <ping-command>SELECT 1</ping-command>
    <metadata-provider>com.spotfire.ws.im.ds.sql.BasicJDBCMetadataProvider</metadata-provider>
    <fetch-size>10000</fetch-size>
    <batch-size>100</batch-size>
    <table-expression-pattern>[$$schema$$.]$$table$$</table-expression-pattern>
    <table-types>TABLE, VIEW</table-types>
    <supports-catalogs>true</supports-catalogs>
    <supports-schemas>true</supports-schemas>
    <supports-procedures>true</supports-procedures>
  </jdbc-type-settings>


Comments

  1. I am facing an issue with the change in the database names. I have two sql server database servers. (Dev and Prod). I have two database_A, database_B in Dev and two database_A, database_B in Prod. Both contain the same tables with different data. My dev DXP points to database_A. I want to point to database_B on prod. I have one spotfire server with a library. When I export and import library items from one folder (DevFolder) to another folder (ProdFolder). Using Remap data source task, I am changing the database name in the jdbc connection string to database_B on prod server. It points to database_A on prod. This looks like it is based on the database name setting from dev. When I look in the columns in the information designer, it has ProdFolder/database_A/Column1 on the prod. Have anyone encountered a similar issue before pointing to two different database names?

    ReplyDelete

Post a Comment

Popular posts from this blog

Using Accordions in Spotfire Text Areas

Spotfire 6.0 provides great tools for quickly building your dashboard, but here we will learn to spice up things with the help of new 6.0 text area. If you are not aware the new 6.0 Text area supports HTML, Javascript and CSS. This opens up possibilities for doing a lot more with the text area. Some of the basic stuff can be seen here http://spotfire.tibco.com/qrt/UBSAN/presentation.html?pcode=100044   One of the cool things you can do is build an accordion panel in the text area for better utilization of the valuable screen real estate and helping the overall experience.(Watch the 0:15 second video below to see how accordion works - Sorry for the jitter in the video. The screen recorder does not record fast enough) Here is the html behind the text area : Please note that Spotfire controls are automatically created when you add text area controls, like filters, drop down lists etc. <DIV id="myaccordion"> <H3>Analysis Details</

Calendar Chart in Spotfire

I recently had a colleague asking me to show him the data in a calendar format.. Something like this I basically used a scatterplot for this.  You can check out the original DXP here  http://bit.ly/spotcalendar Some key settings to make it a calendar. Please note Order date is the date of interest here These expressions are out of the box expressions, no need to handcode them, but select them in the axis value  X Axis    <BinByDateTime([Order Date],"DayOfWeek",0)> Y Axis    Week([Order Date]) Trellis into panels   <BinByDateTime([Order Date],"Year.Quarter.Month",2)> Manual layout 4 X 3 Labels  UniqueConcatenate(DayOfMonth([Order Date])) Shape Tiled Markers Marker by   <UniqueConcatenate([Order Date])> Happy plotting your calendar!!!

Spotfire Auto Save for recovery

This is an extension I build to auto save local copies of currently open DXP every 15 minutes.. I have tested briefly and it seems to be doing its job, please please please try and test it if you can access a server and deploy.. Key Notes - This add-on will Auto Save Files while only in Spotfire Analyst Client. The save time is hard coded for every 15 minutes. Files are saved only if they are changed or user has done some actions like marking, filtering etc. The Files are saved in temporary location of the system, generally which will be like C:\Users\<username>\AppData\Local\Temp\Spotfire AutoSave If a Library file is opened it will be saved on your local machine under the temp path C:\Users\<username>\AppData\Local\Temp\Spotfire AutoSave\Library Content\ Library path will be replicated in this autosave location. e.g. C:\Users\<username> \Local\Temp\Spotfire AutoSave\LibraryContent\mylibraryfolder\mylibraryfilename_mmddyyyy_HH