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 Mode Configuration
  To start and stop the adapter with an ESP project, attach it to a project using the ATTACH ADAPTER statement and configure its properties using the ESP Studio.
• Unmanaged Mode Configuration
  To start and stop the adapter independently of an ESP project, do not reference it in an ATTACH ADAPTER statement, and configure it independently outside of the ESP Studio.
• Starting the JDBC Adapter
  Start the JDBC adapter either in unmanaged or managed mode. In unmanaged mode, the adapter is started separately from the ESP project, and in managed mode, the adapter is started with the ESP project. In unmanaged mode, you can start the adapter from the command line or using the start command files.
• Stopping the JDBC Adapter
  Stop the JDBC adapter either in unmanaged or managed mode. In unmanaged mode, the adapter is stopped separately from the ESP project, and in managed mode, the adapter is stopped with the ESP project. Stop the adapter either from the command line or using the stop command files when running in unmanaged mode.
• Adapter Controller Parameters
  The Adapter Control port listens for commands. The controller.xml file is located in %ESP_HOME%/adapters/framework/config directory. This file is shared among all the adapters within the %ESP_HOME%/adapters/framework/instances directory.
• Logging
  The JDBC Input and Output adapter use the Apache log4j API to log errors, warnings, and information and debugging messages. A sample log4j.properties file containing the logging configuration is located in the %ESP_HOME%\adapters\framework\config directory.