PI BaGen interface

Note: We recommend you install the latest version of PI EFGen (4.0.11.104, or later) before migrating, because 4.0.11.104, or later, have significant migration-related improvements.

You cannot use PI BaGen after migrating. Therefore, before you migrate, make PI EFGen (PI Event Frames Generator) ready to generate batch data in event frame format (but do not turn it on until after migration).

Note: PI EFGen has additional functionality compared to PI BaGen, so you might want to explore those features before you migrate to see if you want to take advantage of them.

Test using PI EFGen to produce data that is consistent with your existing PI BaGen interfaces. You can use the Converter tab in PI EFGen to migrate existing PI BaGen configurations to PI EFGen. Be certain to set PI BaGen compatibility mode. For more information, see PI Event Frames Generator.

Stop PI BaGen. Confirm that PIBaGen batches are completed and not open. If there are batches open, determine the best approach for closing these open batches.

After you have migrated your batch data, enable PI EFGen to generate batch context data in event frame format.

If you cannot find a time when you can run migration without in-progress batches, you can use a feature of PI EFGen to recover your in-progress batches. After migration, use PI EFGen historical recovery to recover these batches:

1. Note the date and time that you stop the PI BaGen Interface, just prior to migration.

2. Migrate your data.

3. After migration completes, start PI EFGen in Recovery mode so that PI EFGen recovers any batches that were open during migration. Set PI EFGen to recover from the earliest in-process batch.

   Go to the Customer Portal if you have questions about how best to configure these options.

   Note: Older versions of PI EFGen (3.0.20.567, and earlier) are not aware of migrated event frames, therefore, it is possible to have duplicate event frames in these cases. To avoid this problem, upgrade to PI EFGen 4.0.11.104, or later, before migrating.