Petstore 1.3 with Oracle 8.1.7 on Solaris 9 - deployment error

Question

Hello,
I'm trying to get Petstore 1.3 shipped with WebLogic Server 7.0 to work with Oracle
8.1.7 on Solaris 9 with a third-party (Oracle) jdbc driver (classes12). I did
the following:
1) created a new connection pool with the correct Oracle database URL and driver
class name (oracle.jdbc.driver.OracleDriver), also user/password properties for
the Oracle db, and the WL server selected in targets;
2) created a database schema for Oracle based on the data in Pointbase and the
weblogic-cmp-rdbms-jar file as well as petstore_catalog_utf8.sql;
3) created a new tx datasource pointing to the Oracle conn pool;
4) modified the catalog component's ejb-jar.xml file's env-entry to contain CatalogOracleDAOImpl;
5) put weblogic.jar in the classpath;
6) used Java's dbping utility to check connection to the database via the Oracle
driver (works fine--no network adapter error or anything related).
I then rebuilt the ear files (build is successful), but when deploying get the
following error:
"Cannot deploy EJB AccountEJB from customerEjb.jar. Cannot find datasource for
JNDI datasource-petstorePool" and says to make sure the JNDI name and deployment
descriptors are correct (I checked the customer component's deployment descriptors
against the tx datasources' JNDI and they match).
What step(s) am I missing? Any suggestions on what else I need to modify would
be very much appreciated.
Thanks,
Beverly Claire

Answer 1

Beverly:
If you have 8.1, then you should be able to simply and easily create a
connection pool to petstore via the console.
The current error you encountering: "petstorePool does not exist" is
because either:
petstorePool is not defined or there was a failure when the pool was first
created trying to connect to the DBMS.
The full errror should be in the log file prior to the TXDatasource error.
Cheers
mbg
"Beverly Claire" <[email protected]> wrote in message
news:[email protected]...
>
Hello Rob,
Thanks for your reply. Yes, the tx datasource's JNDI name isdatasource-petstorePool.
The server log says that "petstorePool does not exist".
My conn pool contents:
Name: petstorePool
URL: jdbc:oracle:thin:@<replaced with db address>:<replaced with dbport>:<replaced
with db SID>
Driver Class Name: oracle.jdbc.driver.OracleDriver
Properties: user=<replaced with username*>
password=<replaced with password*>
*same username and password used to set up the Petstore tables in Oracledb.
>
My tx datasource contents:
Name: PetstoreDataSource
JNDI: datasource-petstorePool
Pool Name: petstorePool
No, actually we're not evaluating in the sense of just-trying-things-out.One
of our clients is considering an application server. They're relying on usfor
help in choosing which would be best. As of now, we are comparing BEA WLServer
7 and 8.1, Sun ONE Application Server 7 EE, Oracle 9i Application Server,and
Fujitsu Interstage v5 Application Server. For cluster testing andperformance
comparison purposes, we'd like to use the same J2EE Application across allservers,
and the obvious choice is Petstore 1.3. One aim is to smoothly connect toan Oracle
database. The other app servers provide setup scripts and databaseschemas for
Petstore-with-Oracle, so db conn and deployment are not a problem at all.As for
WL, we've been trying to get Petstore (both the version downloaded fromSun's
Java Blueprints and the version that shipped with WL 7) to work withOracle, but
no luck so far. It's getting a bit frustrating, given the ease with whichthings
worked out with the other app servers.
Yes, I've tried out Avitek MedRec for WL 8.1, and this time BEA has kindlymade
provisions for Oracle db, so connection to Oracle is not a problem. I'mhoping
BEA will come around to doing the same thing for Petstore, although I'mguessing
that won't be in the near future.
Any other suggestions would be much appreciated.
Thanks,
Bevery Claire