Sun Microsystems 820433510 Resource Adapter Properties, Configuring the Generic Resource Adapter

Foreign JMS Providers

Configuring the Generic Resource Adapter

Prior to deploying the resource adapter, JMS client libraries should be made available to the Enterprise Server. For some JMS providers, client libraries may also include native libraries. In such cases, these native libraries should also be made available to the JVM(s).

1.Deploy the generic resource adapter the same way you would deploy a connector module.

2.Create a connector connection pool.

3.Create a connector resource.

4.Create an administered object resource.

5.Make the following changes to the security policy in the Enterprise Server:

■Modify sjsas_home/domains/domain1/config/server.policy to add java.util.logging.LoggingPermission "control"

■Modify sjsas_home/lib/appclient/client.policy to add permission javax.security.auth.PrivateCredentialPermission

"javax.resource.spi.security.PasswordCredential ^ \"^\"","read":

Resource Adapter Properties

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

Property Name	Valid Values	Default Value	Description
ProviderIntegration	javabean/jndi	javabean	Decides the mode of integration
Mode			between the resource adapter and the
			JMS client.
ConnectionFactory	Name of the class available	None	Class name of
ClassName	in the application server		javax.jms.ConnectionFactory
	classpath, for example:		implementation of the JMS client.
	com.sun.messaging.		Used if ProviderIntegrationMode is
			javabean.
	ConnectionFactory
QueueConnection	Name of the class available	None	Class name of
FactoryClassName	in the application server		javax.jms.QueueConnectionFactory
	classpath, for example:		implementation of the JMS client.
	com.sun.messaging.		Used if ProviderIntegrationMode is
			javabean.
	QueueConnectionFactory

68 Sun GlassFish Enterprise Server 2.1 Administration Guide • December 2008