Forum Discussion
ramjisro
15 years agoNew Contributor
Spoke too soon earlier. You need to build a patched version of soapUI if your provider is TIBCO BusinessWorks. Here's what I discovered:
To use EMS as a transport in soapUI, you need to copy tibjms.jar and tibjmsadmin.jar to $SOAP_UI/bin/ext and restart soapUI.
When using EMS, you need to specify the login and password for EMS on the Aut tab of the request. You're better off to create a separate request for your JMS requests and you HTTP requests.
The SOAPSendReply activity in BusinessWorks (5.5) doesn't really honour the JMSReplyTo that's specified on the request - it can only send replies to temporary queues.
soapUI 3.6.1. doesn't support the use of temporary queues for replies although there is a patch available on the forums at viewtopic.php?f=5&t=3145&p=16812&hilit=tibco+ems+temporary+queue#p16812
To use EMS as a transport in soapUI, you need to copy tibjms.jar and tibjmsadmin.jar to $SOAP_UI/bin/ext and restart soapUI.
When using EMS, you need to specify the login and password for EMS on the Aut tab of the request. You're better off to create a separate request for your JMS requests and you HTTP requests.
The SOAPSendReply activity in BusinessWorks (5.5) doesn't really honour the JMSReplyTo that's specified on the request - it can only send replies to temporary queues.
soapUI 3.6.1. doesn't support the use of temporary queues for replies although there is a patch available on the forums at viewtopic.php?f=5&t=3145&p=16812&hilit=tibco+ems+temporary+queue#p16812