[jboss-jira] [JBoss JIRA] Assigned: (JBAS-1863) Add DSTOOL (Contributed Code) to help users prepare and test datasources

Add DSTOOL (Contributed Code) to help users prepare and test datasources ------------------------------------------------------------------------ Key: JBAS-1863 URL: https://jira.jboss.org/jira/browse/JBAS-1863 Project: JBoss Application Server Issue Type: Patch Security Level: Public(Everyone can see) Components: Management services Affects Versions: JBossAS-4.0.2 Final Environment: All platforms (same contributed web app/war file works in all versions) Reporter: James Ross Assignee: Jesper Pedersen Priority: Minor Original Estimate: 1 day Remaining Estimate: 1 day The dstool.war (source included) file has been provided to Ivelin Ivanov via email - I don't know how to attach it here. You can contact me at jdross(a)co.pinellas.fl.us for a resubmittal of the code. Here's the details I provided Ivelin: All our application code at Pinellas County, Floriday is based on fast J2C connection-pooled datasource database interaction. One of the items we really had to overcome with the "vanilla" JBoss was the exposed passwords. In the JBoss training class, our people learned JBoss' technique for using the login-config.xml file to create encoded authentication entries, in conjunction with the datasource entry in the oracle-ds.xml file. But its really a pain to futz all that together. The other problem with datasources - on any ap server is figuring out if they work after you set them up -- if it doesn't work, is the problem the application code not calling the datasource correctly, or the oracle-ds.xml entry, or the login-config.xml entry, or a bad password -- the list is endless - and JBoss doesn't provide a nice way to test the configuration. So over the Memorial Day Holiday, we created the Datasource Tools Web App. Its all in the dstool.war file, attached (unfortunately not attached on this form, cause I don't know how - but available from jdross(a)co.pinellas.fl.us or from Ivelin). It creates the application-policy stanza for the login-config.xml file, and the local-tx-datasource stanza for the xxx-ds.xml file - all based on some simple entries on a web form. It doesn't modify the files - it just creates the entries for you to cut-and-paste into the files - that way its non-interfering, and requires no setup to find the files. Then, after you setup the the datasource, the Tools Web App provides a really simple means of testing the datasource - and timing its performance. Our interest is primarily in Oracle and MySQL, but to make the tool more general, I've expanded it to also include setup and testing for DB2, HSQL, Postgres, and MS SQL Server. JBoss provides information on 34 different databases (counting the XA variants) - if you find this tool of use, I can expand it to prep/test for the other 28 databases - expansion is just a matter of adding entries to the pcg.dstools.DsDefs.java file - but it would be helpful to have someone at JBoss check it. But first, let me know if there's any interest at all in including this tool with the JBoss distro. No doubt, you have bigger plans for the future in the way of a Datasource Console - but for now, a simple tool makes life a lot easier. To look at it, just drop the attached dstool.war file (provided to Ivelin) into JBOSS_HOME/server/default/deploy then go to: http://localhost:8080/dstool You can run through the tool whether or not you have any datasources defined on the system.