Prepare batch data sources and consumers for migration

To successfully transition your environment from using the PI Batch Database and PI Batch Subsystem, you need to prepare all of your batch data sources and consumers, or devise alternate solutions for supporting your batch needs using PI Event Frames.

Note: If you plan to use RtReports with event frames, you need to use RtReports version 4.0.

First, inventory how your current batch system is constituted. You'll need to take actions for each batch data source and consumer to get it ready to switch to event frames.

1. For each Data Archive server that you plan to migrate, take an inventory of the current sources and consumers of PI batch data.

   Sources of batch data might include:

   • PI Event File (EVT) interfaces

   • PI BaGen (PI Batch Generator interfaces)

   • Batch interfaces 1.x, 2.x, 3.x, and 4.x

   • Your proprietary interfaces

   • PI Batch Subsystem

     Consumers of batch data might include:

   • PI BatchView PI ProcessBook add-in

   • PI BatchView Microsoft Excel add-in (used with PI DataLink)

   • RtReports

     PI WebParts Batchview Control

   • PI OLEDB

   • Your in-house PI-SDK batch applications

   • Code you have implemented within PI ProcessBook displays

   • Third-party applications

2. Prepare your batch data sources. Your site will be ready to migrate to event frames after you prepare each batch data source and consumer, as described here.

   Caution: When you start the migration, the Batch Database becomes read-only, therefore do not proceed with migration until you have identified effective ways of adapting each data source and consumer for event frame data, or devise alternate solutions for supporting your batch needs using PI Event Frames.

   After you initiate migration, most batch interfaces fail to create further PI batch database data. To continue generation of event frames after the migration, you must identify and update all data sources that support generating event frames. Newer versions of some interfaces, specifically batch interfaces version 4.0, automatically cut over from writing batch data to writing to the event frame database. For other interfaces, you must switch manually. Go to the Customer Portal for interfaces that are not listed here for which you need more information.

   Data source	Actions
   PI Event File (EVT) interface	See PI Event File (EVT) interface.
   PI BaGen interface	See PI BaGen interface.
   Batch interfaces 1.x, 2.x, 3.x	See Batch interfaces 1.x 2.x 3.x.
   Your proprietary interfaces	See Your proprietary interfaces.
   PI Batch Subsystem interfaces	See PI Batch Subsystem interfaces.

3. Prepare your batch data consumers.

   Consumer	Actions
   PI BatchView PI ProcessBook add-in	See PI BatchView PI ProcessBook add-in.
   PI BatchView Microsoft Excel add-in (used with PI DataLink)	See PI BatchView Microsoft Excel add-in (used with PI DataLink)
   RtReports	See RtReports.
   PI WebParts Batchview Control	See PI WebParts Batchview Control.
   PI OLEDB	See PI OLEDB.
   In-house PI SDK Batch applications	See In-house PI SDK Batch applications.
   Your code in PI ProcessBook displays	See Your code in PI ProcessBook displays.
   Third-party applications	Explore solutions offered by third-party vendors.