1. Data Virtualization Demoette… ADO.NET Client
Hello, and welcome to the Demoette series for Cisco Information Server, or CIS. Demoettes are brief instructional videos that demonstrate specific features of CIS.
In this Demoette, we discuss connecting as a client to CIS via ADO.NET.

2. Agenda What is it and why does it matter? A basic demo Summary
Here is our agenda.
We begin by defining ADO.NET client connectivity to CIS and outlining its importance for our customers.
Next we walk through a very basic demo of ADO.NET connectivity.
Finally, we summarize the contents of this demoette.

3. Agenda What is it and why does it matter? A basic demo Summary
Let’s begin by discussing what ADO.NET connectivity is, and why it’s important for our customers.

4. What is it? ADO.NET Client Connectivity to CIS ActiveX Data Object
.NET software library
Provides access to data sources
ADO stands for ActiveX Data Object. It is a Microsoft .NET software library that provides general-purpose access to data sources.

5. Why does it matter? ADO.NET Client Connectivity to CIS
Enables .NET developers to write managed code for data access
May be a required access technique for some enterprises
ADO.NET connectivity to CIS is important for many of our customers. It enables .NET developers to write data access code that is managed by the .NET framework. For customers who have embraced .NET, ADO.NET may be a required access method to CIS.

6. Agenda What is it and why does it matter? A basic demo Summary
Next, let’s walk through a very basic demo of ADO.NET connectivity to CIS.

7. Demo: Here is the business problem…
CIS
Here is the business problem that we illustrate in this demo. We have created a CIS federated view from underlying physical data sources. A business analyst wants to consume this view into an application that uses ADO.NET to access data. We will use ADO.NET to enable client access to CIS.

8. Demo: Install ADO.NET Driver for CIS
To begin, we must install the CIS ADO.NET driver on the client’s machine.
<CLICK> The driver installation program is found in the CIS installation directory, under apps | ADO.NET

9. Demo: Install ADO.NET Driver for CIS
We execute the driver installation program…
<CLICK> … and follow the steps…
<CLICK> … to complete the installation.

10. Demo: Configure ADO.NET Client
Now we are ready to test connectivity with an ADO.NET client. Use the simple test client that is available in the additional resources that accompany this demoette. Note that this test client is not part of the CIS product set. Here we see a sample of the README file that comes with this client and explains how it is configured.

11. Demo: Configure ADO.NET Client
As the README explains, configuration of this client involves modifying a text file named conn_info.
<CLICK> In this file, we must specify the host, port, user, password, domain, and CIS virtual database name. All other parameters may typically remain at their default values.

12. Demo: Run ADO.NET Client
The client application requires no installation. We simply double-click the executable, and it asks for a SQL query.

13. Demo: Run ADO.NET Client
We enter a simple query that asks for the number of rows on a virtual table.

14. Demo: Run ADO.NET Client
The result is returned, and we have verified that ADO.NET connectivity to the CIS instance is working. Our demo is complete.

15. Agenda What is it and why does it matter? A basic demo Summary
Let’s summarize what we have seen in this presentation.

16. Summary ADO.NET Client Connectivity to CIS ActiveX Data Object
.NET software library
Provides access to data sources
ADO stands for ActiveX Data Object. It is a Microsoft .NET software library that provides general-purpose access to data sources.
ADO.NET connectivity to CIS is important for many of our customers. It enables .NET developers to write data access code that is managed by the .NET framework. For customers who have embraced .NET, ADO.NET may be a required access method to CIS.
Thank you.

17. TOMORROW starts here.