Linking Progress / OpenEdge Database Objects (Tables, Views, and Stored Procedures) into Virtuoso

Prerequisites

• Virtuoso Universal Server, Commercial Edition
  Virtuoso Universal Server Release 6.x or later is recommended, optimally the latest version available.
  
  
• ODBC Driver for Progress/OpenEdge
  The Virtuoso Server uses an ODBC Driver for Progress/OpenEdge to link in the Progress/OpenEdge Schema Objects (Tables, Views, and Stored Procedures). The OpenLink Multi-Tier ODBC Driver for Progress/OpenEdge will be used in this document, and a functional ODBC Data Source Name (DSN) of prs10_isports_rdf will be assumed to exist on the machine hosting the Virtuoso Server. Any ODBC compliant driver for Progress/OpenEdge should work.
  
  
• Progress/OpenEdge DBMS
  A Progress/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/OpenEdge isports sample database will be used to demonstrate the process.
  
  

Steps

1. Load the HTTP-based Virtuoso User Interface in your browser.
   
   
   
   
2. Click the Conductor link in the left-side navbar, and log in as a user with DBA privileges, such as the default dba user.
   
   
   
   
3. Drill down to the Databases -> External Data Source -> Data Sources tab.
   
   
   
   
4. Locate the DSN for the desired remote data source (we're using prs10_isports_rdf for this example). If not yet connected to the DSN, click Connect, and input your user credentials for the remote data source.
   
   
   
   
5. Once connected to the DSN, click the associated Link objects to get a list of available objects (tables, views, stored procedures).
   
   
   
   
6. Locate and select the desired objects.
   
   
   
   
   • 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/OpenEdge sample isports.PUB schema -- Customer, DECTEST, Invoice, Item, Local-Default, Order, Order-Line, Ref-Call, Salesrep, State.
   • When all desired objects are selected, click the Link... button.
7. Virtuoso will interrogate the remote data source to learn about primary keys, and present you with a default linkage setup.
   
   
   
   
8. You can adjust the Virtuoso catalog, schema/owner, and object identifiers to suit your goals. The Set To All button can be used to speed the process. In this example, we'll put all linked objects into the Progress10 catalog, and the isports schema. We'll leave the object identifiers unchanged.
   
   
   
   
   • Sometimes a primary key is not reported properly, or you want to use a different key, either simple or compound. Click Edit next to the primary key you want to change, and select the columns that Virtuoso should use for the purpose --
     
     
     
     
9. When all are set as desired, click the Link button to link the objects into Virtuoso. Virtuoso may take some time to complete this step, depending on network infrastructure, DBMS load, etc.
10. The Link process will complete by listing the linked objects in the Databases -> External Data Source -> External Linked Objects tab.
    
    
    
    

Confirmation and Testing

Working with External Linked Objects (Tables, Views, and Stored Procedures)

1. Linked object are shown in the Databases -> External Data Source -> External Linked Objects tab.
   
   
   
   
2. Clicking the hyperlinked Local Name of the External Linked Objects will load the Virtuoso Interactive SQL (iSQL) HTTP interface (in a new browser tab or window) with a default SELECT * SQL query. For instance, clicking on Progress10.isports.Order brings --
   
   
   
   
3. Click the Execute button to run the query. Virtuoso will retrieve the results from the remote table. Note: By default, iSQL will "Show no more than 100 rows ." You can change this value as desired.
   
   
   
   

Working with SQL Database Objects (Tables, Views, and Stored Procedures)

1. Linked objects are also visible through the Database -> SQL Database Object tab, just as if they were local Virtuoso data.
   
   
   
   
2. Simply drill down to the Catalog you set while linking --
   
   
   
   
3. As you might expect, clicking on any of the Action links will reveal the table definition, indexes, triggers, constraints, or privileges. For example, clicking Definition for Progress10.isports.Salesrep --
   
   
   
   

Related

• Mapping SQL Data to Linked Data Views?
• Using Microsoft Entity Frameworks to Access Progress/OpenEdge Schema Objects (Tables, Views, and Stored Procedures) with Virtuoso?

CategoryDocumentation CategoryVirtuoso CategoryDotNET? CategoryEntityFrameworks? CategoryWebSite