GIS synchronization
If you're using an Oracle database, Oracle Spatial must be installed for the GIS synchronization process to work correctly.
For example, a parcel is represented by a record in each database. In the GIS database it is a polygon feature with geographic information. The record in Infor Public Sector stores administrative information about the same parcel. If you update the parcel in one database, such as changing the legal owner, the synchronization process can detect the difference and update the other parcel record accordingly.
The first step is to create mappings that define how data is to be
synchronized. The primary setup records are GIS mappings, which associate components in
Infor Public Sector with layers in the GIS. For example, you might
map the Hansen.Property.Address
component to an Addresses
layer. Each GIS mapping has a set of field mappings, which associate specific pieces of data.
The Infor Public Sector
StreetNumber field might be mapped
to the GIS STRNO field, the
StreetName field to the
STRNAME field, and so on.
After everything is set up you will use the GIS Feature Synchronization task in the Batch Manager to analyze and synchronize data. The analysis produces sync audits, which compare records in the two data sources and identify conditions such as orphans (records in one database without counterparts in the other) and mismatched fields. You can create a report-only run, which only creates sync audits and doesn't change any data, or you can do a full synchronization and update the records in one or both databases.
See "Batch Processing" in the Infor Public Sector User and Administration Library.
Finally, the GIS synchronization tools include lookups that you can use to view detailed information about the results of the sync process and to further process sync audits. For example, if a report-only run has identified a data mismatch, you can use the sync audit lookup to synchronize the records.
See Limitations.