IT30476: APPLICATION DEPLOYED IN BAR FILE CREATED WITH MQSIPACKAGEBAR FAILS TO START WITH BIP1359E

APAR status

• Closed as program error.

Error description

• Deploying a BAR file for an application with message flows
  migrated from prior versions of IIB and built with
  mqsipackagebar reports BIP1359E. The application then fails to
  start.
  
  BIP1359E Unable to resolve 'TerminalLink' connection in 'Nodes'
  'Nodes' between '<node>' and '<terminal link>'.
  

Local fix

• In any message flow's ".msgflow" file which was created in a
  prior version of IIB and has an "id" attribute on the
  "nodes.translation" element, simply remove it.
  
  For example:
  
       <nodes xmi:type="ComIbmTryCatch.msgnode:FCMComposite_1"
  xmi:id="FCMComposite_1_10" location="247,183">
         <translation xmi:type="utility:ConstantString"
  xmi:id="ConstantString_7" string="Try / Catch"/>
  
  
  Would need to be edited to remove the part:
        xmi:id="ConstantString_7"
  
  Hence the message flow xml would become:-
  
       <nodes xmi:type="ComIbmTryCatch.msgnode:FCMComposite_1"
  xmi:id="FCMComposite_1_10" location="247,183">
         <translation xmi:type="utility:ConstantString"
  string="Try / Catch"/>
  
  
  Note that there maybe multiple edits of this form needed.
  
  Hence a simple workaround is to build the message flows into a
  BAR using "mqsicreatebar" and then extract the .msgflow files
  and override the Toolkit workspace .msgflow files with those.
  This works because "mqsicreatebar" will have removed these.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM App Connect Enterprise V11.0 having migrated
  flows in BARs created using mqsipackagebar
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  Deploying a BAR file for an application with message flows
  migrated from prior versions of IIB and built with
  mqsipackagebar reports errors of the form:
  
    BIP1359E Unable to resolve 'TerminalLink' connection in
  'Nodes' 'Nodes' between '<node>' and '<terminal link>'.
  
  The flows and application then fail to start.
  

Problem conclusion

• The ACE runtime message flow deployment is corrected to ignore
  the nodes.translation.id attribute in migrated message flows.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.7
  
  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