Configuring Access to a Database Using the Oracle JDBC Driver

13-10 Oracle Complex Event Processing Administrators Guide element element namecom.bea.core.datasource.serviceObjectClassname valuejavax.sql.XADataSourcevalue element properties use-xa-data-source-interfacetrueuse-xa-data-source-interface driver-params Table 13–4 describes the relevant properties. For more information, see Section 13.2.2, Custom Data Source Configuration .

5. Stop and start the Oracle CEP server.

For more information, see Section 1.5.4, Starting and Stopping Oracle CEP Servers . 13.5.2 How to Access a Database Driver Using an Application Library Built With Oracle CEP IDE for Eclipse This procedure describes how to create an OSGi bundle for your driver using the Oracle CEP IDE for Eclipse and deploy it on the Oracle CEP server. This is the preferred method. If do not wish to manually configure the activator implementation, see Section 13.5.1, How to Access a Database Driver Using an Application Library Built With bundler.sh . For more information, see Creating Application Libraries in the Oracle Complex Event Processing Developers Guide for Eclipse. To access a database driver using an application library built with Oracle CEP IDE for Eclipse:

1. Using the Oracle CEP IDE for Eclipse, create a new Oracle CEP project.

For more information, see Creating Oracle CEP Projects in the Oracle Complex Event Processing Developers Guide for Eclipse.

2. Right-click your project folder and select New Folder.

3. Enter lib in the Folder name field and click Finish.

4. Outside of the Oracle CEP IDE for Eclipse, copy your JDBC JAR file into the lib

folder.

5. Inside the Oracle CEP IDE for Eclipse, right-click the lib folder and select

Refresh . The JAR file appears in the lib folder as Figure 13–2 shows. Table 13–3 driver-params Child Element 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.