Migration

To launch the migration utility, select a server node and click on the toolbar. A new window called Migration Chart is displayed if there are any PI points belonging to PIBaGen 1.x on that Data Archive server and if they are not yet migrated. If the userint1 attribute for a PI point belonging to PIBaGen 1.x is set to 1, it is considered that the corresponding PIUnit is already migrated and is not loaded into the Migration Chart. The migration utility sets the userint1 to 1 during the migration process. Only those PIUnits that do not have the Error icon next to the configuration point can be migrated. If there is an error sign, the Migration Status column explains why the PIUnit cannot be migrated. See Migration errors in PI SMT for common errors that arise before and during migration. While the selected PIUnits are migrated, the migration utility follows these steps for each PIUnit:

• Rename the configuration module used by PI-BaGen 1.x to PIBaGen 1.x Configuration-Migrated.

• If the renaming process is successful, the PIUnit is considered to be migrated and userint1 for the PIBaGen 1.x PI point is set to 1.

• A new module is then added under the PIUnit with the name as Configuration Module Name.

• All the PIUnitBatch and PISubBatch configuration is then copied to the newly added Configuration Module.

• If PISubBatches are configured in PIBaGen 1.x, then each PIAlias in each PIModule under SubBatchSupport module represents one SubBatch in PIBaGen 2.x configuration. Therefore, one PIModule with the name format as H:P is added, where H stands for the PIHeading name and P stands for the PI point name (data source for that PIAlias). The same PI point is also used for deriving the PISubBatch name.

• The ActivePoint Behavior is set to Continuous because the Step behavior for SubBatches in PIBaGen 1.x is now behaved like the new Continuous option.

• The PIUnit is registered if the corresponding PIBaGen 1.x PI point had the Scan attribute set to 1. In such a case, the PI point Scan attribute is set to zero after registering the PIUnit.

• If there are any errors during the migration process, the corresponding row is highlighted and the error messages are shown at the bottom of the Migration Chart and are also sent to the log file. If the migration is successful, the Migration Status column shows Migration Completed.