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
n13http://ods.openlinksw.com/dataspace/person/dav#
dctermshttp://purl.org/dc/terms/
n14http://ods.openlinksw.com/dataspace/owiki/wiki/
n34http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtLinkPrs01.
atomhttp://atomowl.org/ontologies/atomrdf#
foafhttp://xmlns.com/foaf/0.1/
n4http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtLinkPrs02.
oplhttp://www.openlinksw.com/schema/attribution#
n11http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtWebHome.
n7http://ods.openlinksw.com/dataspace/%28NULL%29/wiki/ODS/
n32http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtLinkPrs03.
n21http://ods.openlinksw.com/dataspace/owiki#
dchttp://purl.org/dc/elements/1.1/
n33http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtLinkPrs04.
rdfshttp://www.w3.org/2000/01/rdf-schema#
n6http://ods.openlinksw.com/dataspace/owiki/wiki/ODS/VirtProgressLinkingObjects/sioc.
n8http://rdfs.org/sioc/services#
n25http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtLinkPrs05.
n2http://ods.openlinksw.com/dataspace/owiki/wiki/ODS/
siocthttp://rdfs.org/sioc/types#
n26http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtLinkPrs06.
n16http://ods.openlinksw.com/dataspace/person/owiki#
n23http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtLinkPrs07.
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n30http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtLinkPrs10.
n24http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtLinkPrs08.
n9http://ods.openlinksw.com/dataspace/services/wiki/
n29http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtLinkPrs09.
n27http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtLinkPrs11.
n28http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtLinkPrs12.
xsdhhttp://www.w3.org/2001/XMLSchema#
n31http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtConductor.
n18http://ods.openlinksw.com/dataspace/dav#
n10http://ods.openlinksw.com/wiki/main/ODS/VirtProgressLinkingObjects/VirtLinkPrs13.
siochttp://rdfs.org/sioc/ns#
Subject Item
n13:this
foaf:made
n2:VirtProgressLinkingObjects
Subject Item
n9:item
n8:services_of
n2:VirtProgressLinkingObjects
Subject Item
n21:this
sioc:creator_of
n2:VirtProgressLinkingObjects
Subject Item
n14:ODS
sioc:container_of
n2:VirtProgressLinkingObjects
atom:entry
n2:VirtProgressLinkingObjects
atom:contains
n2:VirtProgressLinkingObjects
Subject Item
n2:VirtProgressLinkingObjects
rdf:type
sioct:Comment atom:Entry
dcterms:created
2017-06-13T06:02:45.434541
dcterms:modified
2017-06-29T07:34:24.864215
rdfs:label
VirtProgressLinkingObjects
foaf:maker
n16:this n13:this
dc:title
VirtProgressLinkingObjects
opl:isDescribedUsing
n6:rdf
sioc:has_creator
n18:this n21:this
sioc:attachment
n4:png n10:png n11:png n23:png n24:png n25:png n26:png n27:png n28:png n29:png n30:png n31:png n32:png n33:png n34:png
sioc:content
%VOSWARNING% %META:TOPICPARENT{name="VirtLinkRemoteTables"}% ---+ Linking Progress / <nop>OpenEdge 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 Progress/<nop>OpenEdge</b>%BR% The Virtuoso Server uses an ODBC Driver for Progress/<nop>OpenEdge to link in the Progress/<nop>OpenEdge Schema Objects (Tables, Views, and Stored Procedures). The <b><nop>OpenLink Multi-Tier ODBC Driver for Progress/<nop>OpenEdge</b> will be used in this document, and a functional ODBC Data Source Name (DSN) of <b><code><nowiki>prs10_isports_rdf</nowiki></code></b> will be assumed to exist on the machine hosting the Virtuoso Server. Any ODBC compliant driver for Progress/<nop>OpenEdge should work.%BR%%BR% * <b>Progress/<nop>OpenEdge DBMS</b>%BR% A Progress/<nop>OpenEdge 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 Progress/<nop>OpenEdge <b>isports</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%/VirtLinkPrs01.png"><img src="%ATTACHURLPATH%/VirtLinkPrs01.png" style="wikiautogen" width="600px" alt="VirtLinkPrs01.png" /></a>%BR%%BR% 1 Locate the DSN for the desired remote data source (we're using <b><code><nowiki>prs10_isports_rdf</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%/VirtLinkPrs02.png"><img src="%ATTACHURLPATH%/VirtLinkPrs02.png" style="wikiautogen" width="600px" alt="VirtLinkPrs02.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%/VirtLinkPrs03.png"><img src="%ATTACHURLPATH%/VirtLinkPrs03.png" style="wikiautogen" width="600px" alt="VirtLinkPrs03.png" /></a>%BR%%BR% 1 Locate and select the desired objects. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkPrs04.png"><img src="%ATTACHURLPATH%/VirtLinkPrs04.png" style="wikiautogen" width="600px" alt="VirtLinkPrs04.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 Progress/<nop>OpenEdge sample <b>isports.PUB</b> schema -- <nowiki><b><code>Customer</code>, <code>DECTEST</code>, <code>Invoice</code>, <code>Item</code>, <code>Local-Default</code>, <code>Order</code>, <code>Order-Line</code>, <code>Ref-Call</code>, <code>Salesrep</code>, <code>State</code></b>.</nowiki> * 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%/VirtLinkPrs05.png"><img src="%ATTACHURLPATH%/VirtLinkPrs05.png" style="wikiautogen" width="600px" alt="VirtLinkPrs05.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>Progress10</code></b> catalog, and the <b><code>isports</code></b> schema. We'll leave the object identifiers unchanged. %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkPrs06.png"><img src="%ATTACHURLPATH%/VirtLinkPrs06.png" style="wikiautogen" width="600px" alt="VirtLinkPrs06.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%/VirtLinkPrs07.png"><img src="%ATTACHURLPATH%/VirtLinkPrs07.png" style="wikiautogen" width="600px" alt="VirtLinkPrs07.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%/VirtLinkPrs08.png"><img src="%ATTACHURLPATH%/VirtLinkPrs08.png" style="wikiautogen" width="600px" alt="VirtLinkPrs08.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%/VirtLinkPrs08.png"><img src="%ATTACHURLPATH%/VirtLinkPrs08.png" style="wikiautogen" width="600px" alt="VirtLinkPrs08.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>Progress10.isports.Order</code></b> brings -- %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkPrs09.png"><img src="%ATTACHURLPATH%/VirtLinkPrs09.png" style="wikiautogen" width="600px" alt="VirtLinkPrs09.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%/VirtLinkPrs10.png"><img src="%ATTACHURLPATH%/VirtLinkPrs10.png" style="wikiautogen" width="600px" alt="VirtLinkPrs10.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%/VirtLinkPrs11.png"><img src="%ATTACHURLPATH%/VirtLinkPrs11.png" style="wikiautogen" width="600px" alt="VirtLinkPrs11.png" /></a>%BR%%BR% 1 Simply drill down to the Catalog you set while linking -- %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkPrs12.png"><img src="%ATTACHURLPATH%/VirtLinkPrs12.png" style="wikiautogen" width="600px" alt="VirtLinkPrs12.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>Progress10.isports.Salesrep</code></b> -- %BR%%BR%<a href="%ATTACHURLPATH%/VirtLinkPrs13.png"><img src="%ATTACHURLPATH%/VirtLinkPrs13.png" style="wikiautogen" width="600px" alt="VirtLinkPrs13.png" /></a>%BR%%BR% ---++ Related * [[VOSSQL2RDF][Mapping SQL Data to Linked Data Views]] * [[VirtProgressEntityFrameworkUsage][Using Microsoft Entity Frameworks to Access Progress/OpenEdge Schema Objects (Tables, Views, and Stored Procedures) with Virtuoso]] CategoryDocumentation CategoryVirtuoso CategoryDotNET CategoryEntityFrameworks CategoryWebSite
sioc:id
b5bc5d45b04a3c4c4f8238ebabd1a45b
sioc:link
n2:VirtProgressLinkingObjects
sioc:has_container
n14:ODS
n8:has_services
n9:item
atom:title
VirtProgressLinkingObjects
sioc:links_to
n2:CategoryWebSite n7:VOSSQL2RDF n2:CategoryVirtuoso n7:CategoryEntityFrameworks n2:CategoryDocumentation n7:CategoryDotNET n7:VirtProgressEntityFrameworkUsage
atom:source
n14:ODS
atom:author
n13:this
atom:published
2017-06-13T06:02:45Z
atom:updated
2017-06-29T07:34:24Z
sioc:topic
n14:ODS
Subject Item
n18:this
sioc:creator_of
n2:VirtProgressLinkingObjects