Exercise: GetEASnap for PI JDBC Driver

Document created by kduffy on Sep 25, 2018Last modified by jkim on Nov 7, 2018
Version 5Show Document
  • View in full screen mode

Objective: The goal of this exercise is to demonstrate understanding of how to work with the GetEASnap command line utility.

 

Notes about the example environment:

  • The PI SQL DAS (OLEDB) service is installed locally to the PI JDBC Driver, so it can be referred to as "localhost"
  • The AF Server name is AFSRV01, and it has the NuGreen database imported
  • The user account being passed to the PI SQL DAS (OLEDB) service is student01
    • Note: this is a domain account that the PI OLEDB Enterprise then passes to the AF Server
  • This is a development/test environment, so the PI SQL DAS certificate is not validated. If this were a production environment, it would be very important to validate this certificate

 

Notes about your environment:

  • Perform this exercise on a client machine with the PI JDBC Driver installed
  • Replace the names of the AF Server, PI SQL DAS (OLEDB) server, AF Database, AF element, and domain user as necessary to get the connections to work
  • If you do not have the Nugreen database but would like to use it for this example, you can find it here

 

Problem Statement:

Given the following inputs and outputs from the example environment, use Read: How to Customize GetSnap and GetEASnap for PI JDBC Driver to answer the following questions:

 

  1. What was the full JDBC url being used in this case?
  2. What was the query being executed in this case?
  3. What would the query become if we only wanted to output the Safety attribute of the specified element?
  4. Implement the change in question 3 and recompile the GetEASnap utility into GetEASnapCustom. Demonstrate it working by rerunning the utility from the command prompt.

 

Have questions? Ask the community

When you are ready, compare your answers with the Solution: GetEASnap for PI JDBC Driver

Attachments

    Outcomes