Show Table of Contents
C.4. Change Database for the JMS Services
The JMS service in the JBoss AS uses relational databases to persist its messages. For improved performance, we should change the JMS service to take advantage of the external database. To do that, we need to replace the file
jboss-as/server/production/deploy/jms-singleton/hsqldb-jdbc2-service.xml with a file in jboss-as/docs/examples/jms/ depending on your external database. Notice that if you are using the default server profile, the file path is jboss-as/server/default/deploy/jms/hsqldb-jdbc2-service.xml.
- MySQL:
mysql-jdbc2-service.xml - PostgreSQL:
postgres-jdbc2-service.xml - Oracle:
oracle-jdbc2-service.xml - DB2:
db2-jdbc2-service.xml - Sybase:
sybase-jdbc2-service.xml - MS SQL Server:
mssql-jdbc2-service.xml
Note
Despite its name, the
hsqldb-jdbc-state-service.xml file applies to all databases. So, there is no need to use a special jdbc-state-service.xml for each database.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.