Configuring the geocoding work queues

The ClaimCenter work-queue.xml file configures one Geocode worker to geocode addresses.

<work-queue 
    workQueueClass="com.guidewire.pl.domain.geodata.geocode.GeocodeWorkQueue" 
    progressinterval="600000">
    <worker instances="1" batchsize="100"/>
</work-queue>

The ContactManager work-queue.xml file configures one ABGeocode worker to perform geocode processing on addresses.

<work-queue 
    progressinterval="600000"
    workQueueClass="com.guidewire.ab.domain.geodata.geocode.ABGeocodeWorkQueue">
    <worker batchsize="100" instances="1"/>
</work-queue>

You can modify these configurations, but first verify that you have a good understanding of the work queue infrastructure. For example:

You can have more than one instance of worker.
One concept is how progressinterval is used with batchsize by the system. The default setting of progressinterval is 600,000 milliseconds, or 10 minutes. This setting is the amount of time that ClaimCenter or ContactManager allots for a worker to process batchsize geocode work items. If the time a worker has held a batch of items exceeds the progressinterval, the work items become orphans. ClaimCenter reassigns orphan work items to a new worker instance. Therefore, you need to set the progressinterval larger than the longest time required to process a work item, multiplied by the batchsize.

You must restart ClaimCenter and ContactManager after changing any of these files.

Important: If you have many new User or Contact objects in ClaimCenter or many new ABContact objects in ContactManager, processing these objects can be a system intensive operation. In this case, run the Geocode batch process when you anticipate that system use will be low, such as late at night.