webMethods

Product/components used and version/fix level:

ApplinX 10.7.0.0001.1382

Detailed explanation of the problem:

The REST web service implemented via SOA ApplinX application responds with the payload in XML format.
Do not see how to respond with JSON format. Is it ever possible ?

Error messages / full error message screenshot / log file:

N/A

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

N/A

have you set a Content-Type:application/json HTTP header for your request?

I have set that and received server error http 500

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/c147384de32d18dc63bedd7f7248054f80bd0640_2_952x552.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/c147384de32d18dc63bedd7f7248054f80bd0640.png 2x" data-dominant-color="F7F8F8">

image.png979×567 82.7 KB

do you have access to the server.log from the wmIS that is hosting your REST services? There should be some more information about the error that the service returns as HTTP500 to the caller.

Hi Leonard,

I think you’re using version 10.7 which has the previous WSS REST implementation, which is XML based.
Updating to the latest version would let you use the new implementation with JSON format…

Hi Gadi,

Migrated the working app from 10.7 to 10.11 but still received the same error after adding Content-Type as application/json.

Assume that I might have to open SR

I think you probably need to re-generate the REST service using the new implementation.
Please review the relevant DOC section.

I have recreate procedure group but have not notice the difference.
Also, when explicitly specifying Content-Type as application/xml the the fault: Stream closed takes place

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/cf92733d86407fd85965d0d181347ee4f26ee699_2_1035x385.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/cf92733d86407fd85965d0d181347ee4f26ee699_2_1380x514.png 2x" data-dominant-color="F5F5F5">

image1677×627 198 KB

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/fffd1741b52a773fb7b7075aef124d7faf2cfa2b_2_1035x403.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/fffd1741b52a773fb7b7075aef124d7faf2cfa2b_2_1380x538.png 2x" data-dominant-color="F9F9F9">

image1638×640 133 KB

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/3f628a563736dea73e2d3f4a8c8cd580488ed5b5_2_1035x291.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/3f628a563736dea73e2d3f4a8c8cd580488ed5b5_2_1380x388.png 2x" data-dominant-color="F8F8F8">

image1657×468 94.7 KB

What I’m talking about is a completely new REST implementation, you’re still trying to modify the old one - this will NOT work.
Please review the DOC section I sent earlier and use the NEW implementation of REST.

Thank you very much

I am still very confused by this documentation as it seems very incomplete.

How to use the rest-API-config.json file to generate new REST implementation ?
And attempting to get token with connect session receive HTTP Status 415 – Unsupported Media Type

Cannot recall anything else as much confusing …