IBM Support

IT35699: UDPS NOT REPRESENTED CORRECTLY FOR MIGRATED FLOWS AND SUBFLOWS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • While developing the dynamic UDP functionality we have tested
    against migrated flows/subflows, while the run-time reacts to
    the dynamic UDP overrides the REST layer does not show the UDP
    definitions correctly, this is because the Legacy DFM reader
    does not interpret the UDP definitions correctly.
    Currently it
    is storing the UDP as a simple property name on each of the
    nodes meaning the nodes have properties that are not seen as
    UDPs.
    We also have issues for none promoted UDPs where we have
    no ConfigurablePropertyMap at the flow level.
    As documented in
    https://ibm.ent.box.com/notes/530705741634 :
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of user defined properties in IBM Integration Bus
    migrating to IBM App Connect Enterprise v11 or v12.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If a message flow with user defined properties is migrated from
    IBM Integration Bus to IBM App Connect Enterprise then the user
    defined properties may be incorrectly represented from the Admin
    REST API's information about the message flow and its nodes. The
    user defined properties are correctly applied in the runtime,
    but the misrepresentation in the administrative API may prevent
    dynamic UDP overrides from being applied correctly.
    

Problem conclusion

  • User defined properties on migrated message flows are now
    correctly represented in the administrative API information
    about the corresponding mesasge flows and nodes.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0.15
    v12.0      12.0.3.0
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT35699

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-01-26

  • Closed date

    2022-03-10

  • Last modified date

    2022-03-10

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

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

Fix information

  • Fixed component name

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]

Document Information

Modified date:
11 March 2022