IT32183: AS2INBOUND WORKFLOW PROCESSES OUTBOUND MDN INSTEAD OF ACTUAL PAYLOAD WHENEVER EDIINTPIPELINEPARSE FAILS

Media_IM_6000307
b2bi-docker-6000307
sfg-docker-6000307
Media_IM_6000307
sfg-docker-6000306
b2bi-docker-6000306
Media_IM_6000306

APAR status

• Closed as program error.

Error description

• AS2 Relationships is configured with "Invoke a Business Process
  directly.
  
  
  If there is a certificate misconfiguration that results in a
  signature mismatch and authentication-failed MDN disposition
  error, the AS2Inbound or AS2Extract process is still being
  created by the
  EDIINT Pipeline and calling the business process that was
  configured in AS2 trading relationship. Furthermore, the
  PrimaryDocument that the "AS2Inbound" or "AS2Extract" business
  process is
  passed, is that of the Outbound MDN that was delivered to
  the trading partner. This causes the system to process the
  Outbound MDN as if it were a file received from the trading
  partner and that's leading to unexpected processing.
  
  However, it doesn't look correct that the AS2Inbound or
  AS2Extract
  should be spawned by the EDIINT Pipeline for core processing
  failures
  such as signature mismatches, and certainly not with the
  Outbound
  MDNstill as the PrimaryDocument. When file system storage is
  chosen these files were extracted to the error directory.
  
  An "Inbound
  Error Business Process" was set up in AS2 relation but there was
  no change in behavior.
  

Local fix

• STRRTC - B2BISFG-51611
  OAQ
  Circumvention: None
  

Problem summary

• Users Affected:
  All customers using B2BI AS2.
  
  Problem Description:
  AS2 Relationships is configured with "Invoke a Business Process
  directly" (neither mailbox nor file system). The customer is
  receiving AS2 inbound from partners.
  
  If there is a certificate mis-configuration that results in a
  signature mismatch and an authentication-failed MDN disposition
  error, the AS2Inbound process is still being created by the
  EDIINT Pipeline and calling the business process that was
  configured in the AS2 trading relationship. Furthermore, the
  PrimaryDocument that the "AS2Inbound" BP is passed is that of
  the Outbound MDN that was delivered to the trading partner. This
  is causing the customer system to process the outbound MDN as if
  it were a file received from the trading partner, and that's
  leading to unexpected processing.
  
  However, it doesn't look correct that the AS2Inbound should be
  spawned by the EDIINT Pipeline for core processing failures such
  as signature mismatches, and certainly not with the Outbound MDN
  still as the PrimaryDocument. When file system storage is
  chosen, these files are extracted to the error directory.
  
  The customer tried setting a business process to use as the
  "Inbound Error Business Process" in AS2 relation, but there was
  no change in behavior.
  
  
  Platforms Affected:
  All Platforms
  

Problem conclusion

• Resolution Summary:
  If we are restarting a halted business process, the actual
  document that has the correlations will be the original
  document, the actual document will be a clone of it. There will
  be no correlations for the actual document, in this case,
  Envelope should use the correlation created for the original
  document.
  
  Delivered in:
  6000008
  6000307
  All future Fix Packs can be found in the Release Timeline Matrix
  - https://www.ibm.com/support/pages/node/6194265
  

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

  STR B2B INTEGRA

• Fixed component ID

  5725D0600

Applicable component levels