LI81438: A PUBLISH WITH AN INVALID XML CHARACTER IN SOME CATALOG OR API METADATA COULD INVALIDATE THE ENTIRE CATALOG AT THE GATEWAY

APAR status

• Closed as program error.

Error description

• The generated XML equivalent of the catalog could be malformed
  XML but was being stored in the DataPower document cache as
  valid. This would cause a 404 Not Found response of every API
  request in the catalog until this character was corrected and
  the catalog republished. This bad character should cause the
  publish to fail but should not cause a failure of the existing
  published catalog.
  

Local fix

Problem summary

• The customer's catalog or API metadata could have some
  characters in the metadata values that would make the XML
  representation of the metadata malformed XML.  In most cases,
  metadata that could be specified by a customer with these
  characters are checked and escaped, but the consequences of not
  escaping a particular value would cause the entire catalog to
  not be accessible until this character was determined, corrected
  and the product republished.  With this fix the XML
  representation of the catalog is checked to be well formed XML
  and if not, the existing metadata used at runtime will remain
  unchanged.  The current publish would fail still but the entire
  catalog would still be accessible as it was prior to the publish
  with the invalid character.
  

Problem conclusion

• <span style="background-color:rgb(255, 255, 255)">A fix will be
  delivered in the API Connect 5.0.8.8 GA </span><span
  style="background-color:rgb(255, 255, 255)">and 2018.4.1.12 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