LI81996: MAP POLICY IN A CATCH CONSUMING XML INPUT DOES NOT DETECT THE PROPER CONTENT TYPE

APAR status

• Closed as program error.

Error description

• The map policy uses the input's content-type property as a
  default content type, but this can be overridden by for a
  *.body input by the content-type header associated with the
  payload. In the case of a XML payload in a catch, this override
  of the map policy default was not happening properly. The map
  policy in this case would assume the payload was JSON and would
  not handle the XML payload properly.
  

Local fix

• N/A
  

Problem summary

• The mechanism the map policy uses to override the configured
  input definition's content type failed to get the proper content
  type in this scenario after version 5.0.8.7.  A previous APAR
  had removed the mechanism that had been working in prior
  versions, exposing a defect in the code that utilized an
  alternative mechanism.
  

Problem conclusion

• <span style="background-color:rgb(255, 255, 255)">A fix will be
  delivered in the API Connect v5.0.8.11, 2018.4.1.16, and
  10.0.2.0 GA releases.</span>
  

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

  API CONNECT ENT

• Fixed component ID

  5725Z2201

Applicable component levels

• R508 PSY

     UP