Create an AMM File

Software GmbH provides a mechanism that allows the customer configuration to be saved and restored in another database independent of other parts of the database:

The customer configuration store and optionally the solution store can be saved to an AMM updater file. The updater file allows the configuration of a target database to either be merged or replaced by the configuration stored in the AMM updater file.

To store the complete meta-model configuration of the current database to an AMM file, use the following command line for the AlfaAdministratorConsole.exe:

• AlfaAdministratorConsole.exe -msalias <alias name> -alfaLoginName <username> -alfaLoginPassword <password> -mm_create_update -MmUpdateName <update caption in AMM> -MmUpdateDescription <update description in AMM> -MmUpdateOutputFile <AMM file Name>

To store all meta-model configuration objects tagged with defined tags to an AMM file, use the following command line for the AlfaAdministratorConsole.exe:

• AlfaAdministratorConsole.exe -msalias <alias name> -alfaLoginName <username> -alfaLoginPassword <password> -mm_create_update_by_tag -MmUpdateTags <tag name> -MmUpdateName <update caption in AMM> -MmUpdateDescription <update description in AMM> -MmUpdateOutputFile <AMM file Name>

The AMM file editor contains an export option generating a JSON file with information about the supposed AMM content. This JSON file does not include specific AMM content, but the information about the settings in the AMM editor. For example if the current settings AMM file editor specify that configured reports and publications shall be stored in the AMM file, the JSON contains the information that these objects shall be included. It does not include information about the configured reports and publications available in the database:

• {
• "Name": "Daily reports update",
• "Description": "this is an export of reports and publications",
• "CaseSensitive": 0,
• "RemoveConfig": false,
• "RemoveAllGuidePages": false,
• "RemoveTags": [],
• "MigrateWorkflows": false,
• "IsPrimaryConfig": false,
• "IgnoreCaseSensitivity": false,
• "MetaModelInfo": {
  • "Tags": [],
  • "ContainsEnvOptions": true,
  • "ContainsMultiCultures": false,
  • "ContainsAPICultures": false,
  • "ContainsClassModel": false,
  • "ContainsPresentationModel": false,
  • "ContainsIcons": false,
  • "ContainsDiagrams": false,
  • "ContainsReports": true,
  • "ContainsPublications": true,
  • "ContainsWorkflows": false,
  • "ContainsADIFSchemes": false,
  • "ContainsDbExtensions": false,
  • "ContainsVocabularies": false,
  • "ContainsReferenceData": false,
  • "ContainsEventTemplates": false,
  • "ContainsLicTemplates": false,
  • "ContainsResourceBundles": false,
  • "ContainsDataWorkbenches": false
  • },
• "GuidePages": [],
• "GuideViews": []
• }

The exported JSON file can be used to execute the AlfaAdministratorConsole.exe for generation of an AMM file with the current objects in the source database available for the configuration objects defined in the JSON file only. If the configuration has changed during two runs of AlfaAdministratorConsole.exe, the generated AMM file for the same JSON will have a different content. Start AlfaAdministratorConsole.exe with the following command line to generate an AMM file with the subset of configuration defined via the JSON file:

• AlfaAdministratorConsole.exe -msalias <alias name> -alfaLoginName <username> -alfaLoginPassword <password> -mm_create_update -MmConfigFile <JSON configuration file name> -MmUpdateOutputFile <AMM file Name>

The table below displays the command line options: