JR43435: 220.127.116.11 MIGRATED PROJECTS HAVE MAP ISSUE IN 18.104.22.168 IFIX1
Closed as fixed if next.
The customer has projects migrated from 22.214.171.124 and when they use these projects 126.96.36.199 ifix1, the mapping does not show. This is happening only for the 6.x migrated project. The customer also found out that if they use the Workspace as is from a 188.8.131.52 to a 184.108.40.206 ifix 1, the mapping is ok. But they have multiple users and they need to export and import pojects. If they export from 220.127.116.11 and import into 18.104.22.168 ifix 1 they have this issue
Customer was able to verify some of the questions you had asked. The customer was able to see the mapping when import was done from a mar file. When the extract was done from CVS, they noticed warnings. The customer Engineer has attached the screen shot of the warnings in a document. The mapping error occured when an import was done from CVS. As suggested, the customer restarted and the mapping error was not there. But the project showed a lot of warnings. The customer has several questions: 1. Why is this happening only in 22.214.171.1241 2. Are the warnings benign? 3. Will there be other issues? 4. is restarting a permanent fix or temporary workaround? 1. The issue occurs with processes that contain multiple maps that reference the same business service object (xsd). During checkout these maps are handled in parallel and occasionally will interfere with each other. If the project doesn't show any immediate changes waiting to be committed then restarting Modeler will reload the maps properly. 126.96.36.1991 seems to be more likely to encounter the problem with this particular project. . 2. The "NLS unused message" and "parser for 'bpmn'" warnings that were observed in the log are normal. . 3. If the project shows changes immediately after checkout, then the project should be deleted and checked out again. When the issue occurs it also aborts some of the validation checking so some validation messages may be missing and restarting Modeler won't re-validate. . 4. Restarting is a workaround.
Fix to be delivered with next Modeler 188.8.131.52 cumulative fix.
Test fix provided to customer originating the issue resulting in this APAR. The fix is available on demand. Please contact IBM support.
Reported component name
WBI MODELER AE
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels