2.2. Migrating JBoss Data Virtualization

This topic lists tasks that you might have to implement in order to migrate to JBoss Data Virtualization 6.

What will I have to do?

To migrate to Red Hat JBoss Data Virtualization 6, users will need to install a fresh instance to redeploy customer applications and artifacts.
If users are migrating from a version prior to JBoss Enterprise Data Services 5.3.1, then the REST WARs will need to be regenerated due to changes in CXF. Otherwise the WAR will not deploy due to the WSDL not being found.
Previously, null values were ranked low by default. This could have a negative impact on performance and is not needed in many situations. The ranking of null values are no longer pushed down by default. Users will have to set the org.teiid.pushdownDefaultNullOrder property to preserve the old behavior if required.

Note

The old update procedure syntax is no longer supported. Therefore, users may have to revalidate models and rebuild the VDB.
Users may have to reimport VDBs stored by the hierarchical database in order to update node types.
Any custom translator or connector (resource adapter) will require migrating. It will need to be recompiled and new configuration and packaging will be needed. This is due to the changes from EAP 5 to EAP 6. Also, the translator documentation should be read, because additional features have been added (for example, DDL support), that would require additional updates to the translator.

How will migration impact modeling?

Users may have issues when validating transformations after importing a project set that were built in the previous version of Teiid Designer. Users may have to adjust transformations in their models to account for this.
Note
When you migrate models containing REST procedures from 7.7.x version, edit the XMI file and change the key names. The designer tool then displays the value for the given properties.
key= rest:uri is now key= REST:URI And key= rest:restMethod is now key= REST:METHOD

Copy to Clipboard Toggle word wrap
When importing any of the EDS project, import all the .xmi files one-by-one. This helps you to eliminate all the possible validation errors when importing the complete project set. However, do not import the .project file.

Warning

Do not remove old data before verifying the migration to JBoss Data Virtualization 6 was successful.