MIM synchronization best practices

Here are some of MIM synchronization's best practices to follow:

• Index any Metaverse object you are using for a join.

• The account used for the MIM Synchronization service should be different from the account used for the MIM Service MA.

• The source code for all rules extensions should be backed up and maintained in a source control program. You will need the source code if you ever need to debug a rules extension.

• When writing a rule extension, check whether the attribute is present before looking for a value. An example is as follows:

  if (csentry["department"].IsPresent) {...}

• We suggest performing a full import run profile and a full synchronization on each MA at least every 30 days.

• Clear the synchronization operational run history regularly as the data will make the database grow over time and have an impact on its performance.

• Avoid using the Joiner tool as much as possible because any explicitly joined or projected object will not honor existing or future...