Oracle Stream Analytics includes the Oracle 12c Thin driver for use with Java SE 7. The JDBC Thin driver is a pure Java, Type IV driver that you can be use in applications and applets. It is platform-independent and does not require any additional Oracle software on the client side. The JDBC Thin driver communicates with the server using SQL*Net to access the Oracle Database.

The Oracle 12c Thin drive is in the following JAR file:

/Oracle/Middleware/wlserver/modules/com.bea.oracle.ojdbc6_1.0.0.0_11-2-0-3-0.jar

For more information, see:

• Supported Databases

• Configure Access to a Database with an Oracle JDBC Driver

• http://www.oracle.com/technetwork/database/application-development/index-099369.html.

Oracle Stream Analytics servers support different databases depending on the type of JDBC driver you use.

By default, the Oracle Stream Analytics server creates a local transaction manager. The transaction manager depends on a configured RMI object, as described in JMX Configuration Objects. Oracle Stream Analytics server guarantees that there will never be more than one transaction manager instance in the system.

If a database is unavailable when you start Oracle Stream Analytics server, by default, an Oracle Stream Analytics server data source retries every 10 seconds until it creates a connection. The retries enable the Oracle Stream Analytics server to start when a database is unavailable. You can change the retry interval by providing a value for the connection-creation-retry-frequency-seconds child element of the connection-pool-params element. A value of zero disables connection retry.

The Oracle Stream Analytics server config.xml file requires a configuration element for each data source that is to be created at runtime that references an external JDBC module descriptor.

When you create an Oracle Stream Analytics domain with the Configuration Wizard, you can optionally configure a JDBC data source that uses one of the two supported Data Direct JDBC drivers. In this case the wizard updates the config.xml file for you. When you configure the data source, you provide basic information, such as the database you want to connect to, and the connection user name and password.

You can also update the config.xml file manually by adding a data-source element as the following example shows.

<data-source>
    <name>rdbms</name>
    <data-source-params>
        <global-transactions-protocol>None</global-transactions-protocol>
    </data-source-params>
    <connection-pool-params>
        <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
        <initial-capacity>5</initial-capacity>
        <max-capacity>10</max-capacity>
        <connection-creation-retry-frequency-seconds>
            60
        </connection-creation-retry-frequency-seconds>
    </connection-pool-params>
    <driver-params>
        <url>jdbc:oracle:thin:@localhost:5521:rdb</url>
        <driver-name>oracle.jdbc.OracleDriver</driver-name>
        <properties>
            <element><name>user</name><value>scott</value></element>
            <element><name>password</name><value>tiger</value></element>
        </properties>
        <use-xa-data-source-interface>true</use-xa-data-source-interface>
    </driver-params>
</data-source>
<transaction-manager>
    <name>TM</name>
    <rmi-service-name>RMI</rmi-service-name>
</transaction-manager>

A data source depends on the availability of a local transaction manager. You can rely on the default Oracle Stream Analytics server transaction manager or configure one with the transaction-manager element in config.xml as the example shows. The transaction manager depends on a configured RMI object, as described in JMX Configuration Objects.

If a database is unavailable when you start Oracle Stream Analytics server, by default, an Oracle Stream Analytics server data source retries every 10 seconds until it creates a connection. The retries enable Oracle Stream Analytics server to start when a database is unavailable. The example changes the retry interval in the config.xml file by providing a value for the connection-creation-retry-frequency-seconds child element of the connection-pool-params element. In the example, the value is 60 seconds.

The Java API Reference for Oracle WebLogic Server provides a WLConnection interface that contains methods for getting and manipulating Oracle data sources. For example, the following Java code gets the native Oracle database connection from the pooled connection object.

private DataSource ods;
private Connection wlConnection;
private OracleConnection connection;

wlConnection = ods.getConnection();
connection = (OracleConnection) ((WLConnection) wlConnection)
.getVendorConnection();

This procedure describes how to create an OSGi bundle for your driver using the bundler utility and deploy it on the Oracle Stream Analytics server.

1. Execute the bundler.sh script to create an OSGi bundle that contains your driver.

   The bundler.sh script is in the /Oracle/Middleware/my_oep/oep/bin directory. The following example lists the bundler.sh command-line options and Table 12-1 describes them.

   Note:

   There is no Windows support for bundler.sh (no bundler.cmd).

   bundler.sh
       -source <jar> 
       -name <name> 
       -version <version> 
       [-factory <class>+] 
       [-service <interface>+] 
       [-stagedir <path>] 
       [-targetdir <path>] 
   

   Table 12-1 bundler.sh Command Line Options

   Argument	Description
   -source	The path of the source JAR file to be bundled.
   -name	The symbolic name of the bundle. The root of the target JAR file name is derived from the name value.
   -version	The bundle version number. All exported packages are qualified with a version attribute with this value. The target JAR file name contains the version number.
   -factory	An optional argument that specifies a space-delimited list of one or more factory classes that are to be instantiated and registered as OSGi services. Each service is registered with the OSGi service registry with name (-name) and version (-version) properties.
   -service	An optional argument that specifies a space-delimited list of one or more Java interfaces that are used as the object class of each factory object service registration. If no interface names are specified, or the number of interfaces specified does not match the number of factory classes, then each factory object will be registered under the factory class name.
   -stagedir	An optional argument that specifies where to write temporary files when creating the target JAR file. Default: ./bundler.tmp
   -targetdir	An optional argument that specifies the location of the generated bundle JAR file. Default: current working directory (.).

   The following example shows how to use the bundler.sh to create an OSGi bundle for an Oracle JDBC driver.

   bundler.sh \
       -source /scratch/drivers/com.bea.oracle.ojdbc6_1.0.0.0_11-2-0-3-0.jar \
       -name oracle12c \
       -version 12.1.3 \
       -factory oracle.jdbc.xa.client.OracleXADataSource oracle.jdbc.OracleDriver \
       -service javax.sql.XADataSource java.sql.Driver \
       -targetdir /scratch/stage
   

   The source JAR is an Oracle driver located in the C:\drivers directory. The name of the generated bundle JAR is the concatenation of the -name and -version arguments and is created in the C:\stage directory. The bundle JAR contains the files that the following example shows:

   1465 Thu Jun 29 17:54:04 EDT 2006 META-INF/MANIFEST.MF
   1540457 Thu May 11 00:37:46 EDT 2006 ccom.bea.oracle.ojdbc6_1.0.0.0_
     11-2-0-3-0.jar
   1700 Thu Jun 29 17:54:04 EDT 2006 com/bea/core/tools/bundler/Activator.class
   

   The command-line options specify that there are two factory classes to instantiate and register as an OSGi service when the bundle is activated, each under a separate object class as the following table shows.

   Table 12-2 Factory Class and Service Interface

   Factory Class	Service Interface
   oracle.jdbc.xa.client.OracleXADataSource	javax.sql.XADataSource
   oracle.jdbc.OracleDriver	java.sql.Driver

   Each service registration will be made with a name property set to oracle12c and a version property with a value of 12c. the following example shows the Oracle Stream Analytics server log messages showing the registration of the services.

   ...
   INFO: [Jun 29, 2006 5:54:18 PM] Service REGISTERED: { version=12c, name=oracle12c, objectClass=[ javax.sql.XADataSource ], service.id=23 }
   INFO: [Jun 29, 2006 5:54:18 PM] Service REGISTERED: { version=12c, name=oracle12c, objectClass=[ java.sql.Driver ], service.id=24 }
   INFO: [Jun 29, 2006 5:54:18 PM] Bundle oracle12c STARTED
   ...

2. Copy the bundler JAR to the Oracle Stream Analytics server library extensions directory.

   Because your Oracle Stream Analytics application is an application library that contains a driver, you copy it to the Oracle Stream Analytics server library extensions directory. By default the library extensions directory is in /Oracle/Middleware/user_projects/domains/<domainname>/ <servername>/modules/ext/.

3. In the Oracle Stream Analytics server config.xml file, create a custom data-source element for your driver version and add a driver-params child element as the following example shows.

   For more information, see Server Configuration Files.

       <driver-params>
         <url>jdbc:oracle:thin:@lcw2k18:1531:lcw101</url>
         <driver-name>oracle.jdbc.xa.client.OracleXADataSource</driver-name
         <properties>
           <element>
             <name>user</name>
             <value>scott</value>
           </element>
           <element>
             <name>password</name>
             <value>{3DES}EoIfSBMhnW8=</value>
           </element>
           <element>
             <name>com.bea.core.datasource.serviceName</name>
             <value>oracle12c</value>
           </element>
           <element>
             <name>com.bea.core.datasource.serviceVersion</name>
             <value>12.1.3</value>
           </element>
           <element>
             <name>com.bea.core.datasource.serviceObjectClass</name>
             <value>javax.sql.XADataSource</value>
           </element>
         </properties>
         <use-xa-data-source-interface>true</use-xa-data-source-interface>
       </driver-params>
   

   Table 12-1 describes the relevant properties.

   Table 12-3 driver-params Properties

   Property	Description
   com.bea.core.datasource.serviceName	Specifies the value of the serviceName registration property. This must match the NAME property in your Activator class.
   com.bea.core.datasource.serviceVersion	Specifies the value of the serviceVersion registration property. This must match the VERSION property in your Activator class.
   com.bea.core.datasource.serviceObjectClass	Specifies the interface name of the OSGI service registration.

4. Stop and start the Oracle Stream Analytics server.

   For more information, see Start and Stop Servers.

Optionally, you can use the bootclasspath to access your own JDBC driver.