IBM Support

IT32903: CANNOT DEPLOY AN APPLICATION WITH A .MSGFLOW AND .SUBFLOW FILE WITH THE SAME NAME CORRECTLY

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

  • If a BAR file contains an application with a .msgflow file and
    a .subflow file with the same name then the BAR file will not
    deploy correctly. The deploy chain incorrectly detects that one
    of these files is a duplicate of the other and deletes one in
    favour of the other. This can present itself in one of two ways
    depending on which file is ignored by the deploy chain:
    In the
    first case, if the .subflow file is ignored then the following
    error will be seen:
    BIP1360E: Message flow node 'Name',
    'Name#FCMComposite_1_2' in message flow 'Name' in Application
    'TestAppv10' requires subflow 'Name.subflow' which is not
    deployed.
    In the second case, if the .msgflow file is ignored
    then the BAR file will deploy but the .msgflow file will be
    missing from the list of deployed resources when seen via the
    /apiv2 admin API, the web UI, or mqsilist.
    

Local fix

  • Rename one of the two files so that the names do not clash.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise v11.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If a BAR file contains an application with a .msgflow file and a
    .subflow file with the same name then the BAR file will not
    deploy correctly. The deploy chain incorrectly detects that one
    of these files is a duplicate of the other and deletes one in
    favour of the other. This can present itself in one of two ways
    depending on which file is ignored by the deploy chain:
    
    In the first case, if the .subflow file is ignored then the
    following error will be seen:
    
    BIP1360E: Message flow node 'Name', 'Name#FCMComposite_1_2' in
    message flow 'Name' in Application 'TestAppv10' requires subflow
    'Name.subflow' which is not deployed.
    
    In the second case, if the .msgflow file is ignored then the BAR
    file will deploy but the .msgflow file will be missing from the
    list of deployed resources when seen via the /apiv2 admin API,
    the web UI, or mqsilist.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT32903

  • 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

    2020-05-18

  • Closed date

    2020-08-25

  • Last modified date

    2020-08-25

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
26 August 2020