JBoss.orgCommunity Documentation

Chapter 9. Adding Resources

Other resources, in addition to applications, can be added to your JBoss Application Server instance using the Administration Console. In fact whether you adding new resources or modifying resources already deployed to the running server, the Administration Console offers easy management of the resource properties avoiding error-prone editing of XML configuration files.

Similar to deploying an application, choose the specific type of resource you want to add from the navigation panel (for example, Local Tx Datasources rather than just Datasources), this will bring up the Summary tab for this type. Next hit the Add a new resource button on the right hand side of the main panel. You will be prompted for the template that will be used to create the configuration.

A template is just a set of suggested values to use for the properties defined on that resource. For example, the Oracle templates contain suggested values that are typically used when creating a Datasource for connecting to an Oracle database. Your template choices for datasource types are:

After selecting the appropriate template, click CONTINUE. Add the appropriate configuration information for the datasource. Next to each editable property is a description detailing the use of the property, default value if any, and the affect of the property change. Common configuration errors are detected and will be highlighted after attempting to save. Check the Unset box if the property will not be used. At the end of your configuration session, click SAVE at the bottom of the page which deploys the configuration information to the server. Click CANCEL if you decide not to create the new resource.

After you have saved the new configuration the main panel should return to displaying a list of resources along with a message about whether or not the resource creation succeeded.


Any database drivers needed for the Datasource to function correctly must be deployed to the JBoss Application Server instance separately.

A similar procedure works for creating JMS Destinations and Connection Factories. For Connection Factories however the required resource adapter must already be deployed prior to configuring the connection factory. If this has not yet been done, simply navigate to the Resource Adapters (RAR)s or Enterprise Application (EAR)s (for a resource adapter deployed as part of an Enterprise Archive) and deploy the adaptor JAR file.