Hi and welcome back to the PI SQL online course, in this video we're going to show how to install
configure and test functionality of PI SQL client and PI SQL data access server real-time query
processor or PI SQL DAS RTQP. If you remember from a previous video the RTQP data flow consists of a
server side component and a client side component. The server side component is installed as part of
the AF server installation kit and the client side component is a separate installation. Each
of these kits can be obtained from the tech support download site which I've already done.
Let's begin by installing the RTQP query engine component from the AF Services install kit.
This machine already has the AF server itself installed so I'm going to modify
the installation to include the RTQP query engine. Under individual features you can see PI SQL data
access server RTQP engine, the reason that the RTQP query engine installation is bundled with
the AF server is because both the AF application service and the RTQP query engine both speak
directly to the PI FD SQL database as the backend for the AF server. Because of this both services
are expecting the same version of the PI FD schema and therefore they must both be updated in tandem.
Click through the remainder of the installation. Great let's open up services and confirm that
the RTQP query engine has been installed. Here we see PI SQL data access server RTQP
engine and the services running. Next let's move on to the client side component of the
installation. I'm using the beta version this might look a little bit different for you if
you're using the production release. For the client side component of the installation you
can see we're going to install the OLEDB endpoints as well as PI SQL commander
lite. Now that both portions the installation are complete let's open up PI SQL commander.
You notice right away that we have a new item in the object Explorer called PI SQL client,
this section is going to contain all of your RTQP connections. Also notice that
unlike the other three sections PI SQL client is not pre-populated with a list
of known connections. Each connection is to an AF database in specific and once
connected to that connection will persist in the list of known PI SQL client connections.
Let's begin by creating our first connection to database one. Let's type in the name of
our AF server and AF database. We'll select test connection and click OK. We'll go into
more detail about the schema of the RTQP query engine in a future video so for now
let's just run a few queries to confirm that everything is working properly. Let's begin
by opening up PI System Explorer so that we can confirm what we see in the query
output from RTQP is what we should be seeing. Let's connect to database one.
Now let's expand the master schema, go into element tables and execute the element query,
right click execute predefined query. This is showing us one element and then as a test
element template for the template name. Let's confirm this in PI System Explorer.
Here we see the name is test element and a template is test element template. Great now
let's do a test of creating custom database objects. Let's right click on catalogs and
create template specific data model. Again we'll go in more detail about this in a future video,
for now let's just create one to make sure that everything is stored correctly. We'll create a new
catalog, as well as a new schema. We'll select test element template for the element template
type. We'll create an element view. Let's bring in both attributes and for now we're just looking at
the values so we'll uncheck all the other boxes. Great, we see the custom catalog we just created
so now let's expand it to see our schema, as well as our view. Let's execute the view. You notice
it returns one element as well as two attribute values, test attribute one is one, test attribute
two is two. Let's return to PI System Explorer and confirm that those are the correct values. Here we
see test attribute one is one, test attribute to is too. Great the query was successful.
Next thing I'd like to show is the configuration database , so let's connect to that now. Let's
expand out the elements and we see RTQP engine custom objects, the GUID, our catalog name,
our schema name and the name of our view. Going into detail about how everything is
stored in the configuration database is beyond the scope of this video but what I wanted to
point out is that all the configuration is stored server-side. What this means
is that one person can create something on their client machine then another person
can simply refresh their connection and they'll be able to see the new custom database object.
The last thing you'd like to show is the persistence of the PI SQL client connection
list. So let's close everything out and reopen PI SQL commander. Notice here that we have our
database one connection which I created in a previous session. This concludes the video on how
to install, configure and test the functionality of PI SQL client and PI SQL DAS RTQP.