LVconf Type: External Server Connection

Use this selection to specify that the external data source is a Query Table in a running StreamBase application. With this selection, you must also double-click the uri parameter to specify the full StreamBase URI in sb:// or sbs:// format. Specify the path down to the container that holds the Query Table of interest, if applicable. All Query Tables in the specified StreamBase URI become available to serve from LiveView.

Use this selection to specify that the external data source is from another LiveView table running on the same system or remotely. When using this option, you must specify at least the uri parameter to specify a LiveView URI in lv:// or lvs:// format. The other options shown in the Table Provider Parameters field typically do not need to be set.

Use this selection when the external data source supports JDBC. Run the LiveView JDBC Table sample to learn more about this external data source.

When configuring LiveView to use this data source, you must:

LiveView supports fetching JDBC tables from an external JDBC data source, where the external data source can be any supported JDBC data source. You can filter the JDBC table list by specifying JDBC tables in the lvconf file. The LiveView Table sample's example below filters for one JDBC table called DEVICES:

<mapping selector="DEVICES" formatter="%s"/>

You can perform any SQL query (for example, a SQL query that joins n JDBC tables) and show the query results in one LiveView table. Also, multiple SQL query-based LiveView tables can be part of the same lvconf of external connection type.

You can query multiple JDBC tables from the same data source and send the results to n number of LiveView tables. To define LiveView tables, use Table as the prefix and enter a table name for each table:

<parameter key="TableYourNewLVTable1">
<parameter key="TableYourNewLVTable2">
...

Append n number of queries to your defined LiveView tables as needed. This example defines two queries for two LiveView tables:

<parameters>
  <parameter key="dataSourceRefName">sample</parameter>
     
  <parameter key="TableYourNewLVTable1">select 
    s.UNIT_ID as ID,
    d.UNIT_NAME as Unit,
    s.SERVICE_OPERATION as Operation,
    s.SERVICE_DATE as Date,
    c.NAME as Company,
    c.PHONE as Phone
    from SERVICE_DATA as s
    inner join DEVICES as d on s.UNIT_ID=d.UNIT_ID
    inner join SERVICE_COMPANY as c on s.SERVICE_CO_ID=c.SERVICE_CO_ID</parameter>
    
  <parameter key="TableYourNewLVTable2">select 
    s.UNIT_ID as ID,
    d.UNIT_NAME as Unit,
    s.SERVICE_OPERATION as Operation,
    s.SERVICE_DATE as Date,
    c.NAME as Company,
    c.PHONE as Phone
    from SERVICE_DATA as s
    inner join DEVICES as d on s.UNIT_ID=d.UNIT_ID
    inner join SERVICE_COMPANY as c on s.SERVICE_CO_ID=c.SERVICE_CO_ID</parameter>
</parameters>
...    

Use this selection to specify that the external data source is TIBCO ActiveSpaces. Run the LiveView ActiveSpaces sample to learn more about using this external data source.

Use this selection to specify that the external data source is in another format not provided by StreamBase or Spotfire LiveView. In this case, you must also specify the fully qualified path to a class in the classpath of the current Studio project. The specified class must know how to locate, read data from, and interpret the custom table type. Remember that the classpath when running projects in Studio is not necessarily the same as when running the same project from the command line. Use the Table Provider Parameters section to specify any parameters needed to locate the custom table.