- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
REST WS - Blank Response
Hi Everyone,
We are trying to integrate to an application where the REST Webservice Request is of JSON format and the response is blank or returns no response. To verify either success or failure we need to call another webservice (Request: JSON format and Response: JSON format).
With this situation, in the 1st step as the response is blank, the REST connector is giving timeout. And to execute the 2nd step to verify whether the request is success or not we are planning to use Rest Node (GET) from workflow. But from this link Rest web service workflow node issue we understand that Rest Node will not support JSON request and response type of webservices.
Got struck with this, can anyone suggest on how to take this forward.
Thanks.
- Tags:
- Community Thread
- Discussion
- Forum Thread
- Identity G&L
- Identity Governance & Lifecycle
- IG&L
- IGL
- json
- response
- rest node
- restful
- RSA Identity
- RSA Identity G&L
- RSA Identity Governance & Lifecycle
- RSA Identity Governance and Lifecycle
- RSA IGL
- Workflow
- Workflows
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
What is the difference between blank response and no response?
How can you differentiate between a successful request with no response and an actual timeout?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi Boris,
I mean the webservice give no response whether the request is successful or not. We need to determine that by having another webservice call (GET) to get the details (For eg: Add Approle to Account -> GET the approles tagged to the account and if the one provisioned has been found then the request was success else failed)
To make that GET call, the rest node in workflow is not supporting the JSON requests and responses.
Other than a Custom Java connector is there a way to handle this situation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
I'm not a developer, but I would say that this webservice (with a blank response) is not following best practices of web services.
The rest connector (not the rest node) supports JSON and you can call it using a provisioning node, but I'm not sure if you can get the response back to the workflow.
Other approach would be to use a custom java node (in which you would invoke the GET service)
