To create a JMS connection factory resource, follow these steps:
jms/ConnectionFactory1
It is a recommended practice to use the naming subcontext prefix jms/ for JMS resources.
javax.jms.ConnectionFactory, javax.jms.QueueConnectionFactory, or javax.jms.TopicConnectionFactory.For a JMS connection factory resource, specify the Transaction Support value as follows:
XATransaction (the default value) for a resource that can be used for transactions that involve the use of more than one resource within a transaction scope (for example, this resource plus a JDBC resource, a connector resource, or another JMS connection factory resource). This value offers the most flexibility. A resource that is configured as XATransaction will participate in two-phase commit operations.LocalTransaction for a resource that can be used either for transactions that involve only one resource within the transaction scope or as the last agent in a distributed transaction that involves more than one XA resource. This value offers significantly better performance. A resource that is configured as LocalTransaction will not be used in two-phase commit operations.NoTransaction for a resource that can never participate in transactions; this setting is of limited use in JMS applications.
Equivalent asadmin command: create-jms-resource
See Also: