C O N N E C T I N G   T O   D A T A B A S E S   A N D   O T H E R   R E S O U R C E   M A N A G E R S  

                jboss.jca:service=XaTxCM,name=MyAdapterDS 

Include the security info needed for connections.  There are two necessary cross references 

here:  the same name must appear in the mbean config and as the name of the realm, and 

the managedConnectionFactoryName in the authentication configuration must exactly 

match the ObjectName of the ConnectionManager mbean you are configuring for your 

adapter.  This particular example is using the ConfiguredIdentityLoginModule.  Other login 

modules will be available soon, and if your adapter requires specific credentials you may 

need to supply your own login module.  Most adapters with such requirements should come 

with appropriate login modules. 

The RARDeployment mbean indicates properties of the jca adapter (such as a jdbc driver 

wrapper) you are using.  At the moment some of these are determined from a legacy mbean 

that deploys the classes in the adapter package and reads the adapter deployment 

descriptor.  This is referenced by this tag: 

  jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper 

Here the \u"name\u" part of the ObjectName must match the DisplayName attribute of the 

desired resource adapter.  If necessary you can determine this by dropping the rar package 

into deploy and looking at the resulting automatically created 

org.jboss.resource.RARDeployment mbean in the jmx viewer.  The properties to set on the 

ManagedConnectionFactory instance are specified in the 

ManagedConnectionFactoryProperties attribute in an xml element containing elements 

such as this: 

    jdbc:informix sqli://myhost.mydomain.com:1557/mydb:INFORMIXSERVER=myserver 

specifying the property name, type, and value.  If a property does not need to be set, leave it 

out.  The RARDeployment mbean previously mentioned will also show the available 

properties. 

The other crucial attribute in this mbean is the JndiName specifying where to bind the 

ConnectionFactory or DataSource that your application will use. 

Finally the ManagedConnectionPool mbean configures pooling for the ManagedConnections 

from the resource adapter instance.  MinSize and MaxSize are pretty clear. 

BlockingTimeoutMillis indicates the maximum time to wait for a connection to be returned 

to the pool if none are available: it does not affect waiting for the driver to create a new 

99