book
Article ID: KB0087602
calendar_today
Updated On:
Description
Description: BW does not accept the SOAP Action header as per the latest Submission of SOAP/JMS specification which is also signed by TIBCO. With regard to the
https://www.w3.org/Submission/SOAPJMS/ submission, versions earlier than BW 5.12 were not accepting the SOAP Action headers as per the specification format (
SOAPJMS_soapAction). Support for this enhancement has been added since 5.12.
Issue/Introduction
How to enable SOAP Event Source in BW5 to acceptSOAPJMS_soapAction header as per the specificationhttps://www.w3.org/Submission/SOAPJMS/ .
Resolution
Check the checkbox "Enable W3C SOAP JMS 1.0 Compliance" in the "Transport Details" tab of the SOAPEventSource activity and set the "Target Service" name to take advantage of this feature. See the attached screenshot (Filename: Enable Check Box).
Also, make sure that the client application sets the values of the following six properties appropriately while sending the request message. Refer to https://docs.tibco.com/pub/activematrix_businessworks/5.13.0/doc/html/tib_bw_palette_reference/wwhelp/wwhimpl/js/html/wwhelp.htm#href=palref.5.154.htm for the application properties required. See the attached screenshot (Filename: JMS_Application_Properties). Attached is a sample BW project (Filename: TestCase.zip) that demonstrates this feature. The JMS Application Property activity with the following six application properties configured and populated the values for those properties from the "Input" tab of the "JMS Queue Sender" activity. See the attached screenshot (Filename: Setting_Properties).