1. Data Virtualization Community Edition
Tutorial: Publishing Virtual Databases
Hello, and welcome to the Tutorial Series for Cisco Information Server, or CIS. In this tutorial, we show how to Publish Virtual Databases.

2. For more details… Resources: Additional information: Archives
Documentation
Training
Resources:
Archives
Data files
Tutorial Document
Note that Tutorials are NOT meant to be comprehensive training modules. Instead, they demonstrate a very basic use case that can be built quickly and easily.
However, the Community Edition Knowledge Base contains additional information that will help you learn more and go deeper. Additional resources in the Knowledge Base include:
<CLICK> Resources used to build the tutorial, such as Data Virtualization Archive files, data source files, and a document version of this tutorial.
<CLICK> Additional information, including documentation and training materials.

3. Agenda What is it and why does it matter? How-to Summary
Here is our agenda.
We begin by defining Publishing and outlining its importance in Data Virtualization projects.
Next we demonstrate the basics of Publishing Virtual Databases.
Finally, we summarize the contents of this tutorial.

4. Agenda What is it and why does it matter? How-to Summary
Let’s begin by discussing what Publishing is, and why it is important for Data Virtualization.

5. What is it?
Publishing
Makes CIS resources accessible to authorized consumers
Accessible as a Database via JDBC, ODBC, ADO.NET, OData
Accessible as Web Services via REST, SOAP
Many resource types may be published
Data Virtualization developers use CIS Studio to create virtual views, procedures, transformations, and other types of resources. By default, these resources are not accessible to data consumers. Publishing is the act of making CIS resources accessible to authorized consumers. We can choose to Publish resources as Virtual Databases, as Web Services, or both. Virtual Databases can be accessed by any client tool that connects via JDBC, ODBC, ADO.NET, or OData protocols. Published Web Services are accessible via REST and SOAP protocols.
In this introductory demo we will concentrate on publishing virtual views, which is the most common use case for publishing. However, many other types of resources may be published, including Procedures, Transformations, Tables from physical data sources, and even entire physical databases.

6. Why does it matter? Publishing Simplifies Enterprise data access
Hides Enterprise data complexity
Users leverage tools of choice
Publishing is an essential capability for Data Virtualization, because it makes virtualized data accessible to data consumers. Virtual databases provide a simplified “front door” to all data in the enterprise, while hiding the complexity of the many disparate physical data sources in the Enterprise.
Publishing as a database is important because it presents data in a format that can be accessed by all data visualization tools. This means that data consumers can continue to use their data visualization tools of choice to consume virtualized data.

7. Agenda What is it and why does it matter? How-to Summary
Next, let’s walk through the basic steps of Publishing a Virtual Database.

8. Here is the business problem…
Data Consumers
Here is the business problem we illustrate in this tutorial.
<CLICK> CIS Developers access many different physical data sources…
<CLICK> To produce federated virtual views of data.
<CLICK> However, these views are only accessible within the CIS Studio development environment. They are not visible to data consumers using other data visualization tools.
<CLICK> To make these virtual views accessible to data consumers, we will publish them into a virtual database. This virtual database presents itself as an ANSI-standard SQL database, and accepts client connections from any tool that can use JDBC, ODBC, ADO.NET, or Odata protocols.

9. Let’s get started…
We’re now ready to begin. We’re going to publish the Virtual View named CompositeView from the CIS Examples folder, as shown here.

10. Publish the View
Right-click CompositeView and select Publish.

11. Publish the View
As the dialog box shows, I have already published several virtual databases. I could publish to one of these, but for this example let’s create a new virtual database.
<CLICK> Click Databases to indicate that you do not want to use an existing virtual database.
<CLICK> Now click Add Composite Service.
<CLICK> Give the Service a Name.

12. Publish the View The new Virtual Database is created.
<CLICK> Now the Add Catalog and Add Schema buttons are enabled. These are optional. However, if you want clients to connect via ODBC, be sure to define at least a catalog. The ODBC protocol requires a catalog to be present. For this example…
<CLICK> … we’ll define a Catalog…
<CLICK> … and a Schema.

13. Publish the View
The Catalog and Schema are added to the Virtual Database.
<CLICK> … Optionally, you can change the name of the published view. Click OK…
<CLICK> and the View is added to the Schema.

14. Verify the Published View
Now you can open the published View and examine its column names and data types.
<CLICK> Click Show Contents…
<CLICK> … to bring back a small sample of the data. Our published View is working correctly.

15. Publish to an Existing Virtual Database
Let’s publish a second view, in order to show how to add a View to an existing virtual database. Create a new View in a folder of your choice.
<CLICK> Again, we’ll use the Composite View as our example, but you can use any resource you like. Drag it onto the View canvas and define the projection as you would for any View.
<CLICK> Right-click the new View and select Publish.

16. Publish to an Existing Virtual Database
Now, instead of creating a new Virtual Database, simply select the schema we created earlier.
<CLICK> Optionally, change the name for the published View, and click OK.

17. Publish to an Existing Virtual Database
The new view is added to the Virtual Database. You can open it and examine it just as we did before.

18. Changing a Published Resource
Finally, let’s see what happens as we make changes to published resources. Open the view you created for the last example. Don’t open the Published table in the Virtual Database, but open the view you published in your development folder.
<CLICK> Change the View, as shown here, and save your work.

19. Changing a Published Resource
Now open the published view in the virtual database.
<CLICK> Note that our change is reflected in the Columns list…
<CLICK> … and in the returned data. Resource changes are automatically propagated. No re-publish is required.

20. Changing a Published Resource
Open the lineage diagram to verify the lineage of the change we made.
<CLICK> The new column was added in the View we created based on CompositeView, and was propagated from there to the published view.
We have seen how to publish a View to a new virtual database, how to add a view to an existing virtual database, and we have examined the effects of changes to resources. Our tutorial is complete.

21. Agenda What is it and why does it matter? How-to Summary
Let’s summarize what we have seen in this tutorial.

22. Summary: Definition Publishing
Makes CIS resources accessible to authorized consumers
Accessible as a Database via JDBC, ODBC, ADO.NET, OData
Accessible as Web Services via REST, SOAP
Many resource types may be published
Data Virtualization developers use CIS Studio to create virtual views, procedures, transformations, and other types of resources. By default, these resources are not accessible to data consumers. Publishing is the act of making CIS resources accessible to authorized consumers. We can choose to Publish resources as Virtual Databases, as Web Services, or both. Virtual Databases can be accessed by any client tool that connects via JDBC, ODBC, ADO.NET, or OData protocols. Published Web Services are accessible via REST and SOAP protocols.
In this introductory demo we concentrated on publishing virtual views, which is the most common use case for publishing. However, many other types of resources may be published, including Procedures, Transformations, Tables from physical data sources, and even entire physical databases.

23. Summary: Benefits Publishing Simplifies Enterprise data access
Hides Enterprise data complexity
Users leverage tools of choice
Publishing is an essential capability for Data Virtualization, because it makes virtualized data accessible to data consumers. Virtual databases provide a simplified “front door” to all data in the enterprise, while hiding the complexity of the many disparate physical data sources in the Enterprise.
Publishing as a database is important because it presents data in a format that can be accessed by all data visualization tools. This means that data consumers can continue to use their data visualization tools of choice to consume virtualized data.

24. Summary: Key Take-aways
Publishing
You can create as many Virtual Databases as you like
Catalogs and Schemas are optional. However, Catalogs are required for ODBC clients.
Changes are automatically propagated to published resources
As you work with Publishing in CIS, keep these key take-aways in mind.
You can create as many virtual databases as you like, and you can add resources to any of them.
Optionally, you can create catalogs and schemas for your virtual databases. Note, though, that ODBC clients require the presence of a Catalog.
When you change an underlying resource, the published dependent resource is automatically changed.

25. Summary: What’s next?
Use your knowledge to make your resources available to data consumers
Leverage your knowledge to publish other types of resources
Learn to connect external clients to Virtual Databases
After completing this tutorial, you are ready to make your work available to external clients.
Use your learning from this tutorial to publish virtual views for end-user consumption.
Leverage your knowledge to publish other types of resources, such as Procedures, Transformations, and physical tables.
Use other Tutorials to learn how to connect client tools to your Virtual Databases using protocols such as JDBC, ODBC, ADO.NET, and OData.
Thank you.