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

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

• Message flows and subflows with the same name can now be
  deployed correctly.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.10
  
  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 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