Verify and monitor the Master Data Management integration

SyncEngine Meta Information table

In the SyncEngine Meta Information table, you can find the following information for troubleshooting:

Tabell 1. SyncEngine Meta Information
Field	Info
Master Data Management public ID	A GUID assigned when creating the record.
Master Data Management data type	`1 - Bedrift` `2 - Kontakt` `3 - Hovedbokskonto` `4 - Ansvarsenhetstype` `5 - Ansvarsenhet` `6 - Avgiftskode`
Master Data Management version no.	This is blank before the initial (first) synchronisation. It gets the value 1 after the first synchronisation and increases for each subsequent synchronization. (This happens when synchronised data is edited.)
Master Data Management processing	This field is blank before activating Master Data Management on the machine. Processing status overview: Synkronisering ventende: for records which are waiting for synchronisation Synkronisering pågår: for records currently processed Synkronisering feilet: for records which faild during the synchronisation process

If some synchronisation lines have failed it is possible to retry the synchronisation by selecting the lines and using the Send mislykkede synkroniseringer på nytt processing.

In order to determine the cause of failing synchronisations there is a log file located in the Visma Business Log location (..\Visma\Log\Business\Visma.BusinessHost.SyncEngine)

SyncEngine control information table

In Visma Business, SyncEngine kontrollinformasjon table, you can find the following information for verification:

Tabell 2. SyncEngine kontrollinformasjon
Field	Info
Master Data Management operation ID
Master Data Management data type	`1 - Bedrift` `2 - Kontakt` `3 - Hovedbokskonto` `4 - Ansvarsenhetstype` `5 - Ansvarsenhet` `6 - Avgiftskode`
Master Data Management snapshot ID.
Master Data Management previous snapshot ID
Master Data Management processing	This field is blank before activating Master Data Management on the machine. After activation it will get value 1 ("Send på nytt til Master Data Management" er nødvendig) and value 3 ("Send på nytt til Master Data Management" pågår) when the Send på nytt til Master Data Management is in progress. After the Send på nytt til Master Data Management processing has been completed the field will be blank again.

If there is a mismatch between the local data-set and the data in Master Data Management, all data for the affected master data type should be sent again to MDM. This is done using the Send på nytt til Master Data Management processing. Selecting the affected lines in SyncEngine kontrollinformasjon and use the Send på nytt til Master Data Management processing.

Visma.Business.Host.SyncEngineService user interface.

Using Visma.Business.Host.SyncEngineService user interface gives the user access to a live SyncEngine processing stream for troubleshooting purposes.

Run Visma.BusinessHost.SyncEngineService from the Visma Business folder.

Visma.Business.Host.SyncEngineService configuration parameters:

SqlLog - If specifying a file name here (without path), a log file will be created in Log folder with the executed SQL statements.
BatchSize - If this is set to 0 then all changes are sent to Master Data Management on one transaction. However if you have large amount of data and limited memory on the machine then you can break down the transactions to smaller pieces. The BatchSize determines how large each transaction will be in megabytes.
PollInterval - determines, in seconds, the interval at witch Visma.BusinessHost.SyncEngineService is searching for pending operations.
MaxSyncAttemptCount - determines the number of attempts Visma.BusinessHost.SyncEngineService is making before marking a Sync operation as failed.
WaitTimeForMdmFailedNotifications determines, in minutes, the time Visma.BusinessHost.SyncEngineService waits for a failed notification from Master Data Management.
WaitTimeForRemovingFailedOperations - determines, in minutes, the time Visma.BusinessHost.SyncEngineService user interface displays the fail notifications.
LogLevel - the level of messages logged in the log file. Possible values are None, Errors, ErrorsAndWarnings, All.
MaxLogItemsInGui - determines the number of lines shown in the Visma.BusinessHost.SyncEngineService user interface. Default value is 1000.
RestoreFetchModeThreshold - if the number of entities for a data type is lower than this number all entities are sent in a single package. This makes for a faster master restore.
QueuePushTimeout - timeout for pushing a message on internal queues with default value 3000 and maximum allowed 30000. The value can be increased to solve "failed to send Message in allocated TimeOut" on large integrations.
CompanyProcessingCpuLoad - Load on CPU while processing companies with changes. Values: Max - all cores (default value); Medium - half of cores; Low - one core.