Scope of AMM files
AMM files can include the configuration objects defined in Alfabet Expand as well as object data for various configuration related object classes. You can either select single, changed configuration items for upload or upload the complete configuration. You can only add customized configuration objects to an AMM file. Standard configuration objects are only added if they allow user configuration, like for example protected object classes which can have user defined object class properties.
The following configurations are not stored as part of the meta-model configuration:
- Configuration of some reference data created on the Alfabet user interface: Reference data include for example, cost types, evaluation types, measurement units, and prioritization schemes. Only a subset of reference data can be included in AMM files.
- Mandate configuration: The configuration of mandates is saved as object data and cannot be stored in AMM files.
- Documents uploaded to the Internal Document Selector: Documents in the Internal Document Selector can only be stored in normal database backup files on the database server level or added to the target database manually. This may impact the images and stylesheet files stored in the Internal Document Selector that are to be used in HTML templates implemented in the workflow capability. Although HTML templates can be saved to an AMM file and uploaded to a target database via the meta-model update, the images and stylesheet files must be uploaded to the Internal Document Selector of the target database via the Internal Documents functionality in the Alfabet user interface, which is accessible via the Admin user profile.
If an object is included in an AMM file, all subordinate configuration parts are also selected. For example, if a content area is added to the AMM file, it is added with all content pages, content items, and custom button defined within the data workbench. If a configuration object with the same name exists in the target database, it is overwritten with the configuration object in the AMM file. The name comparison is case insensitive. Only for object classes subordinate configuration can be merged to an existing configuration. For example, an object class is merged into the configuration of a target database configuration via AMM based update of the meta-model and the object class in the target database has a custom object class property not available for the object class in the AMM file. You can either select to merge the object class configuration and preserve the custom object class property of the target database, or you overwrite the object class in the target database, which will remove the custom object class property.
The following table lists the configuration objects which can be uploaded to an AMM file. The table also informs about the name of the configuration objects in the functionality for selecting a customized range of configuration objects to AMM files.
| Tab in Alfabet Expand | Configuration Object (Section name in Find Meta-Model Objects for Deployment table) |
|---|---|
| Meta-Model |
|
| Presentation |
The following options are for concepts of the Alfabet 10.x. configuration which are currently still supported but should be substituted with current configuration options.
The following options are currently not supported, not configurable, or deprecated:
|
| Presentation > Icon Gallery |
|
| Functions |
|
| Workflows |
|
| Reports |
|
| Publications |
|
| ADIF |
|
| Diagrams |
|
| Surveys | Surveys are currently not supported. |
| Data Workbenches |
|
| Reusable Elements |
|
In the editor for creating an AMM file, you can add objects of selected object classes of the Alfabet meta-model to the AMM file. Existing objects in the Alfabet database are overwritten if the key property for identification of the object is identical. The key comparison is case insensitive. The following table lists the object classes for which object can be migrated via AMM, the key used to identify the objects, and whether the objects can be added to the AMM file by direct selection of objects or as sub-objects of a selectable parent object.
| Object Class | Key | Selection | Additional configuration information |
|---|---|---|---|
| Class Configuration (ClassConfiguration) | Class Name | Directly | If stereotypes are defined for an object class, each stereotype is listed in a separate row of the table with the Name defined as "Name (Stereotype)". |
| Color Rule Group (ColorRuleGroup) | Name | Directly | Color rules are included if you include the parent color rule group in the AMM file. |
| Color Rule (ColorRule) | Name | Directly or included with selection of the color rule group they are assigned to. | Color rules that are assigned to a color rule group cannot be included separately. You need to include the color rule group to include them. The table for color rules only displays color rules that are not assigned to a color rule group. These color rules can be selected separately. |
| Consistency Monitor (ConsistencyMonitor) | Name | Directly | |
| Data-Triggered Action Group (DataActionGroup | Name | Directly | If you add a data-triggered action group, the data triggered action group and all data-triggered action in the group are also added. |
| Data-Triggered Action (Data Action) | Name | Directly or with selection of the data-triggered action group it is assigned to. | If the data-triggered action rule you import is part of a data-triggered action group that does not exist in the target database, you must also add the data-triggered action group. |
| Data-Triggered Action Rule DataActionRule | Name | If you add a data-triggered action rule, you must also add the data-triggered actions assigned to the rule and the data-triggered action groups which are parents of the data-triggered actions to the AMM file. | |
| Data-Triggered Action Rule Detail (DataActionRuleDetail) | Rule, Action | Included with selection of the data-triggered action rule it is defined for. | Data-triggered action rule details store information about the data-triggered actions assigned to the rule and the execution order defined for the actions within the data-triggered action rule. |
| Data Quality Rule Group (DataQualityRuleGroup) | Technical Name | Directly | If you add a data quality rule, subordinate data quality rules will not be included automatically and must be added separately to the AMM file. |
| Data Quality Rule (DataQualityRule) | Technical Name | Directly | If you add a data quality rule, you must also add the parent data quality rule group separately to the AMM file. Otherwise, the data quality rule is listed under Unassigned Data Quality Rules. |
| Diagram View (Diagram View) | Name | If you include a diagram view using color rules, you need to include the relevant color rule groups as well. | |
| Diagram View Item (DiagramViewItem) | Name | Included with selection of the diagram view they are assigned to. | |
| Evaluation Type (EvaluationType) | Name | Directly | |
| Indicator Type (IndicatorType) | Evaluation Type, Name | Included with selection of the evaluation type they are assigned to. | |
| External Link (ALFA_EXTERNAL_LINK) | Directly | If the left navigation of a user profile you added to the AMM file includes external links, those must be added separately to the AMM file. | |
| Help Context Content (ALFA_HELPCONTEXTCONTENT) | ContextID | Directly | Context sensitive help is provided with the standard IT Transformation Server configurations of Alfabet only. Each expandable element of the FAQ-like context sensitive help is one help context content object. |
| ITPortfolio | Name | Directly | |
| NotificationMonitor | Name | Directly | |
| Portfolio | Name | Directly | |
| PrioritizationScheme | Name | Directly | |
| Role Type RoleType | Name | Directly | |
| System Date Monitor (SystemDateMonitor) | Name | Directly | |
| User Interface Theme (ALFA_UI_THEME) | Name | Directly | |
| User Profile (ALFA_USERPROFILE) | Name | Directly | If the left navigation of a user profile you added to the AMM file includes external links, those must be added separately to the AMM file. |