Save configurations to an AMM file
You can save the customized meta-model configuration of the Alfabet solution to AMM update files. An AMM file can then be used to replace or modify the configuration in an existing database. The AMM file also controls how the information is updated in the target database. The decision to replace or merge the configuration with that of the target database or to migrate workflows during the configuration update is made when the AMM file is created.
AMM is a proprietary file format and therefore not recognized by Web browsers during download. If you want to store AMM files in a Web-based content management system or intranet for download, you must create a ZIP file containing the AMM file and store the ZIP file so that you can download the file via a Web browser to your local file system.
Alfabet Expand offers different mechanisms for creation of an AMM file. The mechanisms differ in the way objects are selected for uploading to the AMM file and in the availability of merge or replace of the configuration in the target database.
| Mechanism | Selection of objects | Overwriting or Changing the Configuration of the Target Database |
|---|---|---|
| Create Configuration Meta-Model Update File |
|
Merge or replace |
| Find Meta-Model Objects for Deployment | You can choose any combination of available configuration objects for upload to the AMM file. In addition, you can select objects by tag or set a tag for all selected configuration objects.
For configuration object types for that no objects are selected individually for upload, either all or none of the available configuration objects can be uploaded. |
Merge only |
| Save Meta-Model Objects Marked by Current Tag | If all configuration objects that shall be merged into a target database configuration are tagged with the same tag, the tag can be set as current tag and an AMM file can be created that includes only the tagged objects. | Merge only |