Control Architect now supports new document Server technology named MongoDB for maintaining configuration files. This Server technology is installed when you install Control Architect. This new document Server will maintain the thousands of configuration files that in the past had to be maintained and organized in your local file system. The topics below will provide information that will help guide you in migrating to the new Server technology.
Existing MRU Project references
The existing MRU Project reference menu may still show references to their folder paths in your local file system as indicated below:
Project references that include a folder separation character '\' are no longer accessible and will fail to open. In the example above the project reference F:\FHR\Boilder\BLR_20170111 is invalid. The new Project reference format is also visible above where the reference is formatted using the new ':' notation as in HCU2:HCU2_20161010 where the item to the left of the ':' separator char is the Database name (typically the PKS Server or process Unit name) and the item to the right of the ':' separator char is the Collection name (typically a version export from PKS Server).
Right mouse-click on any invalid project reference and choose the menu item Remove this item from list to remove the invalid project reference.
As you migrate your existing projects to the Server you should manually remove the original folder path type reference.
Existing PKS Configuration files
When migrating to the new document Server technology it is no longer necessary to save uncompressed PKS Server exported XML configuration files in your local file system. During import to the Server all required configuration type files are copied to the specified Server Database:Collection. These configuration files include *.cnf.xml, *.bcd, and other file types associated with CAB and Template types. It is recommended that you maintain an archive file (compressed) that was exported from the PKS Server. The Server import function can read archive file types for importing of configuration type data.
Existing HMIWeb Process Graphic files
Unlike PKS configuration files, HMIWeb graphic files at this time are not stored to the document Server. You are still required to maintain these graphic files on your local file system. During import of your HMIWeb graphic files, the graphic files are analyzed and a graphic Asset model is generated and stored to the document Server. No graphic files are currently stored to the Server. This inconsistency exists because of the need to read the graphic data and shape type content files that typically make up a process graphic when viewing the graphic in a Browser view.
Old Project reference path
The obsolete project reference indicated the folder path where your configuration files were stored.
