Index Changes
This is version 1. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Open ESB Packages that Make Up the New Database Binding Component

This runtime component is available as a sun-database-binding.

The design-time components still leverage the org-netbeans-modules-wsdlextensions-jdbc.nbm. NetBeans Modules help create artifacts for the sun-database-binding. The Artifacts that the new version of these components generate are deployed to the DB BC instead of the JDBC BC or SQL SE.

Database BC (DB BC) is a Java Business Integration (JBI) runtime component that provides a comprehensive solution for configuring and connecting to databases. DB BC provides data operations as services. It supports the JDBC from within a JBI environment. Other JBI components invoke these Web Services acting as consumers. DB BC exposes both Data Manipulation Language (DML) and Data Definition Language (DDL) operations as Web Services.

DB BC also acts as a consumer incase of inbound functionality where DB BC polls data from a particular table, converts them into messages, and sends it to the Normalized Message Router (NMR). This is analogous to the inbound connections implemented in CAPS 6.

The services that DB BC exposes are actually SQL operations on Tables, Prepared Statements, and Stored Procedure. The DB BC supports the following database artifacts to be exposed as services.

  • Tables
  • Prepared Statements
  • Stored Procedures
  • SQL File

The DB BC can assume the role of either a JBI consumer (polling inbound requests) or a JBI provider (sending outbound messages).

When the DB BC acts as a JBI consumer, it polls a specified database for updates to a table in the database. When a new record is stored in the table, the database polls for the record for the specified time interval and the DB BC picks up that record, constructs a JBI message, and sends the message to the JBI framework so it can be serviced by other JBI components.

When the DB BC acts as a JBI provider, it extracts the SQL query from a JBI message received from the JBI framework. It then executes the query on a specified database. It converts the reply from the database into a JBI message that other JBI components can service.

Image shows ...

Once installed, the DB BC can be used to design, deploy, and run the Service Units. The most important part of a Service Unit is the WSDL that describes the Database services. DB BC provides a set of extension elements specific to DB BC for connecting to the Database.

The binding component provides features and facilities to the user at various stages of the composite application development lifecycle.

Database BC as Provider

Database BC acts as a provider in case of outbound message flow. DB BC acts as an external service provider when other engines and components 'invoke' it. In this role, when it receives a normalized message as part of the message exchange, it converts and extracts the SQL operation. The SQL operation is then executed on the specified database.

Database BC as Consumer

Database BC acts as a consumer in case of inbound message flow. DB BC polls for records from a particular table constructs a normalized message and sends it as part of the message exchange.

Database BC WSDL Extensibility Elements

The Database BC WSDL extensibility element is a template used to construct an instance of a DB BC WSDL. The DB BC WSDL extensibility elements contains information for constructing the DB BC message. These are constructed using the message parts, message formats, properties mapping, and other message related information necessary for the DB BC to properly map message exchanges to DB BC messages and vice versa. The DB BC WSDL extensibility elements also contain information about which database it connects.


Previous


Return to Understanding Database Binding Component

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This particular version was published on 24-Nov-08 08:11 AM, -0800 by PRABHAMS