This note is for Tibco BusinessWorks 5.8, the JMS implementation of IBM Websphere MQ version 6, Tibco Designer 5.6, SOAP UI 3.6.2 and Hermes JMS 1.14

When sending JMS messages with SOAP UI no new BusinessWorks processes appeared in the Tibco Designer Tester. These processes should have been invoked via a SOAP Service Agent.

Initially I thought that they were not consumed by BusinessWorks/Designer and that there was a queue name mismatch or so. It turned out that the Designer Tester did consume the messages.

The SOAP Service Agent did not initiate any BusinessWorks processes but instead threw an error. The Designer Console was the place to look and the error messages there gave useful hints for solving the problem.

For instance the following error indicates that something is wrong with the SOAP Header tag:

Error [com.tibco.service.binding.soap] BW-EXT-LOG-100000 
Exception thrown while executing the mapper. 
Either invalid or no headers found in SOAP message.

When I got this error message in the BusinessWorks log I saw my BusinessWorks Service Agent was configured to use SOAP 1.1. In addition some header fields were mandatory. So I added a number of mandatory fields to the SOAP header and made sure the namespace prefixes were defined for these fields. Then I changed another namespace to the SOAP 1.1 namespace from SOAP 1.2. In SOAP UI I set the protocol to SOAP 1.1 in the Interface Properties of the wsdl.