IT41896: API COLLECTION CONFIG CREATED AND CONFIGURED BUT IT IS NOT ADDED TO GATEWAY CONFIG

APAR status

• Closed as program error.

Error description

• Under certain circumstances (for example, the apic-gw-service
  cannot connect to primary peer), an API collection can be
  created and correctly configured, but it does not get attached
  to the the gateway config (30.gateway.cfg)
  As a result, attempting to invoke any APIs in this API
  collection result in a 404 error due to the API collection not
  being attached (configured) to the API Gateway.
  

Local fix

• Manually attach the API collection to the API Gateway by:
  - Navigating to the API Gateway
  - In the drop-down list associated with the "API Collection"
  property, select the API Collection and then click "add" button
  - Apply the change by clicking the "Apply" button.
  

Problem summary

• An API Collection might not be attached to the API Gateway
  configuration.
  

Problem conclusion

• Fix is available in 2018.4.1.23, 10.0.1.10, and 10.5.0.2
  
  For a list of the latest fix packs available, please see:
  https://www.ibm.com/support/pages/node/83105
  

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

  DATAPOWER

• Fixed component ID

  DP1234567

Applicable component levels