JDBC Input and Output Adapter

The JDBC Input adapter receives data from tables in a database and inputs it into Event Stream Processor. The JDBC Output adapter sends data from Event Stream Processor to a database table.

Commands specified in the cnxml file for this adapter cannot contain the following strings: "mv", "rm", or "del".

If your records have dates earlier than 1582, you need to remember that the JDBC driver treats these dates differently. It converts these dates from the Gregorian calendar to the Julian calendar. ESP does not alter this behavior or modify the output from the JDBC driver.

These adapters can run in managed or unmanaged mode.

Managed external adapters:

Are started and stopped by the ESP server with ESP projects.
Have a cnxml adapter configuration file that is configured within SAP Event Stream Processor Studio.
Are referenced in a CCL ATTACH ADAPTER statement.

Unmanaged external adapters:

Start and stop independently of the ESP server and ESP projects.
Are configured independently.
Are not referenced in a CCL ATTACH ADAPTER statement.

Ensure that the necessary JAR files for your JDBC drivers are saved to the $STREAMING_HOME/adapters/framework/libj directory.

Note The JDBC adapter searches all of the directories below the $STREAMING_HOME/framework/adapters/libj directory and adds all of the JAR files it finds to its CLASSPATH. This means that you can create a subdirectory below the “libj” directory to keep JAR files grouped together and organized. For example, create a subdirectory named Alpha and place the Alpha JDBC driver in that specific subdirectory: $STREAMING_HOME/adapters/framework/libj/aplha/ngdbc.jar