-
Notifications
You must be signed in to change notification settings - Fork 151
Resource loader configuration
You can enable it by setting the bitronix.tm.resource.configuration property in the configuration file or by calling setResourceConfigurationFilename() on the Configuration object.
This property must contain a path to a properties file that will be loaded by the Resource Loader to create pools. Its default value is null which means the Resource Loader is disabled and resources should be manually created via the API.
You can configure a JDBC connection pool that wraps the driver's javax.sql.XADataSource implementation and presents it to the user as a javax.sql.DataSource, much like with the API.
To configure a JDBC pool, create a set of properties:
- (A) .(B). (C) -
resource.ds1.className=oracle.jdbc.xa.client.OracleXADataSource
resource.ds1.uniqueName=oracle
resource.ds1.maxPoolSize=5
resource.ds1.driverProperties.user=users1
resource.ds1.driverProperties.password=users1
resource.ds1.driverProperties.URL=jdbc:oracle:thin:@localhost:1521:XE
(A) is constant and never changes.
(B) is an arbitrary name used to group a set of properties together.
(C) is a javabean property of bitronix.tm.resource.jdbc.PoolingDataSource.
Refer to the PoolingDataSource javadoc or to the JDBC configuration page to know what properties can be set.
You can configure a JMS connection pool that wraps JMS server's javax.jms.XAConnectionFactory implementation and presents it to the user as a javax.jms.ConnectionFactory, much like with the API or for JDBC.
To configure a JMS pool, create a set of properties:
- (A) .(B). (C) -
resource.mq1.className=org.activemq.ActiveMQXAConnectionFactory
resource.mq1.uniqueName=activemq
resource.mq1.maxPoolSize=2
resource.mq1.driverProperties.userName=defaultUser
resource.mq1.driverProperties.password=defaultPassword
resource.mq1.driverProperties.brokerURL=tcp://localhost:61616
(A) is constant and never changes.
(B) is an arbitrary name used to group a set of properties together.
(C) is a javabean property of bitronix.tm.resource.jms.PoolingConnectionFactory.
Refer to the PoolingConnectionFactory javadoc or to the JMS configuration page to know what properties can be set.
Unlike the transaction manager, the Resource Loader does not support ant-like references (${...}) in its configuration file.
All resources created by the Resource Loader are bound to BTM's JNDI provider, just like the ones created by direct use of the API. Have a look at the Embedded JNDI provider page for more details.