LI83150: APIS CONTAINING CATALOG PROPERTIES DO NOT RESOLVE CORRECTLY IN API CONNECT 10.0.5.5 AND ALWAYS RETURN DEFAULT VALUE

APAR status

• Closed as program error.

Error description

• For APIs with catalog properties, when the API has no reference
  of the form '$(property_name)' to any property.
  The API Manager does not send the catalog properties to the
  gateway, so attempts to access catalog properties using
  'context.get('property_name')' only returns the default value
  instead of the correct catalog-specific value.
  

Local fix

• Add a comment in the API with a $(property_name) style reference
  to the property.
  The important thing is that the string with the property name
  like $(target-url) appears somewhere in the API.
  
  For example, for property 'target-url', add this line to your
  yaml
  # v10.0.5.5 workaround: $(target-url)
  

Problem summary

• The catalog-specific property values are removed from the
  version of the API that is sent to gateways when the API is
  published, so the default property value is always returned
  (instead of the relevant catalog-specific value) when the API
  implementation tries to read the property value using
  'context.get('property_name')'
  

Problem conclusion

• Fix is in v10.0.5.6 and v10.0.7
  

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