REST API Descriptor

, ,
21

You don’t need to use documentToJSONString in your service as long as the Content-Type is set to ‘application/json’
The API layer will convert http payload to a wm document implicitly and place that in the pipeline. However you need to make sure that the service signature matches it identically, otherwise it will get removed.
regards,
John.

22

Hi All
we have installed latest fixes. when we changed the extended setting jsonformat “parsed” it is working find but we are implemented so many flow services “jsonStreamToDocument”. the json format is Stream. why we have given in json format given stream rad API it is not working. Can you please suggest me.

Thanks and Regards
Kanaka

23

As I said you don’t need to use jsonStreamToDocument at all. As long as the content type is set properly your service will already have the data in the pipeline formatted as webMethods attributes correctly.
regards,
John.

24

Hi,

if we have change the extended setting “watt.server.http.jsonformat”=stream we are not hitting services.

we have already implemented so many services “watt.server.http.jsonformat”=stream only, if now we have changed value in parsed it will impact so many flow services.

please help me with this?

Thanks and Regards
Kanaka

25

Sorry I didn’t realise that you changed the watt property.
In which case you need to assume that the input is called jsonStream
e.g.

stream
stream1928×572 84 KB

Then map the output to the input that has been generated for your service.
Call a tracePipeline to check everything at the end.

This worked for me.
regards
John.

26

Hello,

If we use http call invoke jsonStreamToDocument it is working fine me also but when we using rest API descriptor in rad we are not receiving the data. Changed the watt.server.http.jsonformat in extended setting in value “parsed” data we are receiving. we don’t need change watt.server.http.jsonformat=stream rest API descriptor also need work.

please help with this?

Thanks and Regards
Kanaka

27

Can you please paste the request that you are using, you should be able to export it as a curl statement from tools such as postman.

Also post a screenshot of your pipeline where you are calling jsonStreamToDocument (see my example above). Also add a savePipeline to the line following your jsonStreamToDocument. You can then view the resulting pipeline by calling restorePipeline service after from Designer. Also post a screenshot of that too.

As I said it works for me, including both invoke and rad executions.

regards,
John.

28

Hello,

Can you please provide the your id i will connect and show you in Teams

Thanks and Regards
Kanak

1 Like
29

Probably, create a Support Incident and let this get checked.

Thanks,
Sree

30

Request payload handing for Open API request is based on the JSONFormat=Parsed.

With format set to stream, request payload wont be parsed and mapped to input signature. Even having JSonSTreamTo Document wont help for Open API requests.

Please get an support Incident created to get this use cases handled.

31

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