How to resolve the error "Operation not found".
Article ID: KB0093294
Updated On:
| Products | Versions |
|---|---|
| TIBCO API Exchange | - |
| Not Applicable | - |
Description
Description:
This error is thrown if the asg-engine is not able to match the incoming / Northbound request to any Facade operation with regard to Operation URI and SOAP Action.
Resolution
When the engine receives a Northbound request:
Note: If the SOAPAction is empty in Facade Operation, the incoming request should not have a SOAPAction header.
- The incoming SOAPAction [in JMSHeaders, including quotes (if any)] should match the SOAP Action configured for the Facade Operation AND the Operation URI should be empty for the Facade Operation as a JMS Request does not have a URI associated with it.
For HTTP requests:
- The incoming request-uri should match the Operation URI configured for the Facade Operation AND the incoming SOAPAction [in HTTPHeaders, including quotes (if any)] should match the SOAP Action configured for the Facade Operation.
Note: If the SOAPAction is empty in Facade Operation, the incoming request should not have a SOAPAction header.
For JMS requests:
- The incoming SOAPAction [in JMSHeaders, including quotes (if any)] should match the SOAP Action configured for the Facade Operation AND the Operation URI should be empty for the Facade Operation as a JMS Request does not have a URI associated with it.
Issue/Introduction
How to resolve the error "Operation not found".
Feedback
Yes
No
Powered by
