THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Anchor
This article shows you how to configure a DB2 datasource in Apache Geronimo.
In this scenario we are creating a connection pool for a DB2 database, in order to connect to that database we are required to define at least two driver jar files. They include the JDBC driver itself and the respective license files. Depending on your implementation you will need different license files.
...
These files are available in the <sqllib_home>\java directory. For additional information on the DB2 JDBC drivers and licenses visit the DB2 Information Center available at the following URL:
In order to use these files in Geronimo, rename (copy and rename) the files according to the following table.In this case we will not use db2jcc_license_cisuz.jar because it's for Z/OS and iSeries.
...
In order to use the console, Apache Geronimo must be running. Access the Geronimo Administration Console by pointing your browser to the following URL:
- Enter the system as the user and manager as the password and click Login.
- Click on Services->Repository portlet.
- Click on Browse and select the first file to install. In this case we will first install db2jcc-9.5.jar.
- A set of values will be proposed by default, set the Group: to com.ibm.db2, leave the rest by default and click Install.
- Repeat the previous two steps for db2jcc_license_cisuz-9.5.jar
...
As an alternative to the wizard, you can create a deployment plan manually and deploy it using the command line based deployer tool. To use this option create a db2-plan.xml file and copy the content of the following example.
...
Let's analyze this plan now. Take a look at the <dep:environment> section, there you can find the moduleId which identifies the resource or component being deployed; in the Administration Console the moduleId is displayed in the Component Name column on the Database Pools portlet.
...
You will receive the following message:
No Format