Conguringthe Generic Resource Adapter

Priorto deploying the resource adapter, JMS client libraries should be made available to the
EnterpriseServer. For some JMS providers, client libraries may also include native libraries. In
suchcases, these native libraries should also be made available to the JVM(s).
1. Deploythe generic resource adapter the same way you would deploy a connector module.
2. Createa connector connection pool.
3. Createa connector resource.
4. Createan administered object resource.
5. Makethe 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":
ResourceAdapter Properties
Thefollowing table presents the properties to be used while creating the resource adapter.
PropertyName ValidValues DefaultValue Description
ProviderIntegration
Mode
javabean/jndi javabean Decides the mode of integration
betweenthe resource adapter and the
JMSclient.
ConnectionFactory
ClassName
Nameof the class available
inthe application server
classpath,for example:
com.sun.messaging.
ConnectionFactory
None Classname of
javax.jms.ConnectionFactory
implementationof the JMS client.
Usedif ProviderIntegrationMode is
javabean.
QueueConnection
FactoryClassName
Nameof the class available
inthe application server
classpath,for example:
com.sun.messaging.
QueueConnectionFactory
None Classname of
javax.jms.QueueConnectionFactory
implementationof the JMS client.
Usedif ProviderIntegrationMode is
javabean.
ForeignJMSProviders
SunGlassFishEnterprise Ser ver2.1 Administration Guide • December 200868