How to setup 2 JMS JCA providers

[azakkerman]

Hi,

I've been trying to understand the architecture of hooking up to local/remote JMS providers.

What I understand is that the jms-ra.rar deploys a JCA connector to a JMS provider specified by JmsProviderAdapterJNDI config-property in META-INF/ra.xml.

I assume that this can be overridden somehow when the ConnectionManager is deployed (perhaps in the ManagedConnectionFactory?)

Can this be overridden twice or the rar should be deployed twice with different JNDI names in order to provide access to, say a remote JMS provider and a local one on the same node?

[davidjencks]

Normally the ra.xml supplies either no values or default values for the config properties. You set the actual values for a specific instance in a jboss specific deployment descriptor. Normally you do not change the vendor provided ra.xml when deploying an adapter. The jms-service.xml seems to have only one of the config-properties set, but you can set any one of those specified in the ra.xml. For the providerjndi name it would look something like this


<config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:DefaultJMSProvider</config-property>
<config-property name="sessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>


(this uses a slightly simpler config format than that in the current jms-service.xml)