[
https://issues.jboss.org/browse/JBESB-3917?page=com.atlassian.jira.plugin...
]
Andrew Matusevich updated JBESB-3917:
-------------------------------------
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
was:
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
Account: YellowBook (479353)
TAM customer: yes
SRM customer: yes
Strategic: yes
DB schema upgrade support
-------------------------
Key: JBESB-3917
URL:
https://issues.jboss.org/browse/JBESB-3917
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployment
Affects Versions: 4.11
Reporter: Andrew Matusevich
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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira