The ExtraView - ExtraView integration daemon may require significant configuration for large sites, where many business areas, potentially each with hundreds of fields need to be mapped from the source to the target installations. The following pointers can help in making this a simpler task, especially if there is a large amount of data that needs to be synchronized for the initial population of one of the installations.
-
As far as possible, only map the fields for a single direction of mapping, from the source to the target system during the initial data load. An exception to this should be the
EV_IDnn fields you configure to establish the identities of the mapped records
-
Before starting the integration task, set the timestamps for the UDF list history, the relationship group history, and the attachment history to the present time. Set the timestamp for the last issue history and the last upsert history to a date earlier than the date of the earliest record on the source system. This makes the integration daemon reduce the amount of work required and only migrate essential records
-
Turn off all custom code for the duration of the initial data load
-
Bypass all the business rules for the duration of the initial data load
-
If the issues being synchronized are complex, with many document fields, image fields and / or attachments set the
SOCKET_TIMEOUT_SECONDS to a value of 800 or so
-
Consider setting the values of
deletes.client and deletes.client2 to a value of NO for the initial migration of records from one server to another. This will speed up the initial load of data. Once complete, you can reset the values to YES, if this is appropriate
-
Once the initial data load of a target system is complete, reconfigure the configuration to map the records bidirectionally between the source and and target system. Turn on the custom code and business rules. Then, perform a simple mass update to all the records in the target system to trigger the logic within the custom code and business rules.
