Hide Forgot
project_key: SOA As part of migration of MMx metadata repository users, the old MMR vdb needs to be converted and usable to access the old repository thru Teiid. When trying to convert the models, many errors are seen in the JBDS console, and 90% of the models have red x's.
Link: Added: This issue Cloned to SOA-2580
One problem that was encountered is the use of reserved words. In Teiid, there are new reserved words, for which, if used, need to be escaped (i.e., element ==> "element"). And it appears a lot of the errors with the MMR / DTC models are related to using reserved words (i.e., language, element, value, etc.). This issue has been documented on the MMx Migration page (https://docspace.corp.redhat.com/docs/DOC-48911) as it may impact MMx customers that are migrating.
KBase article contents needed to support migrating customers.
Labels: Added: kbase
Writer: Added: Darrin
Parent: Added: SOA-2635
Importing is doing much better, however, it still, sometimes, has an issue importing a model. I was importing the MMFinancials demo models, and it always failed on 1 of the 5 being imported. The one model that failed would show up in designer, but with no tables. If I re-import and overlay the model, it would then contain its models.
Better news, Barry and I figured out (well he did), that after you import your models, close and reopen the project. The lost tables in the model now shows up. Was able to build project with no errors.
Parent: Removed: SOA-2635
The MMR/DTC migration steps still to be completed, but a lower priority as we know of no client as of this point that will require this.
Link: Added: This issue relates to SOA-2635