[CORE-87] Installation process needs to put database drivers in i2b2.war/WEB-INF/lib Created: 07/Feb/14 Updated: 05/Jun/14 Resolved: 28/May/14 |
|
| Status: | Closed |
| Project: | i2b2 Core Software |
| Component/s: | Install |
| Affects Version/s: | 1.7.00 |
| Fix Version/s: | 1.7.01 |
| Type: | Bug | Priority: | Major |
| Reporter: | Karl Burke | Assignee: | Mike Mendis |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS 6.2 JBoss 7.1.1 AS Axis2 1.6.1 |
||
| Rank: | 0|i000nj: |
| Participant/s: |
| Description |
|
After completion of a new installation using the 1.7.00 Ant scripts and documentation, the jar file for the appropriate database driver is not placed in $JBOSS_HOME/standalone/deployments/i2b2.war/WEB-INF/lib. This results in failure to execute queries in the webclient subsequent to login. JBoss logs NoClassDefFoundError entries in $JBOSS_HOME/standalone/log/server.log as well. The i2b2 1.7 virtual machine has both sqljdbc4.jar and ojdbc.jar in $JBOSS_HOME/standalone/deployments/i2b2.war/WEB-INF/lib as well as $JBOSS_HOME/standalone/deployments. A current workaround for the installation process is to copy these files down into the i2b2.war/WEB-INF/lib directory. I suggest the solution is either modification of the Ant scripts, or directions in the documentation to manually copy the appropriate driver. If there is a design reason for having both drivers, rather than just the one needed for the corresponding back-end database, it would be nice if that was documented. See "i2b2 Install Help" Google Group topic "Once more?" dated 1/31/2014. https://groups.google.com/forum/#!msg/i2b2-install-help/Mv8gK9x03_Y/7m8DBdFGb5sJ |