Sun GlassFish Enterprise Server 2.1 Administration Guide

Resource Adapter Properties

The following table presents the properties to be used while creating the resource adapter.

Property Name

Valid Values

Default Value

Description

ProviderIntegrationMode

javabean/jndi

javabean

Decides the mode of integration between the resource adapter and the JMS client. 

ConnectionFactoryClassName

Name of the class available in the application server classpath, for example: 

com.sun.messaging.ConnectionFactory

None 

Class name of javax.jms.ConnectionFactory implementation of the JMS client. Used if ProviderIntegrationMode is javabean.

QueueConnectionFactoryClassName

Name of the class available in the application server classpath, for example: 

com.sun.messaging.QueueConnectionFactory

None 

Class name of javax.jms.QueueConnectionFactory implementation of the JMS client. Used if ProviderIntegrationMode is javabean.

TopicConnectionFactoryClassName

Name of the class available in the application server classpath , for example: 

com.sun.messaging.TopicConnectionFactory

None 

Class name of javax.jms.TopicConnectionFactory implementation of the JMS client. Used if ProviderIntegrationMode is specified as javabean.

XAConnectionFactoryClassName

Name of the class available in application server classpath , for example: 

com.sun.messaging.XAConnectionFactory

None 

Class name of javax.jms.ConnectionFactory implementation of the JMS client. Used if ProviderIntegrationMode is specified as javabean.

XAQueueConnectionFactoryClassName

Name of the class available in application server classpath , for example: 

com.sun.messaging.XAQueueConnectionFactory

None 

Class name of javax.jms.XAQueueConnectionFactory implementation of the JMS client. Used if ProviderIntegrationMode is specified as javabean.

XATopicConnectionFactoryClassName

Name of the class available in application server classpath , for example: 

com.sun.messaging.XATopicConnectionFactory

None 

Class name of javax.jms.XATopicConnectionFactory implementation of the JMS client. Used if ProviderIntegrationMode is javabean.

TopicClassName

Name of the class available in application server classpath , for example: 

com.sun.messaging.Topic

None 

Class Name of javax.jms.Topic implementation of the JMS client. Used if ProviderIntegrationMode is javabean.

QueueClassName

Name of the class available in application server classpath , for example: 

com.sun.messaging.Queue

None 

Class Name of javax.jms.Queue implementation of the JMS client. Used if ProviderIntegrationMode is specified as a javabean.

SupportsXA

True/false

FALSE

Specifies whether the JMS client supports XA or not. 

ConnectionFactoryProperties

Name value pairs separated by comma 

None 

Specifies the javabean property names and values of the ConnectionFactory of the JMS client. Required only if ProviderIntegrationMode is javabean.

JndiProperties

Name value pairs separated by comma 

None 

Specifies the JNDI provider properties to be used for connecting to the JMS provider's JNDI. Used only if ProviderIntegrationMode is jndi.

CommonSetterMethodName

Method name 

None 

Specifies the common setter method name that some JMS vendors use to set the properties on their administered objects. Used only if ProviderIntegrationMode is javabean. In the case of Sun Java System Message Queue, this property is named setProperty.

UserName

Name of the JMS user 

None 

User name to connect to the JMS Provider. 

Password

Password for the JMS user 

None 

Password to connect to the JMS provider. 

RMPolicy

ProviderManaged or OnePerPhysicalConnection

ProviderManaged

The isSameRM method on an XAResource is used by the Transaction Manager to determine if the Resource Manager instance represented by two XAResources are the same. When RMPolicy is set to ProviderManaged (the default value), the JMS provider is responsible for determining the RMPolicy and the XAResource wrappers in the Generic Resource Adapter merely delegate the isSameRM call to the message queue provider's XA resource implementations. This should ideally work for most message queue products.

Some XAResource implementations such as IBM MQ Series rely on a resource manager per physical connection and this causes issues when there is inbound and outbound communication to the same queue manager in a single transaction (for example, when an MDB sends a response to a destination). When RMPolicy is set to OnePerPhysicalConnection, the XAResource wrapper implementation's isSameRM in Generic Resource Adapter would check if both the XAResources use the same physical connection, before delegating to the wrapped objects.