Performing Adoption › Preparing for Adoption

Preparing for Adoption

Preparing for adoption begins with your having some indication from a report you have run that you need to perform an adoption. When needed, adoption is performed before migration. Adoption is needed only when objects you want to replace through migration do not meet migration's criteria for equivalence. Adoption establishes the required equivalence.

If you have never performed an adoption before, preparation guidelines include the following:

• Ensuring the target models meet requirements for adoption
• Becoming familiar with the list of aggregate object types and their selectable and un-selectable subordinates, so that you can determine a good selection strategy for aggregate object occurrences
• Understanding how adoption works well enough to know which model to specify as source model and which to specify as the destination model

Preparation guidelines that apply to each adoption include the following:

• Compile a list of candidates for adoption.
• Identify objects to rename prior to adoption.
• Identify objects that should not be adopted; that is, objects with like names but that are not logically the same, including:
  • Objects that can be identified through Compare Report because they share common ancestry with another object.
  • Objects that can be identified through PI views or manual inspection.
• Determine the scope of adoption.
• Adopt the model in a single session.
• Adopt the model in multiple sessions.
• Adopt selected objects.
• Identify objects to adopt together if adopting selected objects or identifying the sequence of object adoption if adopting an entire model in multiple sessions.
• Create an aggregate set to use for Trial Adoption and Adoption plus the subsequent Trial Migration and Migration.