JR43435: 6.2.0.3 MIGRATED PROJECTS HAVE MAP ISSUE IN 7.0.0.4 IFIX1

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • The customer has projects migrated from 6.2.0.3  and when they
    use these
    projects 7.0.0.4 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 7.0.0.4
    to a
    7.0.0.4 ifix 1, the mapping is ok. But they have multiple users
    and they
    need to export and import pojects.
    If they export from 7.0.0.4 and import into 7.0.0.4 ifix 1 they
    have
    this issue
    

Local fix

  • 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 7.0.0.401
    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. 7.0.0.401 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.
    

Problem summary

  • Fix to be delivered with next Modeler 7.0.0.4 cumulative fix.
    

Problem conclusion

Temporary fix

  • Test fix provided to customer originating the issue resulting in
    this APAR. The fix is available on demand. Please contact IBM
    support.
    

Comments

APAR Information

  • APAR number

    JR43435

  • Reported component name

    WBI MODELER AE

  • Reported component ID

    5724I7500

  • Reported release

    700

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-07-14

  • Closed date

    2012-09-05

  • Last modified date

    2012-09-05

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R700 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Business Modeler Advanced

Software version:

7.0

Reference #:

JR43435

Modified date:

2012-09-05

Translate my page

Machine Translation

Content navigation