Data source minimum required settings for Apache Derby

Set the appropriate properties on every data source configured. These settings are for Apache Derby data sources.

We can configure the following types of providers:

• Derby JDBC Provider

• Derby JDBC Provider (XA)

• Derby JDBC Provider 40

• Derby JDBC Provider 40 (XA)

• Derby Network Server using Derby Client

• Derby Network Server using Derby Client (XA)

• Derby Network Server using Derby Client 40

• Derby Network Server using Derby Client 40 (XA)

• Derby JDBC Provider

  The Derby JDBC driver provides JDBC access to the Apache Derby database using the framework that is already embedded in the application server. We cannot use any Version 4.0 data sources with this provider.

  This provider:

  • Is configurable only in nodes at version 6.0.2 and later

  • Supports one phase data source with the following class:
    org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource

  • Requires the JDBC driver file:

    • derby.jar

      The full path name is ${DERBY_JDBC_DRIVER_PATH}/derby.jar. When creating a connection through the application server, the environment variables are set automatically.

  • Requires the following DataStoreHelper class:
    com.ibm.websphere.rsadapter.DerbyDataStoreHelper

  • Requires the following properties:

    databaseName

    The name of the database from which the data source obtains connections. If we do not specify a fully qualified path name, the application server uses the default location of app_server_root/derby or the equivalent default for AIX , HP-UX, Linux, or Solaris system environments. An example for the database path name is:

    • /tmp/sampleDB

    • c:\temp\sampleDB

    If no database exists for the path name to specify, configure the custom property, createDatabase, to a value of create to create the database dynamically.

• Derby JDBC Provider (XA)

  The Derby JDBC driver (XA) provides JDBC access to the Apache Derby database using the framework that is already embedded in the application server.

  This provider:

  • Does not support use Version 4.0 data sources.

  • Is configurable only in nodes at version 6.0.2 and later

  • Supports the two-phase data source with the following class:
    org.apache.derby.jdbc.EmbeddedXADataSource

  • Requires JDBC driver file:

    • derby.jar

      The full path name is ${DERBY_JDBC_DRIVER_PATH}/derby.jar. When creating a connection through the application server, the environment variables are set automatically.

  • Requires the following DataStoreHelper class:
    com.ibm.websphere.rsadapter.DerbyDataStoreHelper

  • Does not require a valid authentication alias.

  • Requires the following properties:

    databaseName

    The name of the database from which the data source obtains connections. If we do not specify a fully qualified path name, the application server uses the default location of app_server_root/derby or the equivalent default for AIX, HP-UX, Linux, or Solaris system environments. An example for the database path name is:

    • /tmp/sampleDB

    • c:\temp\sampleDB

    If no database exists for the path name to specify, configure the custom property, createDatabase, to a value of create to create the database dynamically.

• Derby JDBC Provider 40

  The Derby JDBC Provider 40 provides JDBC access to the Apache Derby database using the framework that is already embedded in the application server.

  This provider:

  • Is configurable only in nodes at version 7.0 and later.

  • Does not support Version 4.0 data sources.

  • Supports one phase data source with the following class:
    org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource40

  • Requires the JDBC driver file:

    • derby.jar

      The full path name is ${DERBY_JDBC_DRIVER_PATH}/derby.jar. When creating a connection through the application server, the environment variables are set automatically.

  • Requires the following DataStoreHelper class:
    com.ibm.websphere.rsadapter.DerbyDataStoreHelper

  • Requires the following properties:

    databaseName

    The name of the database from which the data source obtains connections. If we do not specify a fully qualified path name, the application server uses the default location of app_server_root/derby or the equivalent default for AIX, HP-UX, Linux, or Solaris system environments. An example for the database path name is:

    • /tmp/sampleDB

    • c:\temp\sampleDB

    If no database exists for the path name to specify, configure the custom property, createDatabase, to a value of create to create the database dynamically.

• Derby JDBC Provider 40 (XA)

  The Derby JDBC Provider 40 (XA) provides JDBC access to the Apache Derby database using the framework that is already embedded in the application server.

  This provider:

  • Is configurable only in nodes at version 7.0 and later.

  • Does not support Version 4.0 data sources.

  • Supports one phase data source with the following class:
    org.apache.derby.jdbc.EmbeddedXADataSource40

  • Requires the JDBC driver file:

    • derby.jar

      The full path name is ${DERBY_JDBC_DRIVER_PATH}/derby.jar. When creating a connection through the application server, the environment variables are set automatically.

  • Requires the following DataStoreHelper class:
    com.ibm.websphere.rsadapter.DerbyDataStoreHelper

  • Requires the following properties:

    databaseName

    The name of the database from which the data source obtains connections. If we do not specify a fully qualified path name, the application server uses the default location of app_server_root/derby or the equivalent default for AIX, HP-UX, Linux, or Solaris system environments. An example for the database path name is:

    • /tmp/sampleDB

    • c:\temp\sampleDB

    If no database exists for the path name to specify, configure the custom property, createDatabase, to a value of create to create the database dynamically.

• Derby Network Server using Derby Client

  Use this provider to access only Apache Derby databases that run on the same node as the application server.

  This provider:

  • Does not support Version 4.0 data sources.

  • Is configurable only in nodes at version 6.1 and later

  • Uses the following one phase data source for the Derby Network Server using Derby Client provider:
    org.apache.derby.jdbc.ClientConnectionPoolDataSource

  • Requires the following JDBC driver file:

    • derbyclient.jar

  • Requires DataStoreHelper class:
    com.ibm.websphere.rsadapter.DerbyNetworkServerDataStoreHelper

  • Requires the following property:

    databaseName

    The name of the database from which the data source obtains connections. If we do not specify a fully qualified path name, the application server uses the default location of app_server_root/derby or the equivalent default for AIX, HP-UX, Linux, or Solaris system environments. An example for the database path name is:

    • /tmp/sampleDB

    • c:\temp\sampleDB

    If no database exists for the path name to specify, configure the custom property, createDatabase, to a value of create to create the database dynamically.

• Derby Network Server using Derby Client (XA)

  Use this provider to access only Apache Derby databases that run on the same node as the application server.

  This provider:

  • Does not support Version 4.0 data sources.

  • Is configurable only in nodes at version 6.1 and later

  • Uses the following XA data source for this Derby Network Server using Derby Client provider:
    org.apache.derby.jdbc.ClientXADataSource

  • Requires the following JDBC driver file:

    • derbyclient.jar

  • Requires the DataStoreHelper class:
    com.ibm.websphere.rsadapter.DerbyNetworkServerDataStoreHelper

  • Requires the following property:

    databaseName

    The name of the database from which the data source obtains connections. If we do not specify a fully qualified path name, the application server uses the default location of app_server_root/derby or the equivalent default for AIX, HP-UX, Linux, or Solaris system environments. An example for the database path name is:

    • /tmp/sampleDB

    • c:\temp\sampleDB

    If no database exists for the path name to specify, configure the custom property, createDatabase, to a value of create to create the database dynamically.

• Derby Network Server using Derby Client 40

  Use this provider to access only Apache Derby databases that run on the same node as the application server.

  This provider:

  • Is configurable only in nodes at version 7.0 and later

  • Does not support Version 4.0 data sources.

  • Uses the following one phase data source for the Derby Network Server using Derby Client provider:
    org.apache.derby.jdbc.ClientConnectionPoolDataSource40

  • Requires the following JDBC driver file:

    • derbyclient.jar

  • Requires DataStoreHelper class:
    com.ibm.websphere.rsadapter.DerbyNetworkServerDataStoreHelper

  • Requires the following property:

    databaseName

    The name of the database from which the data source obtains connections. If we do not specify a fully qualified path name, the application server uses the default location of app_server_root/derby or the equivalent default for AIX, HP-UX, Linux, or Solaris system environments. An example for the database path name is:

    • /tmp/sampleDB

    • c:\temp\sampleDB

    If no database exists for the path name to specify, configure the custom property, createDatabase, to a value of create to create the database dynamically.

• Derby Network Server using Derby Client 40 (XA)

  Use this provider to access only Apache Derby databases that run on the same node as the application server.

  This provider:

  • Is configurable only in nodes at version 7.0 and later

  • Does not support Version 4.0 data sources.

  • Uses the following one phase data source for the Derby Network Server using Derby Client provider:
    org.apache.derby.jdbc.ClientXADataSource40

  • Requires the following JDBC driver file:

    • derbyclient.jar

  • Requires DataStoreHelper class:
    com.ibm.websphere.rsadapter.DerbyNetworkServerDataStoreHelper

  • Requires the following property:

    databaseName

    The name of the database from which the data source obtains connections. If we do not specify a fully qualified path name, the application server uses the default location of app_server_root/derby or the equivalent default for AIX, HP-UX, Linux, or Solaris system environments. An example for the database path name is:

    • /tmp/sampleDB

    • c:\temp\sampleDB

    If no database exists for the path name to specify, configure the custom property, createDatabase, to a value of create to create the database dynamically.

Related tasks

Configure a JDBC provider and data source

Configure a JDBC provider using the administrative console

Configure a data source using the administrative console

Create a JDBC provider and data source using the JMX API