The Configuration Migration Assistant is meta data driven. It uses the Oracle Utilities Application Framework meta data to drive the underlying engine to migrate the data. With the delivery of each product a predefined set of configuration objects are provided preconfigured to be used by sites. It is possible to extend these definitions and this next set of articles will introduce these objects and how to build your own configurations for custom objects.
Before we discuss the configuration objects there is one piece of information that you need to understand. For an object to be migrated using Configuration Migration Assistant it must have two attributes:
- It must not have a system generated random primary key. These types of keys may vary from environment to environment and attempting to migrate data with these types of keys may result in unintentional results and even corruption. Configuration data tends not to use random system generated keys but Master and Transaction data does. Configuration Migration Assistant cannot be used for Master or Transaction Data. Master data is things like Accounts, Meters, Crews, Persons, Assets etc.. Transaction Data is data like Bills, Payments, Meter Reads, Tasks etc...
- Fundamentally Configuration Migration Assitant uses Maintenance Objects to process data but each object to be migrated must have a Business Object for configuration purposes. The Business Object can be any valid Business Object definition. More guidelines about this are in Configuration Migration Assistant Overview (Doc Id: 1506830.1).
The first object to configure for Configuration Migration Assistant is the Migration Plan. This object defines a primary Business Object and any directly related subordinate Business Objects that must be migrated as a single entity. The relationship between the business objects and the sequence of migration is configured in this object.
The following information is configured:
- Instruction Sequence - The sequence number for the migration instruction. This is used to process the data in the correct order.
- Instruction Type - This sets the migration instruction type. There are two values: Primary or Subordinate. There can only be one Primary Instruction Type per Migration Plan.
- Parent Instruction Sequence - If the Instruction Type is Subordinate, then this is the Instruction Sequence for the parent object for this object. Subordinates can be related to other Subordinates to document multi-level structures.
- Description and Business Object - The Business object for this instruction. The description is a free format field to allow you to document the instruction. Usually this is populated with a short description of the object.
- Traversal Criteria Type and Traversal Criteria - This is a definition of how the subordinate is related to the parent object. Configuration Migration Assistant allows you to specify Constraints in the meta data, SQL Statements or XPATH statements to document the relationship. The latter is useful for relating complex business object relationships that arte buried in XML definitions. The Criteria Type determine which method you want to use to express the relationship and the Criteria is the statement to express the relationship. The online help contains examples and guidelines for the Criteria formats supported.
- Next Migration Plan - Configuration Migration Assistant allows you to reuse Migration Plans and this field allows you to link Migration Plans for consistency. We will discuss this feature in future posts.
- Algorithms - One of the features of the Configuration Migration Assistant is the ability to manipulate the data upon import. This is where the specification of the algorithm is performed. This is typically done on the target environment.
To do this use the Admin --> M --> Migration Plan menu option.
Note: Remember, the product ships with a predefined set of Migration Plans for you to use. You may not have to configure this unless you want to copy the provided plans to tailor them or add custom business objects.
Each object to migrate using the Configuration Migration Assistant must exist in at least one Migration Plan.
For more information about this aspect of the Configuration Migration Assistant and other aspects refer to the Configuration Migration Assistant Overview (Doc Id: 1506830.1) whitepaper available from My Oracle Support.