Thanks in advance for looking at the question.
For all the examples of wmq.jmsra-ds.xml, I see following for the configuration of connection factory and mbean definitions:
tx-connection-factory |
|---|
<tx-connection-factory>
<jndi-name>
QUEUE_CONNECTION_FACTORY_NAME
</jndi-name>
...
<!--
Configuration for the ConnectionFactory. This defines the
channel, hostname, port, queueManager, and transportType
properties for a client (TCP/IP) connection to WMQ
-->
<config-property name="channel" type="java.lang.String">
CHANNEL_NAME
</config-property>
<config-property name="hostName" type="java.lang.String">
MQ_HOST_NAME
</config-property>
<config-property name="port" type="java.lang.String">
MQ_Q_MGR_PORT
</config-property>
<config-property name="queueManager" type="java.lang.String">
QUEUE_MANAGER_NAME
</config-property>
<config-property name="transportType"
type="java.lang.String">
CLIENT
</config-property>
<!-- define security domain -->
<security-domain-and-application>
JmsXARealm
</security-domain-and-application>
</tx-connection-factory> |
And then the mbean:
mbean |
|---|
<mbean code="org.jboss.resource.deployment.AdminObject"
name="jca.wmq:name=queue1">
<!-- Bind this AdminObject with the JNDI name IVTQueue
-->
<attribute name="JNDIName">
QUEUE_NAME_TO_WHICH_MESSAGE_HAS_TO_BE_SENT
</attribute>
<!-- this MBean depends on the WebSphere MQ resource
adapter -->
<depends optional-attribute-name="RARName">
jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'
</depends>
<!-- this admin object is a javax.jms.Queue -->
<attribute name="Type">javax.jms.Queue</attribute>
<!--
Configuration for Queue
QUEUE_NAME_TO_WHICH_MESSAGE_HAS_TO_BE_SENT on
queue manager QUEUE_MANAGER_NAME. All messages sent
to this queue will have their expiry time overridden so that
messages never expire.
-->
<attribute name="Properties">
baseQueueManagerName= QUEUE_MANAGER_NAME
baseQueueName= QUEUE_NAME_TO_WHICH_MESSAGE_HAS_TO_BE_SENT
</attribute>
</mbean> |
Although its just few extra types on my keyborad, why does one need to specify the queue manager twice: Once as
queueManager, another time as baseQueueManagerName?
