/com/ibm/as400/access/AS400JDBCDriver.class
chris
Please can some advise if they have experienced a similar problem.
In the jvm_stderr.log we are getting the follwoing exception when trying
to make a backend connection to the AS400
the : /com/ibm/as400/access/AS400JDBCDriver.class is present in
DocumentRoot and jt400.jar is in /usr/WebSphere/AppServer/classes.
The CLASSPATH contains:
/usr/WebSphere/AppServer/hosts/default_host/default_app/servlets
/usr/WebSphere/AppServer/servlets/
/cbsap/cbs/current/share/htdocs/ (document root)
/usr/lpp/db2_06_01/java/db2java.zip
/usr/WebSphere/AppServer/classes
Why is it not finding this?
SW Levels : WAS 3.5 FIX PACK2
db2 6.1.0.27
AIX 4.3.3 (ML 2)
----------------------------------------------------------------------
com.aquarius.utility.exception.AqBackendException
Generic Error Code: 14001
User Error: Could not find JDBC driver class:
com.ibm.as400.access.AS400JDBCDriver
Technical Error: Error connecting communication object.
Exceptions involved:
java.sql.SQLException: Could not find JDBC driver class:
com.ibm.as400.access.A
S400JDBCDriver
Error occurs in: Wed Dec 06 10:55:25 GMT+00:00 2000
Error occurs in: Wed Dec 06 10:55:25 GMT+00:00 2000
at
com.aquarius.backend.connection.JDBC.AqJdbcCommunication.connect(AqJd
bcCommunication.java)
at
COM.footprint.ibs.psBackendConnection.base.IBSConnectionManager.getCo
mmunication(IBSConnectionManager.java)
at
COM.footprint.ibs.psBackendConnection.base.IBSConnectionManager.execu
te(IBSConnectionManager.java)
at
COM.footprint.ibs.virtualBranch.virtualTellerManagement.VirtualTeller
Manager.executeInProcess(VirtualTellerManager.java)
at
COM.footprint.ibs.virtualBranch.virtualTellerManagement.VirtualTeller
Manager.execute(VirtualTellerManager.java)
at
COM.footprint.ibs.psBackend.framework.IBSBackendServiceController.exe
cute(IBSBackendServiceController.java)
at
COM.footprint.ibs.psBackendController.jdbc.JdbcQueryController.execut
e(JdbcQueryController.java)
at
com.aquarius.backend.connection.JDBC.JdbcQueryServiceController.execu
te(JdbcQueryServiceController.java)
at
com.aquarius.backend.BackendServiceController.processRequest(BackendS
erviceController.java)
at
com.aquarius.backend.BackendServiceController.execute(BackendServiceC
ontroller.java)
at
com.aquarius.ps.serviceHandler.AqServiceHandler.callBackendServiceCon
troller(AqServiceHandler.java)
at
com.aquarius.homePage.serviceHandler.ViewHomePageServiceHandler.getRe
alAccountNumber(ViewHomePageServiceHandler.java)
at
com.aquarius.homePage.serviceHandler.ViewHomePageServiceHandler.proce
ssCreditCardHoldings(ViewHomePageServiceHandler.java)
at
com.aquarius.homePage.serviceHandler.ViewHomePageServiceHandler.proce
ssIntermediateOutput(ViewHomePageServiceHandler.java)
at
com.aquarius.homePage.serviceHandler.ViewHomePageServiceHandler.backe
ndProcess(ViewHomePageServiceHandler.java)
at
com.aquarius.ps.serviceHandler.AqServiceHandler.processService(AqServ
iceHandler.java)
at
com.aquarius.homePage.servlet.ViewHomePageServlet.processService(View
HomePageServlet.java)
at com.aquarius.ps.servlet.AqServlet.service(AqServlet.java)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(Servlet
Manager.java:580)
Regards
Chris Onions
IBM Global Services,
I.T.S, Infrastructure & Consultancy Services
Frances Stewart
- From the administrative console, Topology view, select the application server (e.g. Default Server). The properties for the app server are displayed in the right-hand pane.
- Stop the application server if it is running (you don't absolutely have to stop it at this step, but the apply should go faster, and you will need to restart the appserver after setting the classpath).
- Add the following to the Command line arguments property (if you have other setting here separate this from them with a blank (space)):
- -classpath /usr/WebSphere/AppServer/classes/jt400.jar
- Click the Apply button. Wait for the apply to complete successfully.
- Start the application server.
chris
That has done the trick ... thanks
But now the problem has evolved to :
User Error: The URL default library is not valid
Technical Error: Error connecting communication object.
Exceptions involved
java.sql.SQLException: The URL default library is not valid
Error occurs in: Wed Dec 06 13:53:10 GMT+00:00 2000 at
com.aquarius.backend.connection.JDBC.AqJdbcCommunication.connect(AqJdbcCommunication.java)
at
COM.footprint.ibs.psBackendConnection.base.IBSConnectionManager.getCommunication(ICBSConnectionManager.java)
at
COM.footprint.ibs.psBackendConnection.base.IBSConnectionManager.execute(ICBSConnectionManager.java)
at
COM.footprint.ibs.virtualBranch.virtualTellerManagement.VirtualTellerManager.execute(VirtualTellerManager.java)
at
COM.footprint.ibs.psBackend.framework.IBSBackendServiceController.execute(IBSBackendServiceController.java)
at
COM.footprint.ibs.psBackendController.jdbc.JdbcQueryController.execute(JdbcQueryController.java)
at
com.aquarius.backend.connection.JDBC.JdbcQueryServiceController.execute(JdbcQueryServiceController.java)
at com.aquarius.
backend.BackendServiceController.processRequest(BackendServiceController.java)
at
com.aquarius.backend.BackendServiceController.execute(BackendServiceController.java)
We have checked the urls that we are using and nothing seems to be wrong
!
We know the box has connectivety to the AS400 due to the fact that the
server was previously configured and worked using WAS 2.3 and the same
urls: that we are using now !
Any further ideas
Regards
Chris Onions
IBM Global Services,
I.T.S, Infrastructure & Consultancy Services
Frances Stewart wrote:
> Try putting jt400.jar on the classpath for the application server.
> Todo this, do:
>
> 1. From the administrative console, Topology view, select the
> application server (e.g. Default Server). The properties for the
> app server are displayed in the right-hand pane.
> 2. Stop the application server if it is running (you don't
> absolutely have to stop it at this step, but the apply should go
> faster, and you will need to restart the appserver after setting
> the classpath).
> 3. Add the following to the Command line arguments property (if you
> have other setting here separate this from them with a blank
> (space)):
> o -classpath /usr/WebSphere/AppServer/classes/jt400.jar
> 4. Click the Apply button. Wait for the apply to complete
> successfully.
> 5. Start the application server.
>
>
> chris wrote:
>
>> Hello Folks,
>>
>> Please can some advise if they have experienced a similar problem.
>>
>> In the jvm_stderr.log we are getting the follwoing exception when
>> trying
>> to make a backend connection to the AS400
>> the : /com/ibm/as400/access/AS400JDBCDriver.class is present in
>> DocumentRoot and jt400.jar is in /usr/WebSphere/AppServer/classes.
>>
>> The CLASSPATH contains:
>>
>> /usr/WebSphere/AppServer/hosts/default_host/default_app/servlets
>> /usr/WebSphere/AppServer/servlets/
>> /cbsap/cbs/current/share/htdocs/ (document root)
>> /usr/lpp/db2_06_01/java/db2java.zip
>> /usr/WebSphere/AppServer/classes
>>
>> Why is it not finding this?
>>
>> SW Levels : WAS 3.5 FIX PACK2
>> db2 6.1.0.27
>> AIX 4.3.3 (ML 2)
>>
>> ----------------------------------------
>> -----------------------------
>> com.aquarius.utility.exception.AqBackendException
>> Generic Error Code: 14001
>> User Error: Could not find JDBC driver class:
>> com.ibm.as400.access.AS400JDBCDriver
>> Technical Error: Error connecting communication object.
>> Exceptions involved:
>> java.sql.SQLException: Could not find JDBC driver class:
>> com.ibm.as400.access.A
>> S400JDBCDriver
>>
>> Error occurs in: Wed Dec 06 10:55:25 GMT+00:00 2000
>> Error occurs in: Wed Dec 06 10:55:25 GMT+00:00 2000
>>
>> at
>> com.aquari
>> s.backend.connection.JDBC.AqJdbcCommunication.connect(AqJd
>> bcCommunication.java)
>> at
>> COM.footpr
>> nt.ibs.psBackendConnection.base.IBSConnectionManager.getCo
>> mmunication(IBSConnectionManager.java)
>> at
>> COM.footpr
>> nt.ibs.psBackendConnection.base.IBSConnectionManager.execu
>> te(IBSConnectionManager.java)
>> at
>> COM.footpr
>> nt.ibs.virtualBranch.virtualTellerManagement.VirtualTeller
>> Manager.executeInProcess(VirtualTellerManager.java)
>> at
>> COM.footpr
>> nt.ibs.virtualBranch.virtualTellerManagement.VirtualTeller
>> Manager.execute(VirtualTellerManager.java)
>> at
>> COM.footpr
>> nt.ibs.psBackend.framework.IBSBackendServiceController.exe
>> cute(IBSBackendServiceController.java)
>> at
>> COM.footpr
>> nt.ibs.psBackendController.jdbc.JdbcQueryController.execut
>> e(JdbcQueryController.java)
>> at
>> com.aquari
>> s.backend.connection.JDBC.JdbcQueryServiceController.execu
>> te(JdbcQueryServiceController.java)
>> at
>> com.aquari
>> s.backend.BackendServiceController.processRequest(BackendS
>> erviceController.java)
>> at
>> com.aquari
>> s.backend.BackendServiceController.execute(BackendServiceC
>> ontroller.java)
>> at
>> com.aquari
>> s.ps.serviceHandler.AqServiceHandler.callBackendServiceCon
>> troller(AqServiceHandler.java)
>> at
>> com.aquari
>> s.homePage.serviceHandler.ViewHomePageServiceHandler.getRe
>> alAccountNumber(ViewHomePageServiceHandler.java)
>> at
>> com.aquari
>> s.homePage.serviceHandler.ViewHomePageServiceHandler.proce
>> ssCreditCardHoldings(ViewHomePageServiceHandler.java)
>> at
>> com.aquari
>> s.homePage.serviceHandler.ViewHomePageServiceHandler.proce
>> ssIntermediateOutput(ViewHomePageServiceHandler.java)
>> at
>> com.aquari
>> s.homePage.serviceHandler.ViewHomePageServiceHandler.backe
>> ndProcess(ViewHomePageServiceHandler.java)
>> at
>> com.aquari
>> s.ps.serviceHandler.AqServiceHandler.processService(AqServ
>> iceHandler.java)
>> at
>> com.aquari
>> s.homePage.servlet.ViewHomePageServlet.processService(View
>> HomePageServlet.java)
>> at com.aquarius.ps.servlet.AqServlet.service(AqServlet.java)
>>
>> at
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
>> at
>> com.ibm.se
>> vlet.engine.webapp.StrictServletInstance.doService(Servlet
Frances Stewart
They are setting the default library (in the URL) to DB2A01AB26. Could it be that this library does not exist? That's the only thing I can think of right now. If that is not the case, it would be interesting to see the database host server job log to see if anything odd shows up there.
Frances Stewart
Are you using the WebSphere Datasource and JDBC Driver objects in your code? OR are you getting your own JDBC connection, etc.?
If you are using the WebSphere DataSource and JDBC Driver objects, your settings should be as follows:
JDBC Driver
Name: DB2AS400JDBCDriver (or whatever makes sense to you)DataSource
Class Name: com.ibm.as400.access.AS400JDBCDriver (should be found from the drop-down list)
URL Prefix: jdbc:as400 (should be filled in automatically for you)
JTA Enabled: False (this is the default and should stay as false)
Data Source Name: AqJdbcDb2_3 (or whatever makes sense to you)
Database name: 9.9.9.9/DB2A01AB26;errors=full;libraries=DB2A01AB26,DB2A01PDN1,ICBSANUS26,ICBSANUD26,AQSGOLD2;package=aqs261;package
library=DB2A01AB26
(all one line, where 9.9.9.9 is your system IP address or host name, DB2A01AB26 is the default schema or collection/library and the rest are any JDBC connection properties you wish to pass on.)
Chris Onions wrote:
From our AS400 team:
I have just been onto the D26 environment to double check and yes the
DB2A01AB26 definitely exists. This is the FISERV DB2 database which has to
be there.Also the AS400 team say that they are unaware of any logs which would help us !
Any other ideas ?
Chris
Chris Onions
I have just been onto the D26 environment to double check and yes the
DB2A01AB26 definitely exists. This is the FISERV DB2 database which has to
be there.
Also the AS400 team say that they are unaware of any logs which would help us !
Any other ideas ?
Chris