32.2. Creating JBoss EAP 5 Child Resources
32.2.1. Creating Data Sources
Note
It can take several minutes for the new child resource to be added and visible in the JBoss ON inventory because the new resource has to be created on the agent platform and then discovered by the agent.
- Search for the JBoss server instance to which to deploy the data source.
- On the details page for the selected JBoss server instance, open the Inventory tab.
- In the Create New drop-down menu, select the item for .
- Select a template for the data source. There are three data sources templates to populate a data source with common information:
- The default template is used with SQL databases like PostgreSQL or MySQL.
- The Oracle Local TX is used for Oracle databases with local transactions.
- The Oracle XA template is used for Oracle databases with XA transactions.
- Along with the obvious settings, like the resource name, enter the information for the specific child resource to be deployed:
- The type of data source to create, either No TX Data Sources, Local TX Data Sources or XA Data Sources
- A unique JNDI name for the DataSource wrapper to use to bind under
- The fully qualified name of the JDBC driver or DataSource class, such as
org.postgresql.Driver - The JDBC driver connection URL string, such as
jdbc:postgresql://127.0.0.1:5432/foo - The username and password to use to connect to the data source
- The minimum and maximum connection pool sizes for this data source
Additional settings are available under the Advanced Settings area.
32.2.2. Creating Connection Factories
Note
It can take several minutes for the new child resource to be added and visible in the JBoss ON inventory because the new resource has to be created on the agent platform and then discovered by the agent.
- Search for the JBoss server instance to which to deploy the connection factory.
- On the details page for the selected JBoss server instance, open the Inventory tab.
- In the Create New drop-down menu, select the item for .
- Along with the obvious settings, like the resource name, enter the information for the specific child resource to be deployed:
- The type of connection factory to create, either tx-connection-factory (transaction) or no-tx-connection-factory (no transaction)
- A unique JNDI name for the DataSource wrapper to use to bind under
- The username and password to use to connect to the data source
- The minimum and maximum connection pool sizes for this data source
Additional settings are available under the Advanced Settings area.
32.2.3. Creating JMS Queues and Topics
JMS Queues and JMS Topics are child resources of a JBossMQ service or JBossMessaging service resource, which itself is a child of a JBoss server instance.
Note
It can take several minutes for the new child resource to be added and visible in the JBoss ON inventory because the new resource has to be created on the agent platform and then discovered by the agent.
- Search for the JBoss messaging service to which to deploy the JMS queue or topic.
- On the details page for the selected JBoss messaging service, open the Inventory tab.
- In the Create New drop-down menu, select the or item.
- Aside from the obvious settings, like the resource name, the JMS Queue or JMS Topic entry requires two additional parameters:
- The name of the queue or topic to use as the JMX object name
- A unique JNDI name for the DataSource wrapper to use to bind under
Additional settings are available under the Advanced Settings area.
