Project and library migration

Migrating a project and associated libraries from one version to the next one is usually done by starting the project with the new release and then shutting it down. Assuming the Windows user starting PcVue is granted Read and Modify permissions on the project and libraries folders, the project configuration is automatically updated to reflect changes in configuration element properties and file formats.

Depending on changes brought to the product, migrating to a newer version of PcVue can require changes that are not done automatically or that must be monitored for success. This topic describes the typical elements a person performing a migration is expected to look at and provides guidance for migration to specific versions that are known to require actions. Once you have read this introduction, this is probably the only topic in this documentation that you will read from bottom to top, starting at the section corresponding to the version you have been using until now, and stopping at the section corresponding to the version you are migrating to.

The product is designed and maintained with the goal of facilitating product updates and project upgrades. In all cases, migrating a project and associated library is an operation that does require attention. The success of a migration starts with proper preparation, test, and validation prior to putting the new release in production.

In those rare cases a feature change is not backward compatible, whenever possible a compatibility setting is added to enable the previous behavior:

1. Open the Application Explorer and select the topmost (Project) folder.
2. Select the Settings task. The Main Settings dialog opens. The compatibly settings are found in a folder of the same name.

If you start a project and libraries configured with an earlier version of PcVue, a dialog is displayed warning that once the project and libraries have been started with the current version, they may no longer be compatible with any earlier version.

Migration to Version 17 (or later)

Improvements related to cryptographic protection of projects and PcVue station hosts bring changes requiring an explicit migration of a project prior to starting it with a release of version 17 or later.

To migrate a project, you can use the Host Deployment Console, on an engineering or a test host:

1. Copy the project to migrate in a sub-folder of C:\ProgramData\ARC Informatique\PcVue 17\usr\
2. Open the Host Deployment Console as a user with Administrative privileges, a shortcut is available on the desktop and in the Programs menu.
3. In the left pane, click on Projects and check that your project is visible in the list.
4. In the left pane, click on Project migration, and select your project.
5. Click the Migrate button to start the migration process.
6. After a few seconds, a message is displayed indicating the end of the migration process.
   If the message indicates success, the project is migrated and can be started with the current product version.

Alternatively, you can use the ProjectUtility CLI:

1. Open a terminal as a user with Administrative privileges and go to the program files folder where PcVue is installed. By default, C:\Program Files\ARC Informatique\PcVue 17\Bin\
2. Copy the project to migrate in a sub-folder of C:\ProgramData\ARC Informatique\PcVue 17\usr\
3. Run the following command. Replace 'MyProject' with your own project folder.
   Copy

   ProjectUtility migrate "MyProject" user-directory

   If successful, the project is migrated and can be started with the current product version.

Once run successfully, from a cryptographic point of view, you have an unprotected project. Some files have been encrypted with a default cryptographic key, as a newly created project would be. The next step is to protect it before you resume a usual test and validation phase. See Protecting and deploying a project for more information about protecting your project and deploying it on a first host.

The Central project management feature that allows you to manage project and library versions is also subject to changes. It must now be set up by a Windows user with Administrative privileges. See How to manage project and library versions for more information.

Migration to Version 12 (or later)

The HDS database table structures changed in version 12.
If you are using database archiving with the HDS, refer to Overview of Database migration.

Migration to Version 11.2 (or later)

The HDS database table structures changed in version 11.2.
If you are using database archiving with the HDS, refer to Overview of Database migration.

In order to support both the B-OWS and B-AWS requirements, PcVue BACnet implementation was subject to a major rework in version 11.2. See the topic Using the BACnet configuration of a project configured with a previous version of PcVue for information about the migration path.

Migration to Version 11.0 (or later)

The shared libraries supplied on PcVue distribution media are subject to continuous improvement. In particular, a new set of libraries is supplied since version 11. Users with projects using the shared libraries of an earlier version must make sure they take the necessary backup steps before starting the migration process. If backups are available, the older libraries can simply be re-introduced once the new product version installation has taken place, using the procedure explained in the topic Backing up and restoring projects and libraries.

Migration to Version 10.0 (or later)

The HDS database table structures changed in version 10.0.
If you are using database archiving with the HDS, refer to Overview of Database migration.

Migrating from Version 2, 3 or 4

Projects created with the 16-bit versions of PcVue are generally compatible. Some of the drivers available in the 16-bit version are no longer available due to lack of support from the manufacturers. If in doubt, please contact technical support.

Migrating from DOS versions

Projects created with the DOS versions of the product are not directly compatible. However, a high percentage of the configuration information can be retrieved and the project converted using a migration utility.