Support Article
External invocation of Service REST fails
SA-72399
Summary
On invoking the below Service REST rules externally, only one rule is invoked in any given environment.
- http://localhost:8080/prweb/PRRestService/IdentityManagement/V1/Identity/{Param.Operation} - this is defined with POST and PUT methods
- http://localhost:8080/prweb/PRRestService/IdentityManagement/V1/Identity/{Param.userid} - this is defined with DELETE method
For example,
In the DEV environment, the first service is invoked always.
In the TEST environment, the second service is invoked always.
Hence, at any given point, only one service is invoked in an environment. Hence, the application continues to search for that particular service rule.
Error Messages
"POST /prweb/PRRestService/IdentityManagement/V1/Identity/Invite HTTP/1.1" 500 -"
Steps to Reproduce
- Configure the setup to invoke the REST service in the SOAP UI.
- Invoke the REST service in the POST method.
Root Cause
The issue occurred because two different Rest Services were created with the same endpoint URL. The URL was identical apart from the URI parameters.
Resolution
Here’s the explanation for the reported behavior:
Two REST Services are combined as a single service and a validation is added in the new releases.
Published April 6, 2019 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.