As PI Developers, we are often required to bridge the gap between the PI Infrastructure and the customer requirements. A common task is developing solutions for storing "special case" or manually-entered data. Whilst the PI Server provides mechanisms for getting this data into PI, we cannot cater for every possible scenario. There will always be the need for custom development of some description.
Prior to the PR1 release of PI, developing these solutions was relatively straight forward. When PR1 was released (Jan 07), the concept of a Collective was introduced and somewhat complicated the task of persisting manual and special case data in PI. Now, instead of writing to one server, you will need to consider the Collective itself as well as each individual Collective member. Manual Entry/Special Case data is not as straight forward as it used to be.
To help clear up the concerns and misconceptions around Manual data Entry, the vCampus team are releasing a whitepaper on the ins-and-outs of Manual entry data in a High Availability (HA) environment. To help kick this off (and get some discussion/thinking started on the topic), I will be releasing a series of Blog Posts outlining the various key concepts covered in the whitepaper.
These posts will not replace the content of the whitepaper, they will enhance and demonstrate the concepts presented. And, for those busy people out there, they'll give you the abridged "Too Long, Didn't Read" (TLDR) version.
So, watch this space over the next few weeks, there will be plenty to see!
P.S. Don't forget to register for the PI Programming 101 Webinar on the 28th of May. You might be surprised by what you learn!