Mirth Connect
  1. Mirth Connect
  2. MIRTH-4274

Add option to read configuration map from database rather than from file

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.0
    • Component/s: None
    • Labels:
      None

      Description

      • When configurationmap.location is absent or set to "file", same behavior as before, will store in a file specified by configurationmap.path
      • When configurationmap.location is set to "database", it will be stored in the configuration table instead
      • The configuration map is included in the XML file when doing a server config export
        • This should work whether "file" or "database" is used
      • When restoring the server config, the user is prompted and can choose whether or not to overwrite the configuration map
        • This should work whether "file" or "database" is used
      • The API route for setting the server config should include a new parameter that determines whether or not the config map will be overwritten

        Activity

        Hide
        Kevin Foster added a comment -

        Looking forward to this new feature. Is there an existing migration for moving from the file to database store? Or do all the mappings need to be readded manually post upgrade? I made the change in /conf/mirth.properties and now my configuration map is empty. As well, the file $

        {dir.appdata}

        /configuration.properties remains.

        Show
        Kevin Foster added a comment - Looking forward to this new feature. Is there an existing migration for moving from the file to database store? Or do all the mappings need to be readded manually post upgrade? I made the change in /conf/mirth.properties and now my configuration map is empty. As well, the file $ {dir.appdata} /configuration.properties remains.

          People

          • Assignee:
            Nick Rupley
            Reporter:
            Nick Rupley
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development