Incorrect RAD is generated from the Gateway hosted virtual service

Product/components used and version/fix level:

API Gateway and Integration server on the versions 10.11 and 10.15 on the today’ fix level.

Detailed explanation of the problem:

It seems that API Gateway is causing
the sequence of date parameters in the generated RAD documents change
and content type change from json to xml.

Created RAD in IS from an original API, and it works when calling these API’ via the flow services,
however, does not work with API’ exposed from API Gateway.

Used swagger url, downloaded swagger json in the API Documentation section
as well as exported swagger json from API Portal where API was published to.

but still, RAD generated from the API’ specification on Gateway differ from the RAD generated from original native API’.

Error messages / full error message screenshot / log file:

In the attached screenshot the correctly generated (directly from API’) document that is matching API specification is on top, while the document below was generated from API Gateway API specification link from the Document section and is incorrect.

Question related to a free trial, or to a production (customer) instance?

Both components are licensed with the partner license.

Can you elaborate on what the error or symptom is?

The screen shot seems to be noting differing order of the elements. Is that what the suspected issue is? I ask because JSON elements are not ordered. JSON is an unordered collection of name/value pairs. If order is not what is being noted here, my apologies.

Is there a specific message/error that is observed?

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.