soapAction value in the TIBCO BusinessEvents SOAP Request
Article ID: KB0089489
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
Description:
===========
What is the default soapAction value in the SOAP Request?
Environment:
= = = = = = =
TIBCO Product name and version: TIBCO BusinessEvetns 4.x
Operating System(s): All Operating Systems
Symptom:
= = = =
NA
Resolution:
= = = = = =
soapAction takes the default destination name of the event which is sending the request.
Ex: If the destination name is “SendReceiver”, @soapAction attribute takes the value SendReceiver.
Also, if you are importing a WSDL to create the BE project; then the slashes in the soapAction (in the WSDL file) gets replaced by “_” in the Destination name and so the soapAction will not match the servers soapAction when sending out a SoapRequest from BE.
In this case, you will have to override the @soapAction value by creating a ‘soapAction’ property in the input soap event.
Refer to Solution SOL1-BBIVN6.
Description:
===========
What is the default soapAction value in the SOAP Request?
Environment:
= = = = = = =
TIBCO Product name and version: TIBCO BusinessEvetns 4.x
Operating System(s): All Operating Systems
Symptom:
= = = =
NA
Resolution:
= = = = = =
soapAction takes the default destination name of the event which is sending the request.
Ex: If the destination name is “SendReceiver”, @soapAction attribute takes the value SendReceiver.
Also, if you are importing a WSDL to create the BE project; then the slashes in the soapAction (in the WSDL file) gets replaced by “_” in the Destination name and so the soapAction will not match the servers soapAction when sending out a SoapRequest from BE.
In this case, you will have to override the @soapAction value by creating a ‘soapAction’ property in the input soap event.
Refer to Solution SOL1-BBIVN6.
Issue/Introduction
soapAction value in the TIBCO BusinessEvents SOAP Request
Feedback
Yes
No
Powered by
