Exercise: PI ODBC Driver Configuration

Document created by kduffy on Sep 25, 2018Last modified by kduffy on Jul 2, 2019
Version 13Show Document
  • View in full screen mode

Objective: The goal of this exercise is to demonstrate understanding of how to set certain parameters at the connection level for PI ODBC Driver connections. Since the PI ODBC Driver routes its connections through a PI SQL Data Access Server, which then uses either PI OLEDB Enterprise to communicate with an AF Server or the PI OLEDB Provider to communicate with a PI Data Archive, some of the configurations are done at the provider level and some at the ODBC driver level.

 

Approach:

Using the following resource:

  • Not authorized to view the specified discussion 2656

As well as these additional resources:

 

Problem Statement:

Configure an ODBC DSN for the following scenarios:

 

1. A 32-bit application routing through a PI SQL DAS named PISQLDAS01 using explicit login, connecting to a PI Data Archive named "PISRV01" using explicit login. The PI user is "OledbUsers" and the password is "5q1i5|=v|\|"; the domain username is "DomainOledbUsers" and password "5q1i5|=v|\|".

 

2. A 32-bit application routing through a PI SQL DAS named PISQLDAS01, connecting to a PI AF Server named "AFSRV01" using Windows explicit login. The Windows domain username is "OledbUsers" and password is "5q1i5|=v|\|".

 

3. A 64-bit application routing through a PI SQL DAS named PISQLDAS02, connecting to a PI Data Archive named "PISRV02" passing the user's context from start to finish via SSPI, setting the only allowed protocol for communication from the ODBC driver to the PI SQL DAS to HTTPS.

 

4. A 64-bit application routing through a PI SQL DAS named PISQLDAS02, connecting to a PI AF Server named "AFSRV02" passing the user's context from start to finish via SSPI, prioritizing HTTPS over NetTcp for communication from the ODBC driver to the PI SQL DAS to HTTPS.

 

5. A 32-bit application routing through a PI SQL DAS named PISQLDAS03, connecting to a PI Data Archive named "PISRV03" passing the user's context from start to finish via SSPI, disabling asynchronous PISDK calls, and establishing stateless connections between the ODBC driver and the PI SQL DAS.

 

6. A 32-bit application routing through a PI SQL DAS named PISQLDAS03, connecting to a PI AF Server named "AFSRV03" passing the user's context from start to finish via SSPI, and when an error message is encountered for a value, it's embedded into that cell in the result set instead of erroring the query. Lastly, the application cannot parse guid data types, so all guids will need to be returned as a string data type.

 

Have questions? Ask the community

When you are ready, compare your answers with the Solution: PI ODBC Driver Configuration

Attachments

    Outcomes