LI78084: ERROR OCCURS WHEN TAKING AN API OFFLINE

APAR status

• Closed as program error.

Error description

• As the owner of an provider orginization, from the API page of
  API Manager user interface, when clicking the take offline
  button for an API and you are presented with an error stating
  "Could not process the API request. See the server log for more
  information, or contact your administrator."
  

Local fix

Problem summary

• As the owner of an provider orginization, from the API page of
  API Manager user interface, when clicking the take offline
  button for an API and you are presented with an error stating:
  "Could not process the API request. See the server log for more
  information, or contact your administrator."
  
  In the cmc log file, the following stack trace is present:
  2014-06-27 14:33:41.874 SEVERE [T-7680]
  [com.ibm.apimgmt.exception.APIGenericException$Serializer] No
  property documentType found on
  com.ibm.apimgmt.config.data.deployer.PlanPackageDocument!
  Throwable occurred: java.lang.IllegalArgumentException: No
  property documentType found on
  com.ibm.apimgmt.config.data.deployer.PlanPackageDocument!
      at
  org.springframework.data.mapping.context.AbstractMappingContext.
  getPersistentPropertyPath(AbstractMappingContext.java:199)
      at
  org.springframework.data.mongodb.core.convert.QueryMapper$Metada
  taBackedField.getPath(QueryMapper.java:560)
      at
  org.springframework.data.mongodb.core.convert.QueryMapper$Metada
  taBackedField.(QueryMapper.java:486)
      at
  org.springframework.data.mongodb.core.convert.QueryMapper.getMap
  pedObject(QueryMapper.java:104)
      at
  org.springframework.data.mongodb.core.convert.QueryMapper.getMap
  pedKeyword(QueryMapper.java:136)
      at
  org.springframework.data.mongodb.core.convert.QueryMapper.getMap
  pedObject(QueryMapper.java:82)
      at
  org.springframework.data.mongodb.core.MongoTemplate.doFindOne(Mo
  ngoTemplate.java:1438)
      at
  org.springframework.data.mongodb.core.MongoTemplate.findOne(Mong
  oTemplate.java:489)
  

Problem conclusion

• The problem was occurring due to a defect in the IBM API
  Management code.
  
  The fix is targeted for inclusion in IBM API Management fixpack
  V3.0.0.2
  
  Announcements of new fix packs are made on the IBM API
  Management Support Portal at
  http://www-947.ibm.com/support/entry/portal/overview/software/we
  bsphere/ibm_api_management
  

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

  IBM API MANAGEM

• Fixed component ID

  5725L3000

Applicable component levels

• R300 PSY

     UP