MicroStation V8i based configurations, made up of configuration files and variables, were typically referred to as a “Workspace”. A Workspace was composed of Users and Projects. The MicroStation CONNECT Edition is still made up of configuration files and configuration variables, with the overall set of configuration information now referred to as Configuration. The MicroStation CONNECT Edition Configuration contains the WorkSpace and WorkSet components.
In MicroStation V8i, the primary grouping of directory structure, files and associated data was referred to as a "Project". In the MicroStation CONNECT Edition this has changed. That grouping is now referred to as a "WorkSet. This blog post will discuss a few different ways to migrate “Project”(s) to WorkSet”(s).
Migrate Using Configuration Migration
Configuration Migration in the MicroStation CONNECT Edition provides the ability to bring forward, or upgrade, MicroStation V8i based Users and Project combinations. There are two main uses for this tool. One is using the default MicroStation V8i Workspace location, and the other is to browse to an external location.
Configuration Migration can be used to upgrade a default Workspace location in-place. Configuration Migration does not change the location of V8i data such as DGN files and the workspace standards. Configuration Migration creates the MicroStation CONNECT based *.cfg, for the WorkSpace, the *.cfg used for the WorkSet, and the “dgnws”. It simply creates files that link the MicroStation CONNECT Edition to the existing V8i based User and Project. Configuration Migration is located on the WorkSpace drop-down on the Work Page. Configuration Migration will display the location and path to the Workspace location of the MicroStation V8i based products. From there you can select the User and Project combination and define where the new WorkSpace and WorkSet should be located.
Configuration Migration can also be used to browse to an external location to upgrade a Workspace and Project. Again, this migration is done in place, with the MicroStation CONNECT Edition only creating *.cfg, for the WorkSpace, the *.cfg used for the WorkSet, and the “dgnws”. It simply creates files that link the MicroStation CONNECT Edition to the existing V8i based User and Project. Configuration Migration is located on the WorkSpace drop-down on the Work Page. From there you can select Browse and select the location of the User and Project combination and define where the new WorkSpace and WorkSet should be located. For this to function correctly, you must be using standard workspace folder naming conventions, meaning a Workspace directory with subdirectories of Projects and Users. If the directories were named anything else such as, Clients and Types, the Migration Wizard will not recognize them as Workspace directories.
Note : In some cases the paths found in the original PCF or UCF may be incorrect. Therefore, the Configuration Migration may function, but the resultant *.cfg files are only as good as their original source. If the new WorkSpace and WorkSet do not function correctly, the first thing to check is the validity of the WorkSpace configuration file located in the folder \Configuration\WorkSpaces\*.cfg, checking the variable _USTN_WORKSPACEROOT. Ensure it points to the correct folder location. The second thing to check is the validity of the WorkSet configuration file located in the folder \Configuration\WorkSpaces\WORKSPACE_NAME\WorkSets\*.cfg, checking _USTN_WORKSETROOT to verify it is pointed to the root of the WorkSet.
Migrate Projects Manually
The process of manually migrating a “Project” to a “WorkSet” involves copying and re-naming existing folders and editing the configuration file. Here are some simple steps to accomplish this.
Upgrade Projects via Key-In
“Manual” migrations may be fine when you only have a handful of Projects that need to be converted to WorkSets. However, in most cases, many more projects are managed and manually migrating these would be quite a chore. The process can be automated. Here are some simple steps to accomplish this.
Note : Rather than open an existing WorkSet and Design, you could have created a “temporary” or “dummy” WorkSet for this task, and then remove it after the V8i based Projects are migrated to MicroStation CONNECT Edition WorkSets. The file that you open is unimportant. However, the correct WorkSpace must be selected. The WorkSpace that the WorkSets are created in is used to sets configuration variables.
The keyin “project upgradealltoworkets” completes several different tasks. It creates a WorkSet configuration file ”.cfg” from each “.pcf” file. It then creates a “.dgnws” in the location defined by _USTN_WORKSETDGNWS. The variable _USTN_PROJECTDESCR is removed (this variable is replaced by the WorkSet property “Description” stored in the “.dgnws”. It also updates variables that contain the string “_USTN_PROJECTDATA” replacing this with“_USTN_WORKSETROOT”. A Sheet Index is also created in the *.dgnws.
Translated German Wiki article:Migration von V8i-Projekten auf MicroStation CONNECT WorkSets