Additional Steps for Using JBoss AS 7

If you're using JBoss EAP or Wildfly as your application server and Oracle, SQL Server, or DB2 as your database, an additional set of steps is required to handle the JDBC driver. If you're using a driver different from the one supplied with JasperReports Server, you should have already downloaded a JDBC driver jar for your database type. (See Working With JDBC Drivers, if you have not yet done this.)

You need to make an explicit reference to your JDBC driver file name so that JBoss EAP/Wildfly will know the exact file name.

1. Update your default_master.properties file to specify the exact name (artifactId and version) of your JDBC driver:

Edit: <js-install>/buildomatic/default_master.properties

Look for the section "Setup JDBC Driver"

Uncomment and edit these two lines:

# maven.jdbc.artifactId=ojdbc5

# maven.jdbc.version=11.2.0

So that they look like this:

maven.jdbc.artifactId=ojdbc5

maven.jdbc.version=11.2.0

(This will work for a driver with the filename: ojdbc5-11.2.0.jar)

2. Edit your jboss-deployment-structure.xml file so that the JDBC filename is specified:

Edit: <js-install>/buildomatic/install_resources/jboss/jboss-deployment-structure.xml

Look for the section "Setup JDBC Driver"

Uncomment and edit the line for your database type (for instance):

<!-- <resource-root path="WEB-INF/lib/ojdbc5-11.2.0.jar" use-physical-code-source="true"/> -->

So that it looks like this:

<resource-root path="WEB-INF/lib/ojdbc5-11.2.0.jar" use-physical-code-source="true"/>

(This will work for a driver with the filename: ojdbc5-11.2.0.jar)

Note: If your JDBC driver filename does not have a version number, you may need to rename the file and give it a version number.

For instance, if you have a file named: sqljdbc4.jar

You can rename it with a "dummy" version number: sqljdbc4-1.0.jar

Then the artifactId and version can look like this: 

maven.jdbc.artifactId=sqljdbc4

maven.jdbc.version=1.0

Feedback
randomness