Skip navigation.

RDBMS Event Generator

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index View as PDF   Get Adobe Reader

Introducing the BEA WebLogic RDBMS Event Generator

This section introduces the BEA WebLogic RDBMS Event Generator.

It includes the following topics:

 


About the BEA WebLogic RDBMS Event Generator

The RDBMS Event Generator is one of the WebLogic Integration event generators that you can create from the WebLogic Integration Administration Console.

The RDBMS Event Generator uses triggers to detect changes to a database table for added, deleted, or updated rows and publishes the results to Message Broker channels. You can also use the RDBMS Event Generator to run custom queries on the database table and publish the results to Message Broker channels.

To learn more about the event generators available from the WebLogic Integration Administration Console and for information on defining channel rules for the RDBMS Event Generator, see Managing Weblogic Integration Solutions.

Additional information regarding the configuration of event generators is also available in the following sections of Deploying WebLogic Integration Solutions.

 


Supported RDBMS Events

The RDBMS Event Generator enables integration with RDBMS by retrieving data from a database as XML or a CachedRowSet that can be used in a business process. This provides a convenient and simple method for integrating databases with enterprise applications using WebLogic Integration.

The RDBMS Event Generator supports asynchronous message retrieval from databases, including Oracle, Microsoft SQL Server, IBM DB2 UDB, Informix Dynamic Server, and Sybase Adaptive Server in 2 ways:

 


Supported Databases

The following databases are currently supported:

For updated information and details on supported database versions, see Supported Database Configurations section, in the Supported Configurations for WebLogic Integration 8.5 document.

 


Supported Drivers

This section lists the drivers that the BEA WebLogic RDBMS Event Generator supports on the following operating systems:

It also lists the driver class names and JDBC URLs corresponding to the drivers.

Note: The BEA WebLogic RDBMS Event Generator should be used in conjunction with a JDBC 2.1 compliant driver.

Oracle Thin Driver

The Oracle 10g 10.1.0.2.0 Thin Driver file (WL_HOME/server/lib/ojdbc14.jar) is shipped with the product.

Table 1-1 Driver Class Names and JDBC URLs for Oracle Thin Driver 

For Normal Connection

Driver Class Name

oracle.jdbc.driver.OracleDriver

JDBC URL

jdbc:oracle:thin:@hostname:port:schema_name

Example

jdbc:oracle:thin:@127.0.0.1:1521:UAT02

For XA Connection

Driver Class Name

oracle.jdbc.xa.client.OracleXADataSource

JDBC URL

jdbc:oracle:thin:@hostname:port:schema_name

Example

jdbc:oracle:thin:@127.0.0.1:1521:UAT02


 

MS SQL Server 2000 JDBC Driver

You can download the MS SQL Server 2000 JDBC Driver files (Version :2.2.0037) msutil.jar, msbase.jar, and mssqlserver.jar from the following URL:

http://www.microsoft.com/downloads/details.aspx?familyid=9f1874b6-f8e1-4bd6-947c-0fc5bf05bf71&;displaylang=en

Table 1-2 Driver Class Names and JDBC URLs for MS SQL Server 2000 JDBC Driver 

For Normal Connection

Driver Class Name

com.microsoft.jdbc.sqlserver.SQLServerDriver

JDBC URL

jdbc:microsoft:sqlserver://hostname:port;
SelectMethod=Cursor;DatabaseName=?

Example

jdbc:microsoft:sqlserver://127.0.0.1:1433;
SelectMethod=Cursor;DatabaseName=AdapterTesting

For XA Connection

Driver Class Name

com.microsoft.jdbcx.sqlserver.SQLServerDataSource

JDBC URL

jdbc:microsoft:sqlserver://hostname:port;
SelectMethod=?;DatabaseName=?;ServerName=?

Example

jdbc:microsoft:sqlserver://127.0.0.1:1433;
SelectMethod=cursor;DatabaseName=AdapterTesting;
ServerName=itpl-025019


 

DB2 JDBC Driver (JDBC 2.0 Compliant)

The DB2 JDBC Driver file, db2java.zip, is available with the database instance.

Table 1-3 Driver Class Names and JDBC URLs for DB2 JDBC Driver (JDBC 2.0 Compliant)

For Normal Connection

Driver Class Name

COM.ibm.db2.jdbc.app.DB2Driver

JDBC URL

jdbc:db2:DatabaseName

Example

jdbc:db2:DWCTRLDB

For XA Connection

Driver Class Name

COM.ibm.db2.jdbc.DB2XADataSource

JDBC URL

jdbc:db2;DatabaseName=?

Example

jdbc:db2;DatabaseName=DWCTRLDB


 

Informix Dynamic Server JDBC Driver

The Informix JDBC Driver Version 2.21 files, ifxjdbc.jar and ifxjdbcx.jar, are available with the database instance.

Table 1-4 Driver Class Names and JDBC URLs for Informix JDBC Driver

For Normal Connection

Driver Class Name

com.informix.jdbc.IfxDriver

JDBC URL

jdbc:informix-sqli://host:port/DatabaseName: INFORMIXSERVER=ServerName

Example

jdbc:informix-sqli://127.0.0.1:1526/BEADEV: INFORMIXSERVER=BEA_SVR_INFX

For XA Connection

Driver Class Name

com.informix.jdbcx.IfxXADataSource

JDBC URL

jdbc:informix-sqli://host:port/DatabaseName; ServerName=ServerName;PortNumber=port; IfxIFXHOST=host;DatabaseName=DatabaseName

Example

jdbc:informix-sqli://127.0.0.1:1526/BEADEV;ServerName=BEA_SVR_INFX;PortNumber=1526; IfxIFXHOST=127.0.0.1;DatabaseName=BEADEV


 

Sybase DataDirect Connect for JDBC

For integration with Sybase Adaptive Server databases, use the BEA WebLogic RDBMS Event Generator with DataDirect Connect for JDBC (Release 3.3). The required JDBC Driver files, util.jar, base.jar, and sybase.jar, are part of DataDirect Connect for JDBC Release 3.3.

For information about obtaining DataDirect Connect for JDBC, see the following URL:

http://www.datadirect.com/products/jdbc/jdbcindex.asp

Table 1-5 Driver Class Names and JDBC URLs for Informix JDBC Driver

For Normal Connection

Driver Class Name

com.ddtek.jdbc.sybase.SybaseDriver

JDBC URL

jdbc:datadirect:sybase://host:port; databaseName=name

Example

jdbc:datadirect:sybase://127.0.0.1:2048; databaseName=DB1

For XA Connection

Driver Class Name

com.ddtek.jdbcx.sybase.SybaseDataSource

JDBC URL

jdbc:datadirect:sybase://host:port; DatabaseName=name;ServerName=host; PortNumber=port;SelectMethod=cursor

Example

jdbc:datadirect:sybase://127.0.0.1:2048; DatabaseName=DB1;ServerName=127.0.0.1; PortNumber=2048;SelectMethod=cursor


 

 

Skip navigation bar  Back to Top Previous Next