INTRODUCTION
Part one of this series outlined the process of migrating data from an Enterprise database to a PGDB/FGDB. This post continues those instructions to also migrate those tables responsible for ArcFM™ functionality.
There are seventeen tables contained at the root of a Geodatabase that form the foundation of ArcFM™. The names of these tables are (of course) different, but they are all prefaced with “MM_”. Those knowledgeable to a bit of history know that “MM” stands for Miner and Miner, the original company behind ArcFM™.
EXPORT OF PROPERTIES FROM ENTERPRISE DATABASE
We first need to get the ArcFM™ Properties from the Enterprise Database. Conduct the following procedure:
- Log into the Enterprise database and export the ArcFM™ Properties as a XML file. With the connection made and highlighted, click the ArcFM™ XML Export tool on the ArcFM™ Toolbar (Figure 1).
- In the ArcFM™ XML Export GUI, select ArcFM™ Model Name Information, give it an export path, and choose Export (Figure 2).
- At a minimum, repeat for the following other properties AS SEPARATE XMLs: ArcFM™ Properties, ArcFM™ Relationship Class Info, ArcFM™ Snapping Information, and Domains.
- In the resultant Favorites GUI (Figure 4), highlight the system favorites and click the Export button. Save the XML to the same location as above.
CONSTRUCTION OF TABLES AND IMPORT OF PROPERTIES
We next need to prepare the FGDB (created in the previous post) to receive the exported properties. Conduct the following procedure:
- Log into the destination FGDB and highlight the connection.
- Click the Create/Update ArcFM™ Solution Tables button on the ArcFM™ Toolbar (Figure 5). This tool adds the MM_Tables to the Geodatabase.
- Click the Upgrade ArcFM™ Solution Database tool (Figure 6).
- Convert entire database to ArcFM™ Objects by clicking the ArcFM™ Solution Object Converter (Figure 7) with the connection selected.
We are now ready to start importing the properties exported from the Enterprise Database.
- Click the ArcFM™ XML Input tool (Figure 8).
- In the resultant Input GUI (Figure 9), choose the Overwrite option for the following XML file types: ArcFM™ Model Names, ArcFM™ Properties, ArcFM™ Relationship Classes (Make sure to verify results, because these often don’t work without a style sheet), and ArcFM™ Snapping.
- Import the domains, BUT choose the Keep Existing option. This will bring over all the super domains, as well as all the other unused domains.
MIGRATION OF STORED DISPLAYS
The final step (other than testing) is to migrate the desired stored displays. Stored displays save the data view’s layers, symbology, and scale rendering. The easiest way to do this is as follows:
- Within ArcMap, open each stored display, and save as separate ArcMap projects (*.mxd).
- Close down ArcMap.
- Open each created ArcMap project. When logging into ArcFM™, make sure to log into the FGDB.
- Save by choosing the Stored Items menu drop down and “Save As”.
- In the resultant GUI (Figure 10), choose Stored Display for Item Type, System option, and provide a Name.
- Click the OK button to save and dismiss the window.
- From within ArcCatalog, connect to the FGDB and click on the ArcFM™ Data Source Wizard (Figure 11).
- From within the wizard, click Next to the initial informative window.
- Choose Stored Displays option from the next window (Figure 12), and click Next.
- Choose the Set all data sources option (Figure 13), and click Next.
- Enter a path to the FGDB (Figure 14), and click Next.
- Click next to the warning window to proceed with the change in data source.
- Click OK to the final window.
That is it! Make sure to test thoroughly before providing to coworkers/contractors. That concludes the series for fear of losing a good thing. Classic movies with a third sequel (i.e. Child’s Play 3, RoboCop 3, and Ernest Goes to Jail) just didn’t match the previous Oscar-worthy performance of the actors and writers.
Comments? See that spot down at the bottom that says “Add new comment”? Do me a favor…add a new comment.
What do you think?