Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

Then you select the JDBC drivers which, by default, it has been pre-filled based on the database type you selected in the previous step. You also have to select the driver JAR from the pullscroll-down menu and then specify the database name. For this example a test database was previously created, this is a single step procedure and it is explained in Create a database.

...

Once deployed, Derby_Test should be listed along with all the other database pools.

Alternatively you could create your own deployment plan and deploy the database connection pool directly from the commad line with the Deployer tool. The following example illustrates the deployment plan that can be used to deploy the same database pool you just deployed via the Administration Console.

Code Block
xml
xml
borderStylesolid
titleDerby_Test-plan.xml

<?xml version="1.0" encoding="UTF-8"?>
<connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2">
    <dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2">
        <dep:moduleId>
            <dep:groupId>console.dbpool</dep:groupId>
            <dep:artifactId>Derby_Test</dep:artifactId>
            <dep:version>1.0</dep:version>
            <dep:type>rar</dep:type>
        </dep:moduleId>
        <dep:dependencies>
            <dep:dependency>
                <dep:groupId>org.apache.derby</dep:groupId>
                <dep:artifactId>derby</dep:artifactId>
                <dep:version>10.1.3.1</dep:version>
                <dep:type>jar</dep:type>
            </dep:dependency>
        </dep:dependencies>
    </dep:environment>
    <resourceadapter>
        <outbound-resourceadapter>
            <connection-definition>
                <connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface>
                <connectiondefinition-instance>
                    <name>Derby_Test</name>
                    <config-property-setting name="Driver">org.apache.derby.jdbc.EmbeddedDriver</config-property-setting>
                    <config-property-setting name="ConnectionURL">jdbc:derby:test</config-property-setting>
                    <connectionmanager>
                        <local-transaction/>
                        <single-pool>
                            <max-size>10</max-size>
                            <min-size>0</min-size>
                            <match-one/>
                        </single-pool>
                    </connectionmanager>
                </connectiondefinition-instance>
            </connection-definition>
        </outbound-resourceadapter>
    </resourceadapter>
</connector>

If you want to use this option copy this file to you local drive and run the following command from the <geronimo_home>\bin directory:

deploy --user system --password manager deploy <plan_home>\Derby_Test-plan.xml ..\repository\org\tranql\tranql-connector-ra\1.3\tranql-connector-ra-1.3.rar

You should see a confirmation message similar to the one shown in the following example.

No Format
bgColor#000000
borderStylesolid

d:\geronimo-jetty-j2ee-1.2\bin>deploy --user system --password manager deploy \tmp\Derby_Test-plan.xml ..\repository\org\tranql\tranql-connector-ra\1.3\tranql-connector-ra-1.3.rar
Using GERONIMO_BASE:   D:\geronimo-jetty-j2ee-1.2
Using GERONIMO_HOME:   D:\geronimo-jetty-j2ee-1.2
Using GERONIMO_TMPDIR: D:\geronimo-jetty-j2ee-1.2\var\temp
Using JRE_HOME:        C:\Java\jdk1.5.0_06\\jre
    Deployed console.dbpool/Derby_Test/1.0/rar

For further details on this option refer to the Deployment plans section.