Skip navigation
All Places > PI Developers Club > Blog > 2016 > February
2016

Our architecture for PI Web API Indexed Search relies on a Crawler that scans PI System databases for meta-data and builds an index to this information. The PI Web API provides REST services that deliver search results to clients. This works well but it's less than ideal if you want to create a cluster of PI Web API servers working together. Each PI Web API server needs to hold its own index, so it needs its own Crawler to build it. So, if you build a cluster with 3 members, then you will have 3 indexes and 3 Crawlers, all doing the same work.

 

In PI Web API 2016, we are launching a Community Technology Preview (CTP) of a Shared Index. This means that all members of a cluster will share the same index. It also means that only a single Crawler is necessary to scan the PI System databases. All search results returned to clients will be consistent regardless of which cluster member performs the search.

 

We have the Shared Index working but we don't have time in this release to create a proper administration tool. If you would like to build a cluster with a shared index, you will have to configure it manually. We will give you documentation on how to do this, of course. Let me know if you are interested!

We've made a minor change to the name of our upcoming PI OLEDB Enterprise release. We had been planning to release it in 2015 and call it 2015. We had to delay our release so our development team could focus on exposing data from the PI Integrator for Business Analytics through PI ODBC 2015. So, we now look forward to releasing PI OLEDB Enterprise 2016 around the time of OSIsoft User Conference 2016 in San Francisco. Here's a short list of enhancements:

  • Future Data support,
  • Hidden and Excluded AF Attribute support,
  • AF's delta time strings which means, for example, a monthly report will cover the calendar month and not just 30 days,
  • Support for Summaries as both Table-Valued Functions and Function Tables, and
  • UTC mode which causes all times as be represented in UTC. We have added functions to convert to and from local time.

This name change from 2015 to 2016 also affects the Classic provider: PI OLEDB Provider 2015 is now PI OLEDB Provider 2016.

Filter Blog

By date: By tag: