Create Initial Extract Version and Initial Extract Geodatabase

  1. In ArcCatalog, you need to create the Initial Extract version from which the data is to be extracted. This version will likely be created on your Enterprise database. Add the Versions command to a toolbar:
  2. From the Customize menu, select Customize Mode.
  3. In the Commands tab, click Database connection in the Categories list.
  4. Click Versions in the Commands list and drag it to a toolbar. Close the Customize window.
  5. Log in (Connect) to an enterprise geodatabase and click the Versions tool you just added to the toolbar. The Geodatabase Administration window opens. In the Versions tab, select the DEFAULT version, right-click it and select New Version.
  6. On the New Version screen, type the name of your Initial Extract version (any name) and ensure it is private. Click OK.
  7. Create an Initial Extract version for each replica. When you've finished, close the Version Manager.
  8. Right-click the geodatabase in ArcCatalog and select Disconnect. Close and restart ArcCatalog.

    In the next steps, you execute several ArcFM Solution tools in ArcCatalog.

  9. On your Administrator machine, right-click a folder in ArcCatalog and select New to create an empty file geodatabase (*.gdb) or personal geodatabase (*.mdb). This becomes your backdrop geodatabase.
    TIP: Engine Mobile users: The Backdrop geodatabase is created on the Administrator machine because the directory structure on your Administrator machine is exactly the same as the directory structure on your field machines. In a later step, you connect stored display layers from the Login database to the Backdrop geodatabase. It is critical that these databases reside in the exact directory structure used in the field when these layers are connected. This ensures the stored display layers remain connected for field users after the databases are distributed by Geodatabase Replication.
  10. Right-click your newly created (empty) personal or file geodatabase and execute the Create/Update ArcFM Solution System Tables tool. This creates the necessary ArcFM system tables in your new geodatabase.
  11. Connect to the Initial Extract version you created in earlier steps. Right-click your Enterprise geodatabase and select Geodatabase Connection Properties. Ensure that the Transactional radio button is checked and select the initial extract version you created. This causes ArcCatalog to use this version when connecting. You must connect to the Initial Extract version. If you accidentally connect to the SDE.Default version before copying data to your new database, you lose changes in future backdrop updates.

  12. Copy and paste data from the Initial Extract version(s) in SDE into the personal or file geodatabase created in earlier steps. If you require a spatial subset, try using ESRI's Create Replica tool (see ArcGIS online help for more information). This copy or extract MUST come from the Initial Extract version(s). Note that if you copy the Landbase dataset, you need a Network Analyst extension license.
  13. Close ArcCatalog and restart it.
  14. Run the Upgrade ArcFM Solution Database tool on your new personal or file geodatabase. This tool updates your geodatabase with modifications required by the latest release.
  15. Next, select your SDE geodatabase (Enterprise) and run ArcFM XML Export. Select all export options. This tool exports the selected information (export options) to an XML file.

  16. Select the personal or file geodatabase you created earlier and use the ArcFM XML Import tool to import the data from the previous step. This imports data such as model name assignments, ArcFM properties, snapping information, etc.

    If you do not use Engine Mobile, continue to step 16. Engine Mobile users only:  Assign the MM Field Edit model name to the geodatabase. The MM Field Edit model name is necessary if you have a stored display that points to multiple workspaces (i.e., databases). When the field user opens the stored display that points to multiple databases, the layers point to the database that has this model name assigned.

  17. Right-click the geodatabase and select ArcFM Properties Manager.
  18. On the Model Names tab, select the Domain Independent Database Model Name domain.
  19. Select MM FIELD EDIT in the Model Names Available field and double-click it to move it to the Model Names Selected field. Remove the MM ENTERPRISE model name from the Model Names Selected field.  
    TIP: Inspector users should complete the Inspector configuration before step 15.
  20. Disable any virus-scanning software. If you use Microsoft Security Essentials, for example, follow these steps to temporarily disable real-time protection:
  21. Open Microsoft Security Essentials.
  22. Click the Settings tab.
  23. Click Real-time protection in the left pane.
  24. Uncheck Turn on real-time protection.
  25. Click Save Changes.
  26. Run the ArcFM Set ServerOIDs tool on your new geodatabase. You may need to add this command via the Customize menu. This tool populates the ServerOID field with the appropriate values. The time required to run this tool varies according to the size and complexity of your database. Learn more about this tool in the help topic titled ArcFM Set Server OIDs.
  27. Re-enable real-time protection in Microsoft Security Essentials, or re-enable your other virus-scanning software. 
  28. Place the backdrop database on the Administrator or client machine in the location where users access it. The database must be in its permanent location before connecting the layers in the next step. You can copy the backdrop database to another machine after connecting the layers, but it must be placed in the same path to prevent breaking the data sources. Field users won’t have the ability to connect broken data sources. If you do change the path of the backdrop database, be sure to run the ArcFM Data Source Wizard to fix broken data sources.

IMPORTANT: Geodatabase Replication: The location of the backdrop database may depend on the base path and  client base path set up for Geodatabase Replication. Now is a good time to review the instructions for creating the base path on the server and the client base path to ensure your backdrop database is properly located for replication. If you move your backdrop database to the Server Base Path, be sure to run the ArcFM Data Source Wizard once the backdrop database is in the correct location for Geodatabase Replication.

Open the Backdrop database in ArcMap and connect any broken data sources. Create any stored displays to be used by field users. Field users won’t have the ability to connect broken data sources or create stored displays.

  • Geodatabase Replication: The backdrop should be kept as current as possible. If you have a regular posting/reconcile process in place, the backdrop would ideally be refreshed with each iteration of that process. The Geodatabase Replication tool is used to refresh the backdrop. If you wish to configure Geodatabase Replication to maintain this database, copy the Backdrop database you just created to the Initial Extracts folder in the Geodatabase Replication Base Path on the Replication Server.

  • Autoupdaters: When features are imported from the field to the enterprise, all edits that were performed in the field are duplicated (or replayed) on the Enterprise. However, autoupdaters are not executed (unless configured, see below) while importing field edits to the Enterprise. All necessary autoupdaters must fire when the edits are made in the field.There may be an instance where an autoupdater exists on the Enterprise, but not in the field. You can configure an autoupdater like this to fire when the mobile edits are replayed on the Enterprise machine during import. Use the On Mobile Feature Create, On Mobile Feature Update, and On Mobile Feature Delete feature properties in the ArcFM Properties Manager (Object Info tab) to specify the autoupdater(s) that should fire on the Enterprise while replaying edits from the field.

QR code for this page

Was this helpful?