For the deployment follow the same steps as for the Universal driver. Instead of db2jcc.jar use
db2java.zip and rename it to db2java-8.1.8.jar, you will still need to add the license drivers.
The plan below is the one I just used to deploy the pool on my machine, note the first dependency is
pointing to the legacy driver and the JDBC driver class is COM.ibm.db2.jdbc.app.DB2Driver
When I copied the drivers to the Geronimo repo I created a com.ibm.db2 directory instead of just
plain db2, this should be reflected in the <uri> for the dependencies.
I have not tested it against a mainframe. As Matt mentioned, your runtime environment should be set
to find the specific libraries for the destination OS. I think you should have this already set as
you mentioned you used to use the legacy driver so far.
<?xml version="1.0" encoding="UTF-8"?>
<connector configId="user/database-pool-DB2_Test/1/car"
xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.0";>
<dependency>
<uri>com.ibm.db2/db2java/8.1.8/jar</uri>
</dependency>
<dependency>
<uri>com.ibm.db2/db2jcc_license_cu/8.1.8/jar</uri>
</dependency>
<dependency>
<uri>com.ibm.db2/db2jcc_license_cisuz/8.1.8/jar</uri>
</dependency>
<resourceadapter>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface>
<connectiondefinition-instance>
<name>DB2_Test</name>
<config-property-setting
name="Password">db2admin</config-property-setting>
<config-property-setting
name="CommitBeforeAutocommit">false</config-property-setting>
<config-property-setting
name="Driver">COM.ibm.db2.jdbc.app.DB2Driver</config-property-setting>
<config-property-setting
name="ExceptionSorterClass">org.tranql.connector.AllExceptionsAreFatalSorter</config-property-setting>
<config-property-setting
name="UserName">db2admin</config-property-setting>
<config-property-setting
name="ConnectionURL">jdbc:db2://localhost:50000/SAMPLE</config-property-setting>
<connectionmanager>
<local-transaction/>
<single-pool>
<match-one/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
</connector>
HTH
Cheers!
Hernan
Matt Hogstrom wrote:
By legacy driver you mean the Type 2 driver?
I haven't tried it but I would expect that there are at least two
changes that need to be made. First, you'll need to ensure that your
runtime environment is setup to find the dlls or so's depending on the
target OS. The second is when deploying the driver you'll need to
specify that the DriverType is 2 and not 4.
Can you provide some additional detail on how your setting this up ?
Fran Varin wrote:
The examples that I have found (and implemented) refer to configuring
the DB2
Universal Driver with Geronimo. Up until this point we have used the
legacy
driver as opposed to the Unerval Driver. Does anyone have any
information on
how to configure the legacy driver with Geronimo?
--
View this message in context:
http://www.nabble.com/Configuring-DB2-CLI-%22legacy%22-driver-with-Geronimo-t1374822.html#a3689906
Sent from the Apache Geronimo - Users forum at Nabble.com.
