Data source minimum required settings for Apache Derby

Derby JDBC Provider

JDBC access to the Apache Derby database using the framework already embedded in the application server. We cannot use any Version 4.0 data sources with 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 we create 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:

  • (UNIX) /tmp/sampleDB
  • (Windows) 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)

JDBC access to the Apache Derby database using the framework already embedded in the application server.

• 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 we create 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:

  • (UNIX) /tmp/sampleDB
  • (Windows) 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

JDBC access to the Apache Derby database using the framework already embedded in the application server.

• 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 we create 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:

  • (UNIX) /tmp/sampleDB
  • (Windows) 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)

JDBC access to the Apache Derby database using the framework 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 we create 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:

  • (UNIX) /tmp/sampleDB
  • (Windows) 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

Access only Apache Derby databases that run on the same node as the application server.

• 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:

  • (UNIX) /tmp/sampleDB
  • (Windows) 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)

Access only Apache Derby databases that run on the same node as the application server.

• 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:

  • (UNIX) /tmp/sampleDB
  • (Windows) 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

Access only Apache Derby databases that run on the same node as the application server.

• 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:

  • (UNIX) /tmp/sampleDB
  • (Windows) 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)

Access only Apache Derby databases that run on the same node as the application server.

• 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:

  • (UNIX) /tmp/sampleDB
  • (Windows) 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.

Configure a JDBC provider and data source

Configure a JDBC provider

Configure a data source

Create and configure a JDBC provider and data source using the JMX API