Configuring Remote Component Options

A remote component is an underlying engine that performs a specific processing function, such as address validation, geocoding, or tax jurisdiction assignment. Some remote components can be configured to maximize performance. For example, a remote component might have options controlling how much reference data is cached in memory or how incoming data is matched to the reference data.

Each remote component is deployed into its own JVM. This means that the JVM configuration can be done through the remote component and independent of the server itself, allowing for flexibility of memory allocation and tuning of performance based on the characteristics of the remote component.

Remote component options affect all instances of the component as well as any stages that use that component. This is different from stage options, which can be modified at design time and at runtime.

Spectrum Universal Addressing component configuration

For U.S. address processing, there are several options controlling which reference data is cached in memory (for more information, see Using Management Console to Create a Database Resource).

• DpvMemoryModel: Controls which DPV files are in memory
• LacsLinkMemoryModel: Controls which LACS^Link files are in memory
• SuiteLinkMemoryModel: Controls which Suite^Link files are in memory

Spectrum Enterprise Geocoding component configuration

Spectrum Enterprise Geocoding has several options that can affect the performance of U.S. geocoding (for more information, see Adding an Enterprise Geocoding U.S. Database Resource).

• egm.us.multimatch.max.records: Specifies the maximum number of possible matches to return. A smaller number results in better performance, but at the expense of matches.
• egm.us.multimatch.max.processing: Specifies the number of searches to perform. A smaller number results in better performance, but at the expense of matches.
• FileMemoryLimit: Controls how much of the reference data is initially loaded into memory.