APAR status
Closed as program error.
Error description
Code fixes to resolve some compatibility issues in the API Connect v5 emulation functionality.
Local fix
Problem summary
<p>Issue included:</p><ul><li>A version 1.5.0 Invoke or proxy policy could return a HTTP 200 when the response content type header didn't match the response payload content.</li><li>API Gateway v5 emulation could return an incorrect payload content type header in some use cases.</li><li>A version 1.0.0 policy exception would not update the HTTP status and reason returned by the API Gateway.</li><li>A version 1.5.0 invoke or proxy policy would not update the body of the output context with the response body in some use cases.</li><li>API Gateway v5 emulation could provide a string instead of a parsed JSON or XML payload to the emulated policy in some use cases.</li><li>Some API Connect context variables are inaccessible by version 1.0.0 GatewayScript and XSLT policies</li></ul>
Problem conclusion
<span style="background-color:rgb(255, 255, 255)">A fix will be delivered in the API Connect </span>v10.0.1.1 release.
Temporary fix
Comments
APAR Information
APAR number
LI81736
Reported component name
API CONNECT ENT
Reported component ID
5725Z2201
Reported release
A0X
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-10-28
Closed date
2020-12-10
Last modified date
2020-12-10
APAR is sysrouted FROM one or more of the following:
IT34413
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
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X"}]
Document Information
Modified date:
11 December 2020