Connectors consist of two parts: the connector framework and the application-specific component.
The connector framework, whose code is common to all connectors, acts as an intermediary between the integration broker and the application-specific component.
The application-specific component contains code tailored to a particular application or technology (in this case, JDBC). The connector framework provides the following services between the integration broker and the application-specific component:
The connector for JDBC enables the integration broker to exchange business objects with an application built on any database supported by a driver that follows the JDBC 2.0 or above specification. This section presents a high-level description of the connector's architecture and use of different JDBC drivers.
For specifying the driver to be used by the connector to connect to the database, see Enabling multi-driver support.
The connector connects to the application database by using the JDBC Connect mechanism. One connector-specific configuration parameter (DatabaseURL) allows you to specify the name of the database server to which the connector should connect. For information on the configuration parameters, see Configuring the connector.
When the connector is started, it establishes a connection pool with the database. It uses connections from this pool for all transaction processing with the database. On termination of the connector, all connections in the pool are closed.
Figure 1 shows the connector components and their relationships within the business integration system.