adoption
Adoption is the process that establishes common ancestry between objects in different models that are logically the same. Whether objects are adopted is determined by adoption rules, where criteria are often identical object name value and same aggregate object type, or common ancestry between parent objects. When a match is found, the Original Encyclopedia ID and Original Object ID of the object in the destination model is changed to have the same values as those of the object that is logically the same in the source model. After adoption, these two objects share common ancestry. When an aggregate object is adopted, its component objects are also adopted if they meet adoption criteria according to the adoption rules. When a parent object is adopted, but a component of that object is not adopted because it is not logically the same as any component in the source model, that component is reported as unadopted.
adoption rules
Adoption rules are the rules that determine whether an object in the destination model will have its Original Encyclopedia ID and Original Object ID replaced by those of the object that is logically the same in the source model. See Adoption Rules.
aggregate object
An aggregate object is an occurrence of an aggregate object type. It is also called aggregate object occurrence. An aggregate object represents a collection of related objects within a model. An aggregate object is the smallest unit of information that you can select to migrate, adopt, or compare. An aggregate object is the smallest unit of information that can be marked changed (see Change Capture). Entity types, Attributes, and Relationship Memberships are examples of aggregate objects.
aggregate object expansion
Aggregate object expansion is the process of determining which related objects are migrated along with a selected aggregate and whether the proper conditions exist in the destination model for the migration to succeed. See the section, Aggregate Object Expansions and Special Cases
aggregate object type
Aggregate object type is a category to which aggregate object occurrences belong. To display a selection list of aggregate objects for Migration, Adoption, or Compare Report, you first select the aggregate object type to which it belongs. Only certain object types are aggregates for Version Control. Aggregate object types for Adoption are different from aggregate object types for Migration and Compare Report.
aggregate set
Aggregate set is a collection of aggregate object occurrences that can be reused as is or modified for functions requiring the same or similar sets, such as such as Trial Migration and Migration.
ancestry
Ancestry of an object refers to the combination of its Original Encyclopedia ID and its Original Object ID. This composite identifier is used internally by Version Control to identify objects across models that are versions of the same object. Migration preserves ancestry when replacing an object; migration propagates ancestry when adding an object. See also common ancestry.
Change Capture
Change Capture is a subsystem that collects and saves information in the model on changes made to aggregate objects or their components. In any session where model objects can be changed, the Change Capture subsystem identifies each change by the CHNGED/CHNGDBY association between an aggregate object and a session object, which contains the date and time of the session and the user ID in effect for the session. An aggregate object is marked changed when it participates in an upload, load module packaging, member name specification, or code and DDL generation. See Change Capture for Version Control.
child model
Child model is a model that has been extracted from one encyclopedia and loaded to another encyclopedia. The model is designated as child in the encyclopedia where it is loaded. A child model can be used as the source model for Migration, Adoption, and Compare Report. Among Version Control functions, it can be used as the destination model only for Compare Report. A child model can be created with the Extract, Model command from the Encyclopedia Model Selection window on the Encyclopedia Client.
common ancestry
Two objects in different models share common ancestry if the objects have the same Original Encyclopedia ID and the same Original Object ID. When objects are migrated from the source model to the destination model, they replace objects with which they share common ancestry. Common ancestry between objects that are logically the same is created by Adoption according to adoption rules by assigning the ancestry of the source model object to the selected destination model object. Common ancestry between objects is created by Migration for objects meeting Special Equivalency Rules. Migration replaces the ancestry as well as the definition of the object being replaced. Objects that share common ancestry are equivalent; they may be the same version or different versions.
companion object
Companion objects maintain the context in which the aggregate object exists in the source model. In migrations, if an aggregate object's companion objects already exist in the destination model, they are not replaced. However, any companion objects missing from the destination model are migrated with the aggregate object. You do not need to specifically request migration of a companion. For example, referenced dialects are companion objects of exit states. If an exit state is migrated, its referenced dialects are copied with it if the dialects do not already exist in the destination model.
Compare Aggregate Object Report
Compare Aggregate Object Report, is the report that is produced when you run the Compare Report function that summarizes how aggregate objects differ between the two models being compared. Sections reported reflect sections you select. If you are comparing two models that you want to keep synchronized and you want to know what new objects were created in the source model that need to be added to the destination model, you would request the section Source only. If you want to know which of the objects that exist in both models have been changed in one model since being changed in the other, you would request the section Different. If you are managing models used for parallel development and you want to know what new components may have been added to an aggregate object in the destination model that are missing from that object in the source, you would request the section Destination only. By examining these report sections, you can determine which objects to select for migration. If you want to identify the objects that were last updated in the same change session, you would request the section Same.
Compare Report
Compare Report is the process that performs difference analysis by comparing all or selected aggregate objects within two selected models in the same C/S Encyclopedia. In addition, Compare Report follows down the chain of subordinate aggregate objects comparing each existing level until no more exist. The purpose of this analysis is to determine which of the models' aggregate objects differ or do not exist. Objects may differ based on changes made to the model. Object changes are collected by the Change Capture subsystem. Differences between equivalent objects are determined by comparing timestamps of their respective session objects or their last change date and time information. An object that is said not to exist is one for which there is no equivalent object in the other model.
component object in adoption
Component objects are objects adopted when an aggregate object is adopted. Component objects in Adoption may be either another aggregate object (attribute), used in the adoption rules of another aggregate (identifier), or referenced across other aggregate objects (view).
component object in migration
Component objects are part of the basic definition of the aggregate object. Component objects always migrate with the aggregate object so that the aggregate object will have the same definition and context in the destination model as in the source model. Conversely, an aggregate replaced by migration will have all component objects replaced or removed. In some instances, a component object of an aggregate object is also an aggregate object in its own right For example, an attribute is a component object of an entity type and also an aggregate object in its own right.
destination model
Destination model is the model that you copy objects to in migration. It is the model in which you update objects' ancestry in adoption. When you select objects to adopt, the selectable objects reside in the destination model. See also source model.
enabling object
Enabling objects are objects that either must be in the destination model when the aggregate object is migrated or must be included in the same migration as the related aggregate object for the migration to succeed. An enabling object, or enabler, may have a parental relationship to the aggregate object, as a parent subject area has to an entity type. The parent subject area must be in the destination model when you migrate an entity type or you must migrate the subject area when you migrate the entity type. An enabling object may be a referenced object, as an entity type is referenced by a view of an action block. The entity type must be in the destination model when you migrate the action block or you must migrate the entity type when you migrate the action block. If an enabler of an aggregate object is not an aggregate object, you must determine what aggregate object the enabler is a component of and migrate that aggregate object along with the other selected objects.
Encyclopedia ID
Encyclopedia ID is the numeric identifier assigned to each C/S Encyclopedia during installation. An encyclopedia's Encyclopedia ID is unique across encyclopedias. The Encyclopedia ID is automatically assigned to each object created within the encyclopedia as one part of the object's unique identification. The combination of an object's Encyclopedia ID and Object ID uniquely identifies the object across all encyclopedias. See also Original Encyclopedia ID.
equivalence
Equivalence between two objects in different models exists when the two objects share common ancestry or the objects meet one of the Special Equivalency Rules. Migration replaces equivalent objects. Compare Report lists equivalent objects as either the same or different, depending on the comparison of their respective session objects that indicate the date and time of the last change session.
equivalent objects
Equivalent objects are objects that either share common ancestry or meet one of the Special Equivalency Rules. Equivalent objects are said to be versions of the same object. Equivalent objects are compared as being the same or different, based on whether their respective session objects are the same or different. See also equivalence.
Host Encyclopedia Version Control
Host Encyclopedia Version Control is the implementation of Version Control available on the Host Encyclopedia. For a summary of differences between C/S Encyclopedia Version Control and Host Encyclopedia Version Control, see Differences from Host Encyclopedia Functions.
language code
Language code is the encyclopedia code page assigned to a model.
logically the same
Logically the same describes objects in different models that are meant to be equivalent, but do not share common ancestry. Objects that are logically the same can be objects that are alike but did not originate from the same source or objects that had their common ancestry severed. Objects that are logically the same can be adopted if they meet adoption criteria specified by the adoption rules for their object type. After adoption, objects that were logically the same become equivalent objects.
migration
Migration is the process that creates or replaces an aggregate object and its components with its definition from a source model within the same encyclopedia. If the destination model contains the aggregate object equivalent to the object being migrated plus any required enabling objects, migration replaces that object and all of its components and adds any missing companion objects. If a component that exists in the destination model does not exist in the source, migration deletes that component. If the destination model does not contain the aggregate object equivalent to the object being migrated, migration adds the aggregate object to the destination model. See also special cases.
Object ID
Object ID is the numeric identifier assigned to each object when it is created. By itself, the Object ID uniquely identifies the object within one encyclopedia. The combination of an object's Encyclopedia ID and Object ID uniquely identifies the object across all encyclopedias. See also Original Object ID.
Original Encyclopedia ID
Original Encyclopedia ID is an object property that is part of an object's ancestry. When a new object is initially uploaded from the CA Gen Toolset, the object's Encyclopedia ID becomes its Original Encyclopedia ID. When a new object is created on an encyclopedia through migration or any of the following commands issued from the Encyclopedia Client, the object inherits the Original Encyclopedia ID from the object on which it is based: Copy From This Encyclopedia, Copy From Another Encyclopedia, or Create Model from Subset. This object property along with the Original Object ID determines common ancestry between objects.
Original Object ID
Original Object ID is an object property that is part of an object's ancestry. When a new object is initially uploaded from the toolset, it is assigned an Original Object ID that is equal to its Object ID. When a new object is created on an encyclopedia through migration or any of the following commands issued from the Encyclopedia Client, the object inherits the Original Object ID from the object on which it is based: Copy From This Encyclopedia, Copy From Another Encyclopedia, or Create Model from Subset. This object property, along with the Original Encyclopedia ID, determines common ancestry between objects.
related objects
Related objects are objects related to an aggregate object. For Migration, an aggregate object's related objects include component objects, companion objects, and enabling objects. For Compare Report, an aggregate object's related objects include subordinate aggregate objects. For Adoption, an aggregate object's related objects include component objects in adoption.
session object
Session object is the object created during a process that changes model objects, which indicates the date and time of the session and the user who initiated the session. Session objects are associated to aggregate objects via CHNGDBY when any of the following C/S Encyclopedia processes change model objects: upload, load module packaging, member name specification, code and DDL generation, and conversion. When an object changes, the object or its parent aggregate object is marked as changed, and a new session object is created. The changed aggregate object is associated with the new session object and disassociated from the old session object. See also Change Capture.
source model
Source model is the model from which you select objects to migrate or compare. It is the model whose objects' ancestry is propagated during adoption. It is the model whose objects' definitions are copied during migration. See also destination model.
special cases
Special cases for migration include objects that are migrated only if certain other objects exist in the destination model, but the migration can succeed even if these objects are absent.
Special Equivalency Rules
Special Equivalency Rules is a table of rules for establishing equivalence between two aggregate objects usually of the same aggregate object type that exist in different models and do not share common ancestry. One such rule is: Business System Implementation objects are equivalent if they are associated to Business Systems that share common ancestry. The exception to the rule of being the same aggregate object type is: a Default Dialog is equivalent to a Default Primary Window if each is primary for equivalent Procedure Steps. Objects that are deemed equivalent based on one of these rules are treated as though they share common ancestry, even though they do not. Compare Report and Migration use the Special Equivalency Rules table. When objects that are equivalent based on Special Equivalency Rules are migrated, Migration establishes common ancestry between the objects. See the table, Special Equivalency Rules subordinate aggregate object
Subordinate aggregate objects
Subordinate aggregate objects are, in some cases, component objects. For example, an entity type's attributes are subordinate aggregate objects and also components of that entity type. In other cases, subordinate aggregate objects are not component objects but have a well-known child-parent relationship to the aggregate object in question. For example, Procedures are subordinate aggregate objects to Business Systems even though Procedures are not defined as a component of a Business System. Compare Report processing follows down the chain of subordinate aggregate objects, comparing each existing level. If you select a subject area to be compared within two models, all subordinate aggregate objects of that subject area are compared, including its child subject areas, entity types, attributes, relationship memberships, and so on.
Trial Adopt Model Report
Trial Adopt Model Report is the report produced by Trial Adoption when you select Adopt All Objects as the Object Range.
Trial Adopt Objects Report
Trial Adopt Objects Report is the report produced by Trial Adoption when you select Adopt Selected Objects as the Object Range.
Trial Adoption
Trial Adoption is a process that simulates an actual Adoption and reports what the results of the adoption would be. Unlike Adoption, Trial Adoption does not change the ancestry of objects in the destination model and does not perform or report component unadoption. Trial Adoption produces either the Trial Adopt Model Report or the Trial Adopt Objects Report.
Trial Migrate Aggregate Object Report
Trial Migrate Aggregate Object Report is the report produced by Trial Migration.
Trial Migration
Trial Migration is a process that simulates an actual Migration and reports what the results of an actual migration would be. Unlike Migration, Trial Migration does not change the destination model. Trial Migration produces the Trial Migrate Aggregate Object Report.
unadopted object
Unadopted object is a component of an aggregate object for Adoption, where the aggregate object was adopted but the component was not adopted because it did not conform to the adoption rules for its object type. When an object is unadopted, it is given a new Original Object ID that has never been used and its Original Encyclopedia ID is replaced with the Encyclopedia ID of the current encyclopedia.
unadoption
Unadoption is a phase of Adoption processing where components of adopted objects that cannot be adopted with the parent have their ancestry replaced to sever any common ancestry the objects may have with objects in another model. (If unadoptions were not performed, subsequent migration could place component objects within multiple parents.)
|
Copyright © 2013 CA.
All rights reserved.
|
|