Schema management
Very early on in our MIM deployment, we ran into discussions regarding the need for schema changes in MIM. The default schema is not sufficient, and needs to be modified in almost every case. I will only give a short overview about schema management in this chapter, and will try to explain more in the coming chapters.
MIM Sync versus MIM Service schema
One of the problems with the MIM Synchronization/MIM Service system is that it holds two schemas. We have one schema for the MIM Synchronization Service database and one for the MIM Service database.
Depending on our needs, we change one or both of these schemas. Whether the attributes or objects are required within MIM Service depends on whether or not they are managed using MIM Portal, or used in some policy. If not, we do not need them in the MIM Service schema.
On the other hand, if an attribute or object type is used in a policy within MIM Service, but is never supposed to be synchronized to other data sources, we do not...
