IT37711: REDEPLOYING A NAMESPACED MESSAGE FLOW OVER A MIGRATED FLOW CAN CAUSE DUPLICATE FLOWS TO RUN

APAR status

• Closed as program error.

Error description

• If a message flow is migrated from IIB v10 or below to ACE v11
  or v12 using mqsiextractcomponents, the message flow is
  namespaced (i.e. it does not belong to the default broker
  schema), and is not in an application, then a .dfmxml file is
  created in the Default Application for the message flow with the
  namespace embedded in the file name.
  
  When the message flow is redeployed using a BAR file that has
  the sourec .msgflow in it, the namespace will be encoded using a
  series of subdirectories, rather than in the msgflow name.
  During a redeploy, the .msgflow file and .dfmxml file will both
  exist simultaneously on disk. The deploy process is meant to
  detect this clash and favour the new .msgflow file over the
  migrated format. However due to the difference in how namespaces
  are encoded on disk between these two formats this clash is not
  detected and so the integration server will try to run the two
  message flows simultaneously.
  
  A BIP2118 error may be logged to the syslog stating that a REST
  resource could not be registered with a URI because it is
  already registered to another resource.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users migrating to IBM App Connect Enterprise v11 and v12
  with namespaced message flows deployed outside of applications.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  If a message flow is migrated from IIB v10 or below to ACE v11
  or v12 using mqsiextractcomponents, the message flow is
  namespaced (i.e. it does not belong to the default broker
  schema), and is not in an application, then a .dfmxml file is
  created in the Default Application for the message flow with the
  namespace embedded in the file name.
  
  When the message flow is redeployed using a BAR file that has
  the sourec .msgflow in it, the namespace will be encoded using a
  series of subdirectories, rather than in the msgflow name.
  During a redeploy, the .msgflow file and .dfmxml file will both
  exist simultaneously on disk. The deploy process is meant to
  detect this clash and favour the new .msgflow file over the
  migrated format. However due to the difference in how namespaces
  are encoded on disk between these two formats this clash is not
  detected and so the integration server will try to run the two
  message flows simultaneously.
  
  A BIP2118 error may be logged to the syslog stating that a REST
  resource could not be registered with a URI because it is
  already registered to another resource.
  

Problem conclusion

• Redeploying the .msgflow file will now cause the .dfmxml file to
  be replaced.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.14
  v12.0      12.0.2.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 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