IT24065: PROCESSING OF THE HIA ORDER TYPE FAILS WITH"EBICS_INTERNAL_ERROR"

iSeries_Media_5020603_6.zip
iSeries_Media_5020603_6
Media_IM_5020603_6
Media_IM_5020603_6

APAR status

• Closed as program error.

Error description

• We have started the user initialisation process with EBICS for
  our first customer using this protocol. We have received order
  types INI and HIA for one of the users.
  
  The INI order type have been processed correctly, but the
  processing of the HIA order type fails with
  "EBICS_INTERNAL_ERROR" showing the following error:
  
  Prefix must resolve to a namespace: ds
  
  The error shows on step 13 of the handleEBICSRequest process
  using the EBICS Server Service.
  
  The request from our customer declares the namespace explicitly
  on the "RSAKeyValue" tag contained in
  ebicsUnsecuredRequest/body/DataTransfer/OrderData and it seems
  that IBM Sterling B2B Integrator is unable to process
  the request with this structure.
  
  
  
  We compare the request with the HIA order type generated by
  Sterling Integrator EBICS Client. Sterling Integrator EBICS
  Client declares the namespace with prefix "ds" in the root
  element and uses this prefix for the "RSAKeyValue" tag and its
  children elements.
  
  
  
  The user state remains as partially initialised.
  
  Our customer uses RSA keys and we already needed to install a
  new version and hotfix to support the requirements from our
  customer. We are currently on hotfix 5020500_13_HF3.
  
  We need a solution to be able to support our customer requests
  as soon as possible.
  
  Attached is the customer HIA order type request and the
  OrderData tag unpackaged, the process data and step details,
  and an example HIA order type request from Sterling Integrator
  EBICS Client that we have used to compare the structure with our
  customer request, and the OrderData tag from this request
  unpackaged.
  

Local fix

• RTC:  561364
  
  The EBICS workaround for schema is based in a modification to
  the OOTB BP handleEBICSRequest, that manages all
  incoming requests on EBICS protocol.
  However, BBVA has created a modified Business Process to
  accomplish the same functionality, hence we
  use BBVA version of the Business Process.
  

Problem summary

• Users Affected:
  EBICS Users
  
  Problem Descrition:
  Incorrect response header provided for key management order
  types.
  
  Platforms Affected:
  All
  

Problem conclusion

• Resolution Summary:
  
  A code fix is provided.
  
  Delivered In:
  5020603_6
  

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