Hi all,
WebSphere just released a Beta version of the Liberty Profile that
includes support for JCA 1.6 (and ejbLite and various other 'new'
features).
I'm wondering if anyone on this list has managed to get version 2.1 (or
any older version) of the resource adapter working with the WebSphere
Liberty Profile beta (with any JMS provider).
I am trying to integrate TIBCO EMS with the Liberty Profile June/July
2014 Beta using the generic JMS resource adapter v2.1, and so far it
has been a bit of a struggle. Sadly, EMS does not support setting
properties via beans, so I'm forced to use jndi
ProviderIntegrationMode. That may or may not be relevant, but I point
it out anyway.
I am using the genericra.rar package as provided, with no modifications
(other than adding my provider jars to it), and attempting to configure
via the MessageDriven/ActivationConfigProperty annotations in my MDB,
along with the resourceAdapter and activationSpec elements of my
server.xml. I can't seem to concoct the right activationSpec, or
possibly my resourceAdapter element/properties are wrong. I have tried
lots of things I see in the IBM documentation, but generally my results
are that a) I enter a property in the activationSpec that the server
doesn't understand (resulting in the activation spec being ignored/),
or I enter an "empty" property, resulting in a
NullPointerException/invalid property exception.
I'm using a slightly modified version of the IBM "pishopReplyMDB" from
their docs to test with. It's properly installed. Here's my
resourceAdapter config (forgive the formatting limitations of this very
old website).
<resourceAdapter autoStart="true" id="tibjmsRA"
location="/Users/larry/ibm/wlp/usr/shared/resources/genericra.rar">
<properties.tibjmsRA LogLevel="finest"/>
<properties.tibjmsRA SupportsXA="true"/>
<properties.tibjmsRA ProviderIntegrationMode="jndi"/>
<properties.tibjmsRA
JndiProperties="java.naming.factory.url=tcp://localhost:7222,
java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContex
tFactory"/>
I've tried using both jmsActivationSpec (I'm still not clear on whether
this applies only to wmqJms, or to all JMS resource adapters):
<jmsActivationSpec
id="sampleMDB/pishopExampleReplyMDB/PiShopReplyMDB">
<properties.tibjmsRA/>
</jmsActivationSpec>
...and activationSpec:
<activationSpec
id="sampleMDB/pishopExampleReplyMDB/PiShopReplyMDB">
<properties.tibjmsRA
ConnectionFactoryJndiName="XAConnectionFactory"
DestinationJndiName="queue.sample"/>
</activationSpec>
jmsActivationSpec seems to be the only one that causes ANYTHING to
happen. My activationSpec seems to be consistently ignored.
I am sure that my beginner-level hands-on familiarity with app servers
is getting in my way here, so any pointers or anecdotal experience
would be greatly appreciated it.
Thanks,
Larry M.