Follow these steps:
If you log on with a group ID, all members of the group can edit, rename or delete the aggregate set you create or change the aggregate set's administrator.
For Compare Report, Trial Migration, or Migration, select the same model you will select as the source model. For Trial Adoption or Adoption, select the same model you will select as the destination model.
Select an aggregate object type for which you want to list aggregate object occurrences. See the tables in Become Familiar with Aggregate Object Types.
Use the following procedure to highlight the aggregate object type of interest.
– Subordinates of Subject Area, Entity Type, and Attribute
– Subordinates of Database, Tablespace, Data Table, and Link Table
– Subordinates of Business System, Procedure, Batch Job, and Procedure step
– Subordinates of Function, Child Function, and Process
– Subordinate of Organizational Unit
– Subordinate of User Class
– Subordinate of Work Attribute Set
Select the lowest–level aggregate object possible to migrate. This strategy will reduce the number of objects that have to be migrated, as well as optimizing performance. Use the Compare Aggregate Objects Report to identify objects that have changed. Use the Trial Migration Report to determine the anticipated outcome of migrating the objects of interest. Use the expansion tables to identify component objects. If selecting a parent aggregate object, it is not necessary to select any of its component objects, since components are migrated automatically.
To identify object types that require other objects to be adopted in the same session, or previously adopted, see the guidelines under Example Where Object in Adopt Selected Depends on Another. If you are adopting all model objects in multiple sessions, list each aggregate object type in the recommended sequence, then use Select All to select all occurrences for each aggregate object type that has occurrences.
There is no need to select a subordinate aggregate object if you have selected its parent, since it will be automatically processed when the parent object is fully expanded. This is the reason that selecting Add at the parent level is not recommended here; the assumption is that you made the selection at the highest level you need.
Try to migrate at the lowest level possible. For example, do not migrate an entity type when only an attribute has changed; migrate only the changed attribute.
|
Copyright © 2013 CA.
All rights reserved.
|
|