Integrating NonStop JDBC Type 4 Driver With JBoss Applications

Check that the EAR file is complete and inspect the WAR file and each of the EJB jar files produced

by the build to ensure they contain all the necessary components (classes, descriptors, and so on).

Note: There may be some JMS related errors that you can safely ignore because the Duke’s Bank

sample does not use any JMS code.

You can safely redeploy the application if it is already deployed. To undeploy it, you just have to

remove the archive from the deploy directory. There’s no need to restart the server in either case. If

everything seems to have gone well up to this point, then point your browser at the following

application URL:

http://localhost:8080/bank/main

You should then be forwarded to the application login page. As explained in the tutorial, you can log

in with a customer ID of “200” and the password “j2ee”. If you receive an error at this point, check

again to ensure that you have set up the database correctly, as described in the “Configuring JDBC

Type 4 data source for the JBoss Application Server” section. In particular, check that the connection-

url is correct. Then ensure that you have populated the database with data.

You should also be able to run the standalone client application using the following command:

ant -f jboss-build.xml run-client

This is a Swing graphical user interface (GUI) client, which allows you to administer the customers

and accounts.

Information about further customization to the Duke’s Application can be found online from the JBoss

site at the following URL:

http://www.jboss.org/modules/html/docs/jbossj2ee.pdf

Conclusion

The Type 4 Driver supports the portability goal of fast ROI with absolute minimum application change.

This sample indicates how applications written for a third-party JDBC driver can to be executed on the

Type 4 Driver with just runtime configuration changes. It highlights that the Type 4 Driver’s JDBC

standards compliance helps you port existing applications or write new ones to use the NonStop

SQL/MX or SQL/MP Database via any platform.

The example here is only intended to get you up and running with integrating NonStop SQL/MX

Database and the Type 4 Driver with the JBoss Application Server. The applications are not intended

to reflect how you should go about writing production J2EE software, as there are differences of

opinion on this subject.

Ordering Information

The NonStop JDBC Type 4 Driver is an Independent Product that can be ordered using the part

number SJ82V1.

The platform used must have Java 1.4.1 or later running on it.