Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 4.11
    • Fix Version/s: None
    • Component/s: Deployment
    • Labels:
      None

      Description

      Currently ESB does not support seamless migration for messaging/registry persistence DB schema/data when ESB version is upgraded.

      Customer encountered errors when migrating from SOA-P 3.5.0 => 3.5.1
      Expectation is that ESB should upgrade DB tables without loosing any data at start-up, they cannot afford starting with fresh schema in production environment as they may have messages in flight etc

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                amatusev Andrew Matusevich
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: