IT31542: SAPREPLY NODE MAY ISSUE A SUPRIOUS BIP3451 WARNING IF INITIALISED BEFORE ANY SAPINPUT NODE DURING A DEPLOY

APAR status

• Closed as program error.

Error description

• The initialisation order of message flow nodes is unspecified so
  a BIP3451 warning may occur if a SAPReply node attempts to start
  before any SAPInput node in the same flow has had a chance to
  start.
  
  Additional Symptom(s) Search Keyword(s):
  

Local fix

• Manually editing the .msgflow or .subflow file to ensure that
  the SAPReply node's definition appears after that of a SAPInput
  node, and that the unique ID for the SAPReply node is
  lexicographically after the unique ID for a SAPInput node
  should force the SAPInput node to start before the SAPReply
  node, but this is not guaranteed.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of the SAPInput and SAPReply nodes in IBM App Connect
  Enterprise v11.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The initialisation order of message flow nodes is unspecified so
  a BIP3451 warning may occur if a SAPReply node attempts to start
  before any SAPInput node in the same flow has had a chance to
  start. For example:
  
  BIP3451W: SAPReply node 'mySAPReplyNode' in message flow
  'mySAPFlow' has been deployed to integration server 'myIS' that
  has no SAPInput node.A SAPReply node replies to a BAPI call that
  a SAPInput node receives. If no SAPInput node is present, a
  SAPReply node does not have a BAPI request to which to
  respond.The message flow will deploy but an error will be thrown
  if a message reaches the SAPReply node. Add a SAPInput node to a
  flow in this integration server and re-deploy.
  
  This message should only be issues if there are no SAPInput
  nodes in the same flow.
  

Problem conclusion

• The BIP3451 warning will now only be issued by a SAPReply node
  if there are no SAPInput nodes registered after every message
  flow node has been initialized.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.8
  
  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