This HTML5 document contains 51 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

PrefixNamespace IRI
n29http://ods.openlinksw.com/dataspace/person/dav#
n8http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtLinkInf04.
dctermshttp://purl.org/dc/terms/
n19http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtLinkInf10.
n18http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtLinkInf09.
atomhttp://atomowl.org/ontologies/atomrdf#
n6http://ods.openlinksw.com/dataspace/owiki/wiki/
foafhttp://xmlns.com/foaf/0.1/
oplhttp://www.openlinksw.com/schema/attribution#
n13http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtLinkInf05.
n34http://ods.openlinksw.com/dataspace/%28NULL%29/wiki/ODS/
n28http://ods.openlinksw.com/dataspace/owiki#
n15http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtLinkInf11.
dchttp://purl.org/dc/elements/1.1/
rdfshttp://www.w3.org/2000/01/rdf-schema#
n9http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtLinkInf01.
n25http://rdfs.org/sioc/services#
n2http://ods.openlinksw.com/dataspace/owiki/wiki/ODS/
siocthttp://rdfs.org/sioc/types#
n14http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtLinkInf06.
n27http://ods.openlinksw.com/dataspace/person/owiki#
n17http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtLinkInf12.
n10http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtLinkInf02.
n22http://ods.openlinksw.com/dataspace/owiki/wiki/ODS/VirtINFLinkingObjects/sioc.
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n11http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtLinkInf07.
n24http://ods.openlinksw.com/dataspace/services/wiki/
n32http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtLinkInf13.
n33http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtWebHome.
n7http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtLinkInf03.
xsdhhttp://www.w3.org/2001/XMLSchema#
n12http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtLinkInf08.
n20http://ods.openlinksw.com/dataspace/dav#
n5http://ods.openlinksw.com/wiki/main/ODS/VirtINFLinkingObjects/VirtConductor.
siochttp://rdfs.org/sioc/ns#
Subject Item
n29:this
foaf:made
n2:VirtINFLinkingObjects
Subject Item
n24:item
n25:services_of
n2:VirtINFLinkingObjects
Subject Item
n28:this
sioc:creator_of
n2:VirtINFLinkingObjects
Subject Item
n6:ODS
sioc:container_of
n2:VirtINFLinkingObjects
atom:entry
n2:VirtINFLinkingObjects
atom:contains
n2:VirtINFLinkingObjects
Subject Item
n2:VirtINFLinkingObjects
rdf:type
atom:Entry sioct:Comment
dcterms:created
2017-06-13T06:02:31.236925
dcterms:modified
2017-06-29T07:33:51.039846
rdfs:label
VirtINFLinkingObjects
foaf:maker
n27:this n29:this
dc:title
VirtINFLinkingObjects
opl:isDescribedUsing
n22:rdf
sioc:has_creator
n20:this n28:this
sioc:attachment
n5:png n7:png n8:png n9:png n10:png n11:png n12:png n13:png n14:png n15:png n17:png n18:png n19:png n32:png n33:png
sioc:content
%VOSWARNING% %META:TOPICPARENT{name="VirtLinkRemoteTables"}% ---+ Linking Informix Database Objects (Tables, Views, and Stored Procedures) into Virtuoso ---++ Prerequisites * <b>Virtuoso Universal Server, Commercial Edition</b>%BR% Virtuoso Universal Server Release 6.x or later is recommended, optimally the latest version available.%BR%%BR% * <b>ODBC Driver for Informix</b>%BR% The Virtuoso Server uses an ODBC Driver for Informix to link in the Informix Schema Objects (Tables, Views, and Stored Procedures). The <b><nop>OpenLink Multi-Tier ODBC Driver for Informix</b> will be used in this document, and a functional ODBC Data Source Name (DSN) of <b><code><nowiki>inf10ma</nowiki></code></b> will be assumed to exist on the machine hosting the Virtuoso Server. Any ODBC compliant driver for Informix should work.%BR%%BR% * <b>Informix DBMS</b>%BR% A Informix DBMS hosting the required Schema Objects (Tables, Views, and Stored Procedures) needs to be available. This may be on any host which is TCP/IP accessible from the Virtuoso Server host. In this document, the Informix <b>stores_demo</b> sample database will be used to demonstrate the process.%BR%%BR% ---++ Steps 1 Load the HTTP-based Virtuoso User Interface in your browser. %BR%%BR%<a href="%ATTACHURLPATH%/VirtWebHome.png"><img src="%ATTACHURLPATH%/VirtWebHome.png" style="wikiautogen" width="600px" alt="" /></a>%BR%%BR% 1 Click the <b>Conductor</b> link in the left-side navbar, and log in as a user with DBA privileges, such as the default <b><code>dba</code></b> user. %BR%%BR%<a href="%ATTACHURLPATH%/VirtConductor.png"><img src="%ATTACHURLPATH%/VirtConductor.png" style="wikiautogen" width="600px" alt="VirtConductor.png" /></a>%BR%%BR% 1 Drill down to the <b>Databases</b> -> <b>External Data Source</b> -> <b>Data Sources</b> tab. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkInf01.png"><img src="%ATTACHURLPATH%/VirtLinkInf01.png" style="wikiautogen" width="600px" alt="VirtLinkInf01.png" /></a>%BR%%BR% 1 Locate the DSN for the desired remote data source (we're using <b><code><nowiki>inf10ma</nowiki></code></b> for this example). If not yet connected to the DSN, click <b>Connect</b>, and input your user credentials for the remote data source. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkInf02.png"><img src="%ATTACHURLPATH%/VirtLinkInf02.png" style="wikiautogen" width="600px" alt="VirtLinkInf02.png" /></a>%BR%%BR% 1 Once connected to the DSN, click the associated <b>Link objects</b> to get a list of available objects (tables, views, stored procedures). %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkInf03.png"><img src="%ATTACHURLPATH%/VirtLinkInf03.png" style="wikiautogen" width="600px" alt="VirtLinkInf03.png" /></a>%BR%%BR% 1 Locate and select the desired objects. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkInf04.png"><img src="%ATTACHURLPATH%/VirtLinkInf04.png" style="wikiautogen" width="600px" alt="VirtLinkInf04.png" /></a>%BR%%BR% * You can use the Catalog and Schema drop-down selectors and the table name test-entry box to construct a filter to shorten the visible list. * For this example, we'll choose the tables from the Informix sample <b>stores_demo</b> schema -- <b><code><nowiki>call_type</nowiki></code>, <code><nowiki>catalog</nowiki></code>, <code><nowiki>cust_calls</nowiki></code>, <code><nowiki>customer</nowiki></code>, <code><nowiki>items</nowiki></code>, <code><nowiki>manufact</nowiki></code>, <code><nowiki>msgs</nowiki></code>, <code><nowiki>orders</nowiki></code>, <code><nowiki>state</nowiki></code>, <code><nowiki>stock</nowiki></code>, <code><nowiki>test</nowiki></code></b>. * When all desired objects are selected, click the <b>Link...</b> button. 1 Virtuoso will interrogate the remote data source to learn about primary keys, and present you with a default linkage setup. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkInf05.png"><img src="%ATTACHURLPATH%/VirtLinkInf05.png" style="wikiautogen" width="600px" alt="VirtLinkInf05.png" /></a>%BR%%BR% 1 You can adjust the Virtuoso catalog, schema/owner, and object identifiers to suit your goals. The <b>Set To All</b> button can be used to speed the process. In this example, we'll put all linked objects into the <b><code>informix</code></b> catalog, and the <b><code>stores</code></b> schema. We'll leave the object identifiers unchanged. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkInf06.png"><img src="%ATTACHURLPATH%/VirtLinkInf06.png" style="wikiautogen" width="600px" alt="VirtLinkInf06.png" /></a>%BR%%BR% * Sometimes a primary key is not reported properly, or you want to use a different key, either simple or compound. Click <b>Edit</b> next to the primary key you want to change, and select the columns that Virtuoso should use for the purpose -- %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkInf07.png"><img src="%ATTACHURLPATH%/VirtLinkInf07.png" style="wikiautogen" width="600px" alt="VirtLinkInf07.png" /></a>%BR%%BR% 1 When all are set as desired, click the <b>Link</b> button to link the objects into Virtuoso. <i>Virtuoso may take some time to complete this step,</i> depending on network infrastructure, DBMS load, etc. 1 The Link process will complete by listing the linked objects in the <b>Databases</b> -> <b>External Data Source</b> -> <b>External Linked Objects</b> tab. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkInf08.png"><img src="%ATTACHURLPATH%/VirtLinkInf08.png" style="wikiautogen" width="600px" alt="VirtLinkInf08.png" /></a>%BR%%BR% ---++ Confirmation and Testing ---+++ Working with External Linked Objects (Tables, Views, and Stored Procedures) 1 Linked object are shown in the <b>Databases</b> -> <b>External Data Source</b> -> <b>External Linked Objects</b> tab. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkInf08.png"><img src="%ATTACHURLPATH%/VirtLinkInf08.png" style="wikiautogen" width="600px" alt="VirtLinkInf08.png" /></a>%BR%%BR% 1 Clicking the hyperlinked <b>Local Name</b> of the <b>External Linked Objects</b> will load the Virtuoso <b>Interactive SQL</b> (iSQL) HTTP interface (in a new browser tab or window) with a default <b><code>SELECT *</code><b> SQL query. For instance, clicking on <b><code>informix.stores.customer</code></b> brings -- %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkInf09.png"><img src="%ATTACHURLPATH%/VirtLinkInf09.png" style="wikiautogen" width="600px" alt="VirtLinkInf09.png" /></a>%BR%%BR% 1 Click the <b>Execute</b> button to run the query. Virtuoso will retrieve the results from the remote table. <i><b>Note:</b> By default, iSQL will "<b>Show no more than 100 rows </b>." You can change this value as desired.</i> %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkInf10.png"><img src="%ATTACHURLPATH%/VirtLinkInf10.png" style="wikiautogen" width="600px" alt="VirtLinkInf10.png" /></a>%BR%%BR% ---+++ Working with SQL Database Objects (Tables, Views, and Stored Procedures) 1 Linked objects are also visible through the <b>Database</b> -> <b>SQL Database Object</b> tab, just as if they were local Virtuoso data. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkInf11.png"><img src="%ATTACHURLPATH%/VirtLinkInf11.png" style="wikiautogen" width="600px" alt="VirtLinkInf11.png" /></a>%BR%%BR% 1 Simply drill down to the Catalog you set while linking -- %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkInf12.png"><img src="%ATTACHURLPATH%/VirtLinkInf12.png" style="wikiautogen" width="600px" alt="VirtLinkInf12.png" /></a>%BR%%BR% 1 As you might expect, clicking on any of the <b>Action</b> links will reveal the table definition, indexes, triggers, constraints, or privileges. For example, clicking <b>Definition</b> for <b><code>informix.stores.orders</code></b> -- %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkInf13.png"><img src="%ATTACHURLPATH%/VirtLinkInf13.png" style="wikiautogen" width="600px" alt="VirtLinkInf13.png" /></a>%BR%%BR% ---++ Related * [[VOSSQL2RDF][Mapping SQL Data to Linked Data Views]] * [[VirtInformixEntityFrameworkUsage][Using Microsoft Entity Frameworks to Access Informix Schema Objects (Tables, Views, and Stored Procedures) with Virtuoso]] CategoryDocumentation CategoryVirtuoso CategoryDotNET CategoryEntityFrameworks CategoryWebSite
sioc:id
d1f8a70979c012cb804a4b5ed91873fa
sioc:link
n2:VirtINFLinkingObjects
sioc:has_container
n6:ODS
n25:has_services
n24:item
atom:title
VirtINFLinkingObjects
sioc:links_to
n2:CategoryWebSite n2:CategoryDocumentation n34:CategoryEntityFrameworks n34:VirtInformixEntityFrameworkUsage n2:CategoryVirtuoso n34:VOSSQL2RDF n34:CategoryDotNET
atom:source
n6:ODS
atom:author
n29:this
atom:published
2017-06-13T06:02:31Z
atom:updated
2017-06-29T07:33:51Z
sioc:topic
n6:ODS
Subject Item
n20:this
sioc:creator_of
n2:VirtINFLinkingObjects