Configuring batch processes

To configure batch processes, run BQSConfigurationManager.exe. You will first see the O&R Connection dialog box, which you use to connect to your Operations and Regulations database.

The BQS tool uses the same connection settings as GeoAdminstrator, stored in V8Configuration.xml.

The grid in the BQS Batch Configurations form lists the existing batch process configurations. To add a new configuration, click New. The BQS tool opens the Create New Configuration form.

  1. Type a name for the configuration in the Batch Name field.
  2. Under Batch Type, select the type of batch process you’re configuring.
    The first two options transfer data from the GIS to Operations and Regulations, or from Operations and Regulations to the GIS. You can also select Sync to synchronize the mapped fields between the two databases based on the ownership defined in the field mapping catalog.
  3. Under Component Type, select the type of records that you want to work with.
    You can select Asset, Address, Parcel, or Property. If you select Asset, you must also select the correct asset type from the Asset Type list. The list includes both standard asset types and any agency-defined asset types.
  4. Select the field mapping catalog for the process from the Field Mapping Catalog list.
    The list shows all catalogs that have been defined in GeoAdministrator.
  5. Specify the GIS layer that corresponds to the selected Operations and Regulations component type in the GIS Data Source field.
    The GIS data source can be an ArcSDE geodatabase, a personal geodatabase, a file geodatabase, or a shape file.
  6. If you want to use a SQL statement to select records, select Select Records by SQL Statement and enter your SQL in the fields below.
    If you’re transferring data from GIS to Operations and Regulations, the SQL statement is used to select records from the GIS data source. If you’re transferring from Operations and Regulations to GIS, the SQL statement selects records in the Operations and Regulations database. The SQL option isn’t available if you selected Sync as the batch type.
  7. Under Logging Preferences, enter the folder where you want to store the log file for this process.
    The log is a .csv file that lists the records that were processed in a batch run. You can select Log Records with Core Field Mismatches if you want the log to include records where there are core field mismatches between the two databases. Core fields are the fields that uniquely identify a record, such as COMPTYPE, COMPKEY, and UNITID for a point asset. For example, a hydrant feature in the geodatabase might have the same COMPTYPE and COMPKEY as a hydrant record in Operations and Regulations, but a different UNITID.
  8. Select Create New Records When Orphans Found if you want to add new records when transferring data from GIS to Operations and Regulations, or from Operations and Regulations to GIS.
    An orphan is a record that exists in the source database, but not the destination. If you don’t select this check box, the process will only synchronize existing records.
  9. To limit the number of records processed, use the Set Batch Size for Commit and Set QAQC Batch Size fields.
    To conserve system resources, you may want to limit the number of records in a batch. The Set QAQC Batch Size field defines the maximum number of records the BQS tool will process in each batch. The Set Batch Size for Commit field defines the number of records at a time that the BQS tool will commit during processing. Each field can be enabled or disabled by a check box.
    Note: If the Sync process is configured to run in multiple batches, it will not return Operations and Regulations orphans. This is a known limitation that will be addressed in a future release.
  10. When you’re finished entering your configuration settings, click Save.